ISSUE DESCRIPTION
In MSFS 2020 I was able to trigger multiple Light Potentiometer Key-Events in one single calulator code. In MSFS2020 only the last K-Event seems to be fired.
Example for setting 5% steps to the A32nx display brightness values with one potentiometer:
@ 655.35 / 5 / near 5 * s0
l0 84 (>K:2:LIGHT_POTENTIOMETER_SET)
l0 87 (>K:2:LIGHT_POTENTIOMETER_SET)
l0 88 (>K:2:LIGHT_POTENTIOMETER_SET)
l0 89 (>K:2:LIGHT_POTENTIOMETER_SET)
l0 92 (>K:2:LIGHT_POTENTIOMETER_SET)
l0 93 (>K:2:LIGHT_POTENTIOMETER_SET)
- only for LightPotentiometer 93 it works!
If applicable, which aircraft is experiencing this issue:
Tested with FlyByWire A32nx & Stock Asoobo TBM 930
[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?
YES
FREQUENCY OF ISSUE
How often does this occur for you (Example: Just once, every time on sim load, intermittently)?
ALWAYS
REPRODUCTION STEPS
- Remove everything from Community-Folder
- load MSFS2024 in free flight with Asobo TBM930
- Try the script with light potentiometer 14 (backlight) assigned as last k-event
@ 655.35 / 5 / near 5 * s0
l0 15 (>K:2:LIGHT_POTENTIOMETER_SET)
l0 14 (>K:2:LIGHT_POTENTIOMETER_SET)
=> works.
4. Change the order oft the light potentiometers to
@ 655.35 / 5 / near 5 * s0
l0 14 (>K:2:LIGHT_POTENTIOMETER_SET)
l0 15 (>K:2:LIGHT_POTENTIOMETER_SET)
=> Now light potentiometer 14 doesn’t work anymore.
YOUR SETTINGS
If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.
What peripherals are you using, if relevant:
Just any kind of analogue value. In my case a potentiometer on a joystick axis. So not relevant.
[PC Only] Are you using Developer Mode or have you made any changes to it?
Doesn’t change anything if DevMode is active or not.
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OP’s steps to reproduce it?
•
Provide extra information to complete the original description of the issue:
•
If relevant, provide additional screenshots/video:
•