geoffda

Thanks so much! It might be worth adding some documentation around that. I see it in the AAO Specific RPN Commands section, but that is the only place it is mentioned and none of the examples use it. Anyway, thank you again for your quick response.

I'm trying to implement looping behavior in an AAO MSFS 2024 script. Here is what I've got in the editor: :loop·\n 49907·(>K:ROTOR_BRAKE)·\n (WAIT:100)·\n (L:SWITCH_499_A,·number)·0.5·>=·if{·(GOTO:loop)·}·\n However it doesn't appear that the GOTO ever executes. Here is what I'm seeing when I watch the script: Call: 49907 (>K:ROTOR_BRAKE) Pr2: 49907 (>K:ROTOR_BRAKE) Call: (WAIT:100) Call: BLK:C:\Users\xxx\OneDrive\Documents\LorbyAxisAndOhs Files\Scripts\af3ad8fa-1b30-4c2f-8d4c-f584da6af864,(L:SWITCH_499_A, number) 0.5 >= if{ (GOTO:af3ad8fa-1b30-4c2f-8d4c-f584da6af864|loop) } Pr1: 0.711 0.5 >= if{ (GOTO:af3ad8fa-1b30-4c2f-8d4c-f584da6af864|loop) } Pr2: (GOTO:af3ad8fa-1b30-4c2f-8d4c-f584da6af864|loop) The above watch seems to confirm that the predicate is true (which is what I'm seeing in the behavior window), so the GOTO presumably should execute. If I unroll the loop, I get the behavior that I expect, but I would prefer to use the loop along with a precise termination predicate. Interestingly, C:\Users\xxx\OneDrive\Documents\LorbyAxisAndOhs Files\Scripts is empty, so I'm wondering if that has something to do with my problem? Does anyone know what I'm doing wrong? Thanks!

Second that. My transfer of databases didn't go quite that smoothly, but I was able to make it work. In my case, restoring the backed up database appeared to work, but when I reopened AAO, none of my configs were present. What I noticed when looking at the configs in %USERPROFILE%AppData\Local\LORBY_SI\LorbyAxisAndOhsMSFS24 was that ConfigDatabase_MSFS2024_1.xml had been updated, but ConfigDatabase_MSFS2024.xml had not. Deleting the empty config and copying/renaming the 1st config appropriately solved the problem and I now have all of my MSFS 2024 configs moved across.

You are absolutely right! Looking at the XML, they are using different LVARs for animation versus input. Thanks for calling that out.

Wow, this is really a different implementation...If you just map LVARs, you won't hear the sounds. Wwise sounds are handled via separate LVARs that you can find in the sound.xml file. Here is an example of a script to press aileron trim left: 0·(>L:VC_AILERON_Trim_SW_VAL,·Number) 1·(>L:WASMVAR_iFly737MAX_AileronTrimSwitch,·Bool) With the script to release the switch 10·(>L:VC_AILERON_Trim_SW_VAL,·Number) 1·(>L:WASMVAR_iFly737MAX_AileronTrimSwitchRelease,·Bool)