Airspeed bugs for Landing refrence speeds will not set when clicking on the Flipcard

[Wothan]

Thanks for a great Aircraft.

Overall a great addon.

Title says....They just stay put at max.

[b3lt3r]

@wothan I believe you cannot set them using the flipcard until you have the flaps set to the target landing extension.

What I do (no doubt wrong) is after each extension, click on the card and that moves the bug down to give me a visual cue during what is a "busy" time :-)

It is confusing because for TO it's fine to set.

[Wothan]

@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.

[Melon]

@wothan Yeah it would be nice to be able to select it well before, either by the EFB or selecting the particular row on the flip card. Perhaps there could be an option on the Aircraft page to make the flip card a bit more granular, so you could select those specific levels.

[b3lt3r]

@wothan I agree. I'm going to see if I can figure out the command/lvar triggering the bug update and add that to my spad next event when I lower the flaps so I don't have to think about it.

[Martyn]

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.

[b3lt3r]

@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]

@b3lt3r 'L:146_SPEEDS_SET, number' can be used to trigger the automatic bug setting (just set it to '1')

[b3lt3r]

@martyn Fantastic, thank you!

update works perfectly - bugs set as each stage is deployed

[b3lt3r]

@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.

[Wothan]

Thanks Martyn - looking forward to the option.
Top notch support as always from JF.

[Martyn]

@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

[tatar]

@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.

[tatar]

I tried to do something similar to what b3lt3r did and found it relatively easy with MobiFlight (if anyone was interested).