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.

Lorby_SI

Commercial Member
  • Joined

  • Last visited

  1. Other Codes for the ISFD: STD button: 105 and 106 HP/IN button: 97 and 98 RST button: 103 and 104 Plus button: 99 and 100 Minus button: 101 and 102 Turn Baro Left and right: 107 and 108
  2. In the Sim: Activate MSFS developer mode When you are sitting in the cockpit, open "Tools->Behaviors" Click back into the sim, hover the mouse over a button you are interested in and press "Ctrl - G" This will bring up the behavior code and you can inspect the "Mouse Rect" section to see what you need to replicate in AAO The code that iFly is using is quite complex though. They aren't using distinct LVars for each button (although at first glance it looks that way - don't be fooled!). Instead they are using codes that are sent to always the same LVar, and you are expected to handle Key Down and Key Up separately. Example: the "APP" button on the ISFD As a single script: 95·(>L:VC_Instruments_trigger_VAL,·Number)·(SPLIT:100)·96·(>L:VC_Instruments_trigger_VAL,·Number)· Or you assign 95 (>L:VC_Instruments_trigger_VAL, Number) to Key Down and 96 (>L:VC_Instruments_trigger_VAL, Number) to Key Up
  3. Hello @ll, SimConnect cannot handle variables of the following nature: (L:1:varname:index, Number) To work around this, run a (SIMPROC) autoscript in AAO at suitable intervals that transfers the desired value into your own LVar. Example: (SIMPROC)·(L:1:WT_B707_ENGINE_FUEL_CONSUMED:1,·Number)·(>L:MyEngFuelCon1,·Number)
  4. Hello @ll, AAO 4.61 has been uploaded to the shops. - Change: RPN: added menu option to temporarily disable the execution of all autoscripts - Bugfix: MSFS24: writing to Z: variables not working - Bugfix: Add/Change Buttons: fixed CTD with certain actions - Bugfix: Change Axis: fixed skew point editing logic - Bugfix: RPN: "rndsel{" couldn't be used within if - must now end on "}rndend" instead of just "}"
  5. The same happens when you use the delete buttons, those with the red "X". This will be fixed in the next version.
  6. Since the StreamDeck has momentary buttons, IMO you have to create toggle scripts. For example for the fuel pump switch: 0 1 2 1 (L:1:SWS_FUEL_Switch_Pump_1, Number) (L:SWS_FP_IDX) 4 iseq (>L:1:SWS_FUEL_Switch_Pump_1, Number) (>L:SWS_FP_IDX)
  7. Are we talking about MSFS 2024? And do you mean the "A/T" button on the MCP? Then it would be this script: (SIMPROC) 0x00040607 'FSS.INTERACTION' (>F:KeyEvent)
  8. That must be a limitation in the Elgato StreamDeck software. The command line is sent as-is, the underscores are definitely in there.
  9. No apologies needed, this was an actual problem that I was unaware of. Thank you for reporting it!
  10. There is one CTD that I was able to confirm - and that happens when you delete assignments from the Key Down/Key Up sections using the "red x" buttons. Not directly related to the Longclick, but it might trip you up nevertheless. This will be fixed in the next version of AAO.
  11. Which part didn't work? Couldn't map it or couldn't call it when it was mapped?
  12. Was the StreamDeck connected to AAO at this point, and is AAO connected to the sim or running in Offline Mode? All Buttons are only re-drawn when AAO is actually "active".
  13. Version 73.02 is out, it has the page parameter now. The SdProfileMapping tool has been fixed. This must be used before you can switch on any profile or page! I made a small script package demonstrating the technique using AAO RPN scripts: https://www.dropbox.com/scl/fi/5g7kh0dath6nnh2x8yf7b/SD_Ctrl_Scripts.zip?rlkey=fxpw9cp1bngd24fgp1v5b9zap&dl=0 The script group is called "SD_Ctrl" Make sure to call the "init" script before doing anything else. Ideally configure it as a Global Automated Script, so you can't forget it. After that you can just use the "Toggle" scripts to browser through the profiles and their pages. Do that slowly, apparently the StreamDeck sometimes needs a while to catch up. If it doesn't work out of the box, check out the "switch" script of the group. It uses the internal Variable (L:SD_ID_2, String) to determine the ID of your StreamDeck device (if you have several, then there is more than one of these LVars). Change the variable name to the one correct for you. You may have to switch to a few different AAO profiles manually a couple of times before the LVar is visible. These scripts use a special feature of the SdProfileMapping tool - it creates a simple CSV file with all mapped profiles and the number of pages they have in "Documents\LorbyAxisAndOhs Files". The "init" script reads that file, and with that information it can toggle through all the mapped profiles and their pages.
  14. Version 73.02 has just been released, that should fix the grey bar. It is available on both the axisandohs.com website and fs.to
  15. No, don't bother (unless you need it = when you download and install a profile that has been made with this version). This is something new, apparently the definition of when this bar is NOT there has changed in the StreamDeck software and/or the default layout of the rotary encoder. Unfortunately this is very tricky and I can't promise a quick solution. The work around is to use the RotaryEncoderCanvas action instead - which I suppose is what most authors are doing anyway.

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.