Thank you for the SU10 updates that fixed our compilation! We've now worked through the rest of the code and got it to compile. When running, the WASM gauge is going into a "dirty" state after our variable initialization but I am not getting any log or indication of why in the console.
When I try to isolate, the issue seems to be related to when we allocate our variable memory. If I add a "return" randomly somewhere earlier in the code, it works, but if the function executes fully, the dirty state is applied. The code is about 1,000 lines of more or less identical function calls with different strings to setup LVARS and such.
I've checked for obvious issues like stack overflows and such to no avail. Additionally, the code is working in P3D and in our standalone test environment, so I know it's not a major logical error. Any help would be appreciated.
The latest WASM file is here: https://invernyx-my.sharepoint.com/:u:/p/cbiedenkapp/EW97yHTz9rZDoAPS01Hhb1oBSatxa6oQp-sLa2-5jw3-vQ?e=FwfJhn
The panel.cfg entry to load the gauge is:
Thank you in advance!