Airspeed bugs for Landing refrence speeds will not set when clicking on the Flipcard
-
@b3lt3r
While it does make sense, I would rather like that I could select my final Flaps setting. f.ex. on the Tablet, so that I can set all bugs in advance, well before being busy setting up for the Approach. -
We've added a 'Flipchart Options' tickbox to the EFB configuration menu. When enabled, you can click on a specific row on the speed flipchart that you'd like to set on the ASI bugs, e.g. take-off flaps 18 or landing flaps 30.
That's been added as an option as the size of the flipchart can make it a bit fiddly from a distance, so when the option is disabled it'll continue to set the ASI bugs based on current flap selection, regardless of where on the flipchart you click.
Martyn - Development Manager
-
We've added a 'Flipchart Options' tickbox to the EFB configuration menu. When enabled, you can click on a specific row on the speed flipchart that you'd like to set on the ASI bugs, e.g. take-off flaps 18 or landing flaps 30.
That's been added as an option as the size of the flipchart can make it a bit fiddly from a distance, so when the option is disabled it'll continue to set the ASI bugs based on current flap selection, regardless of where on the flipchart you click.
@martyn That's great thank you Martyn. Is there a sim-connect or LVAR used to trigger the bug set when currently clicking on the card? I've tried to find it but all I see in the spad and devmode monitors are the bugs being set rather than any triggering action. Have the feeling this is one of those WASM gauge ones :-)
-
@martyn That's great thank you Martyn. Is there a sim-connect or LVAR used to trigger the bug set when currently clicking on the card? I've tried to find it but all I see in the spad and devmode monitors are the bugs being set rather than any triggering action. Have the feeling this is one of those WASM gauge ones :-)
-
@b3lt3r 'L:146_SPEEDS_SET, number' can be used to trigger the automatic bug setting (just set it to '1')
-
@b3lt3r 'L:146_SPEEDS_SET, number' can be used to trigger the automatic bug setting (just set it to '1')
@martyn will the Spad Next mod I've done still work as-is after the changes in the upcoming patch?
I trigger the 'L:146_SPEEDS_SET, number' => 1 as a second action when I command a notch down on the flaps so the bugs are set for correctly for the actual setting.
-
@martyn will the Spad Next mod I've done still work as-is after the changes in the upcoming patch?
I trigger the 'L:146_SPEEDS_SET, number' => 1 as a second action when I command a notch down on the flaps so the bugs are set for correctly for the actual setting.
@b3lt3r Yes, you can use that same variable to configure the speed bugs for your current flap selection, or you can use 'L:146_SPEEDS_SET_FLAP' with these values to set the bugs:
1 - Takeoff 18
2 - Takeoff 24
3 - Takeoff 30
4 - Approach 33
5 - Approach 30
6 - Approach 24
7 - Approach 18
8 - Approach 0 -
@Martyn
Actually, it would be nice to have such functionality as the third option in "Flipchart Options" or at least a key assignment to trigger the "click on a flipchart" event (if its easier to implement).
On the final approach, I often don't have time to click on the flipchart with mouse.
I know I could write a code to capture the event via simconnect but it is not an easy task for me. -
@Martyn
Actually, it would be nice to have such functionality as the third option in "Flipchart Options" or at least a key assignment to trigger the "click on a flipchart" event (if its easier to implement).
On the final approach, I often don't have time to click on the flipchart with mouse.
I know I could write a code to capture the event via simconnect but it is not an easy task for me.
