Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

V3.00 b53, SD multigauge display does not change

Featured Replies

After updating to 3.00 b53, the multigauge display in the streamdeck no longer works depending on the L:Var value.
Streamdeck Plugin 17.02
I have downloaded the Fenix profile (https://flightsim.to/file/33274/fenix-a320-aao-scripts-streamdeck-xl-profile-teaser )
In this profile in the folder EFIS there are 2 MultiGauges buttons each to "turn left" the Efis Mode and Range. On these buttons the set mode or range is displayed with text. To "turn right" there are two SliderGauge, on these button with a picture the knob position is displayed.
After the update to 3.00 b53 the "turn left" of the button by pressing the MultiGauge still worked, but the displayed text did not change. While at the Slider Gauge buttons for "turn right" the respective button picture changed.
After I went back to version 2.81 b05 the display on the buttons of the MultiGauge works again as usual.
Thanks for advice Stefan

 

 

Edited by Stefan01

regards
Stefan Liebe

  • Author

No I did not contact him, because the names of the L: variables are correct and it works fine with version 2.81 b05.

regards
Stefan Liebe

  • Commercial Member
1 minute ago, Stefan01 said:

No I did not contact him, because the names of the L: variables are correct and it works fine with version 2.81 b05.

As mentioned in the release notes, the way that LVars are handled in MSFS has changed with SU12, and that is reflected in AAO 3.00. There is still an option to go back to the old logic in the "Application" menu of AAO, but this will not be there forever. The author of the profile must take a look at this issue - it could very well be a problem in MSFS itself (I've seen some weird stuff with their new method too)

What are the exact names of the associated LVars?

And: are you using the latest StreamDeck plugin too?

Edited by Lorby_SI

LORBY-SI

  • Author

For the Mode button

Key event K:FENIX_A3XX-EFIS_Nd_Mode_DEC

and Visibility Variable S:(L:S_FCU_EFIS1_ND_MODE, number, number) 0 ==
 

For Range button

key event K:FENIX_A3XX-EFIS_Nd_Zoom_DEC
and Visibility Variable S:(L:S_FCU_EFIS1_ND_ZOOM, number, number) 0 ==

regards
Stefan Liebe

  • Commercial Member
15 minutes ago, Stefan01 said:

For the Mode button

Key event K:FENIX_A3XX-EFIS_Nd_Mode_DEC

and Visibility Variable S:(L:S_FCU_EFIS1_ND_MODE, number, number) 0 ==
 

For Range button

key event K:FENIX_A3XX-EFIS_Nd_Zoom_DEC
and Visibility Variable S:(L:S_FCU_EFIS1_ND_ZOOM, number, number) 0 ==

Both those S: scripts are syntactically incorrect (...,number, number) and shouldn't work in either version. Is that really their code? If it is, they will be rejected by version 3.

Should be:
(L:S_FCU_EFIS1_ND_MODE, Number) 0 ==

(L:S_FCU_EFIS1_ND_ZOOM, Number) 0 ==

The "Key Events" are actually calling scripts in AAO. Make sure that the syntax of those scripts is correct too (=no copy&paste error from the SD profile...).

Edited by Lorby_SI

LORBY-SI

  • Author

... and the L:variables to change the picture in "right turn" buttons SliderGauge are the same and that works fine.

regards
Stefan Liebe

  • Commercial Member
6 minutes ago, Stefan01 said:

... and the L:variables to change the picture in "right turn" buttons SliderGauge are the same and that works fine.

"Are the same" - how? 

All I can tell you is that those scripts that you posted above are wrong and shouldn't work in either version. That is simply not a proper LVar name, and it MUST be corrected in the profile (=contact the author...)

If version 2.8x let them slip through and MSFS processed them, so be it. But I cannot explain why something that is broken is working at all (seems pointless too).

Edited by Lorby_SI

LORBY-SI

  • Author

OK thank you. I will contact the author and perhaps he can find out what is wrong. Thanks a lot Stefan

Edited by Stefan01

regards
Stefan Liebe

Hello,

thanks for the hint, I uploaded a fix (hopefully - do not have the time to test it right now, but should work)

Guenter Steiner
--------------------------------------------------------------------------------------

Betatester for: A2A, LORBY, FSR-Pillow Tester
--------------------------------------------------------------------------------------

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.