Lorby_SI

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)

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)

That must be a limitation in the Elgato StreamDeck software. The command line is sent as-is, the underscores are definitely in there.

No apologies needed, this was an actual problem that I was unaware of. Thank you for reporting it!

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.

Which part didn't work? Couldn't map it or couldn't call it when it was mapped?

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".

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.

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

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.

Is this new? What version of the StreamDeck plugin is this?

What if you would use the AAO control layers for this? You could create several layers that you can switch between using AAO commands. That way you can "disable" certain keys and re-enable them at will. I assume that we are talking about keyboard assignments, right? So you would put all your assignments on the first layer, plus one combo assigned to "AAO_BUTTON_LAYER_TOGGLE" On the second layer you add only this assignment (=you have it on both). By triggering the TOGGLE event, you are switching between the two layers, so either your buttons work, or they don't.

I'm sorry, but that would be next to impossible to do. The whole logic that is listening for inputs is only active when you are either connected to the sim or running in offline mode. So the only possible event would be to disconnect and/or leave offline mode. But you can't turn it on again, because nobody is listening. What is your use case, why would you want to do this?

Not sure that is true. PMDG have instead made their own SDK with their very own custom events (= not actual MSFS InputEvents!). That has been the case since forever, this SDK hasn't changed at least since the P3D days. And in the MSFS behavior code they are mis-using the K:ROTOR_BRAKE event, that they send different codes to, which their internal code understands and acts upon.

InputEvents and BVars are the official method for external controls. The aircraft developers implement them specifically for each model. Or they are supposed to. Don't disregard them just because the EJets got them wrong. I have yet to find even one aircraft where the default simulator (K:) events are even used properly. They somehow never caught on in the MSFS world, everybody was working around them from the start.

The website says that they are LVars. Not a fan, personally, LVars shouldn't be used this way. As the developer rightfully says on that page "Use at your own risk". The correct way would be for them to implement InputEvents. Anyway, in the example that you posted, the three scripts would look like this: 0 (>L:B757_GEAR_HANDLE_POS, Number) 0.5 (>L:B757_GEAR_HANDLE_POS, Number) 1.0 (>L:B757_GEAR_HANDLE_POS, Number) Small scripts like these you can enter directly into the button assignment. Switch the green button to MAN, select "RPN" and then copy&paste the code into the textbox. For larger scripts, take a look at the chapter "Scripting" in the AAO manual.

No idea. What is this, where did you get this spec? Is it a variable, an event, from the simulators SDK, custom to the aircraft?? And what do you mean by "set round numbers"? "Set" where? Edit: if this is supposed to be the simulator variable A:GEAR HANDLE POSITION, that would have to be either assigned to an Axis or scripted 0 (>A:GEAR HANDLE POSITION, Percent over 100) 0.5 (>A:GEAR HANDLE POSITION, Percent over 100) 1.0 (>A:GEAR HANDLE POSITION, Percent over 100) At least in theory, I can't test it. I won't be getting the 757, sorry.

Are there no "MSFS IEs" / Input Events for this plane? If there are, you will see them in the behavior inspector too, and in AAO on the event selection dialog in the tab "MSFS IEs"

The link to the spec that I posted above is precisely for this command. Yes, this exists, but it only allows you to switch to the profiles that are part of your own plugin. Hence the detour with the additional mapping app.

Seems like it has been documented just now? The additional page parameter is there now in the SDK documentation. I will add that option to the next version of the AAO plugin. That happens because Elgato have changed the name of the profiles folder. I will fix that in the next version of the plugin

You can send network messages from AAO scripts. AAO RPN has a few commands for that, or you could resort to Javascript or JScript.

That doesn't seem to have found its way into the SDK documentation yet.

Connected to the sim - loaded a plane, sitting in the cockpit - hit "plus" to add a new button - I can click on the "Long Click" checkbox as much as I want, no CTD - ??? The Key Down/Up get new labels, as they should, and I can happily switch back and forth with no issue at all. Am I missing something?

So you are connected to the sim while you do this? (as opposed to Offline Mode). Is there anything showing in the "Device" section at this point? Maybe there is a conflict with incompatible HID or USB devices. Go to Hardware->Device Blacklist and move everything into the list on the right with the "Ignore" button that isn't a proper game controller that you are actively using in AAO. That includes all mice and keyboards too, they must be blacklisted as well (AAO talks to them through other means)

No problem here, I cannot make it CTD whatever I do with "Long Click"?? Can you describe in more detail what you are doing in what sequence to get this CTD?