Context: Custom standalone WASM module built for MSFS 2020 (SDK v.0.24.3) installed in MSFS 2024 Community folder.
Similar MSFS 2020 issue: None, works as expected in 2020.
Bug description:
Invoking Gauge API trigger_key_event_EX1() doesn’t seem to have any effect the first time after Sim has been started.
Every subsequent invocation works as expected. Even if the WASM module is reloaded (eg. rebuilt from project manager). Seems specifically after first start of simulator itself.
Repro steps:
Load a standalone WASM module which calls trigger_key_event_EX1(65752, 0, 0, 0, 0, 0) (on demand somehow or twice after a flight has started). This ID is for the PARKING_BRAKES event (toggle parking brakes).
Load a freelight with a stock Cessna 172, starting on a runway.
Either trigger the trigger_key_event_EX1() call in the WASM module somehow or wait for it to trigger twice.
Observe that the first call seems to be ignored, meaning the parking brake state doesn’t change. Subsequent calls work fine.
Start simulator, load into a flight with C172 on runway, as above.
Start WASimUI, hit the “Connect” button at top left, then use “Key Events” section to send a PARKING_BRAKES event.
This ends up invoking void sendKeyEvent() in the module’s code (which then uses trigger_key_event_EX1()).
Thanks for the detailed report - we managed to reproduce, indentiy and fix the issue.
Unfortunately we were late for it to be included in the SU1 release candidate build, which means we may not be able to ship the fix to you prior to the SU2 flighting.
If any window opens to push it prior to the official SU1 release, we will let you know.
Apologies for the mistake - the fix has been integrated from the SU2 branch to the SU1 branch on Feb 21th. It should be included in the next SU1 Beta (1.3.23.0 and higher).
Can you please check if the fix works as expected when the build is available?
No, sorry, not participating in the beta. This was originally reported by a user of my software, so I can check with them. Will ack if I hear back or when I can test this in release version. Or maybe @Seb851 can confirm.
Thanks to any/all for fixing and getting it included.