Hi, 

I recently purchased a stream deck and the Axis and Ohs software. I knew there would be a lot to learn and look forward to it but are there any guides specifically for stream deck and the plugin. I'm using a few youtube videos and bits I can find on the forums but I'd love something where I could look for what I wanted specifically. For example, I used the developers mode in game (MSFS) to find the variable for the Autopilot Altitude. I generated a script (in the AAO software) to increase this value by 1000 with a right turn of the dial and copied this into the streamdeck software (into the event for turning the dial). I turned the dial and this set the altitude shooting up non stop. Even after restarting the game it still did the same. I had to overwrite the scripts (import scripts) to stop this happening. 

Any advice would be greatly appreciated as it will probably cut years from my learning curve if I carry on how I am!  Sorry if this is not the place to ask this but I thought it was worth a try. 

Thank you for reading my post.

 

Dave 

Can you be more specific about what you did and what that script looked like? What aircraft was that for? Screenshots?

Are you certain that the script did what you thought that it would do? Did you test it in AAO (using the "Test" button on the Editor dialog?) 

And what does "copy into the StreamDeck software" mean exactly? There are two options how to call a script. One is calling is as K: with "scriptgroup-scripttitle" the other is using type S: and entering the actual code in the StreamDeck Action. Be mindful that you should not copy code directly from the editor, instead use the grey box below it - that contains the compiled code - and when you copy & paste that all formatting (and especially the "dots") are removed.

Edited January 9, 20242 yr by Lorby_SI

Hi, Thank you so much for getting back to me so fast! I didn't expect a reply tonight. From your reply I've figured I need to do a bit more homework as I'll just be wasting your time. I have higher education qualifications in software engineering from when I was much younger so I know I can crack this! 

My question was just a, possibly poorly written, example of an issue I've had. My general struggle is just getting started with understanding the whole system. I know I can watch events and variables from your software. I can also see variables within the developers mode but these seem to differ from the AAO software and I just want to understand how to use this data on the stream deck. I feel I may have been a tad lazy in reaching out to you in the hope of finding documentation aimed at the stream deck platform and how to use it. 

Thanks again for responding to me and sorry I've wasted your time with such a vague question. I've not done anything like this for a long time so I just need to get my head into gear and I'll be able to ask proper questions when needed.

Sorry again

 

Dave 

Finding the correct items to control a button or lever in the cockpit with is tricky business, especially in MSFS.

What you initially see in AAO are the variables and events from the MSFS SDK, nothing more. The problem now is, that none of the aircraft developers use them. Or at least not for non-standard controls in the cockpit - but there are many who don't use them at all. Not even Asobo does it all the time.

With the current version of MSFS things have become a little easier. 

• When the default/SDK events are of no use in that particular aircraft...
• first check the "MSFS Input Events". They appear in the selection lists in the group "MSFS Input Events" when you are sitting in the cockpit, not before. AAO reads them from the sim at runtime, because they are not the same for every aircraft. On the StreamDeck that would be type "IE:".
  Warning: the "Test 0" and "Test 1" buttons on the event treelist don't work for input events. That is a bug in AAO 4.0.
• If you can't find the desired control there, switch to the MSFS developer mode, Tools->Behaviors. Hover the mouse over the button or lever that you are interested in and press Ctrl-G
  This will bring up the behavior code (not for all aircraft, but most of them). First place to look are the Interaction components at the bottom of the list. They usually contain mouse actions in their names, like "LeftSingle" or "Drag".
  That is what you want, you will have to replicate the code that a mouse actions initiates in AAO to make it work. This code can take a myriad of forms, from simple BVars, HVars, K-Event to entire script involving LVars.
  All those can be used in AAO in scripts, some can be assigned directly to axis and buttons.
• If all that fails you may have found an item that cannot be controlled from the outside at all, because it is "mouse only". Those really exist, for example the carb heat lever in the Big Radials Norseman. Not a lot you can do when you hit this.

Are you familiar with the ready-made StreamDeck profiles on flightsim.to? If not, I would strongly suggest to download one of them and install it. Talented simmers put endless hours into those! (make sure to buy them a coffee...)
This has the benefit that you have a baseline, a working solution that you can analyze - and familiarize yourself with the general patterns and pitfalls.

AAO is ultimately just a translator between you/your hardware and the MSFS SDK. Shortcuts are rare...

 

Edited January 10, 20242 yr by Lorby_SI

Hi, thank you again for your reply. There's some good information for me to get started with. I have downloaded some profiles from there thanks. Its crazy to see how much effort has been put in so will definitely buy them a coffee. The profile I wanted for the Hjet was designed for the Stream Deck XL so I had to negotiate buying that with the wife (so glad I got an understanding one!! and she got a hairdryer out of it) ! I'm going to spend time looking into how they have done things and hopefully pick up the syntax I'll be using. 

Thanks again for getting back. It's appreciated.

 

Dave  

2 hours ago, dave091277 said:

The profile I wanted for the Hjet was designed for the Stream Deck XL

That's not really an issue. You could use my StreamDeckEditor app to move over some of the actions to the Plus "offline". And for the rotary encoders you only want the scripts that come with the package.

But getting an additional XL is certainly a good idea, that is an ideal combination. Especially when it comes with a hairdryer!