Lorby_SI

Not at all, or rather, not to me. When I write about an app being "performance intensive" I am talking about the load that running this software is causing on your computer. I am talking about high numbers in the task manager for % CPU, %GPU, %disk access, % memory consumption. An app can be very responsive and at the same time very performance intensive. Meaning that it requires a lot of processing power to be responsive. If that is the case, then this software is very sensitive to performance shortages - when your CPU does other things (like running MSFS and a ton of related addons and apps), then my "performance intensive" app will suffer = it will slow down and become unresponsive.

Doesn't matter, there is no clear-cut solution, in fact, I cannot even point you at a singular cause. But I already wrote all this before. It could be that too many performance intensive StreamDeck Actions are in play (which means that they require a lot of processing power and are prone to lag when the power is not there), it could be that what you do in the sim or what you read from the sim is laggy, it could be that SimConnect or AAO is overwhelmed, it could be that there are other SimConnect errors that force AAO to slow down and reconnect - or two dozen other things.

No. The parameter determines how much time is passing between each update. The higher the value, the slower the StreamDeck. This does not change the amount of data that has to be transmitted in the slightest. So if there is too much data, you have the same problem, just at larger intervals. My advice would be to forget about the parameter. It is only there because I don't like hard coded parameters. There is no intended use case for this number. Maybe some day someone may want to change the number and has a positive effect from it. Maybe that someone is you. But I doubt it.

The effect is simple and exactly as you would imagine. Set refresh to 1000ms and all buttons will only refresh once every second. Press a button and it will take up to 1 second before you get the feedback. You can try setting it to 150/200/250 in small steps to find some middle ground between performance and responsiveness, but it will obviously never become more responsive. And don't bother going below 100ms, that will cause even more problems.

No, I'm afraid that is not how this works. The refresh rate is a global parameter, when you set it to 1 second, everything will refresh at 1 second intervals. I doubt that it would make any difference anyway - you will probably have the same problem, just at larger intervals. I will keep it in mind tough, that one may want to set a different refresh rate for separate StreamDecks. Problem is, that the plugin is run globally by the Elgato software for all devices at the same time. A lot depends on what actions are in use. Graphics and/or complex logic, especially MultiGauge and RotaryEnvoderCanvas require a lot of processing power and when used in large numbers are prone to cause performance problems. The Elgator software/runtime itself is not really meant to do that kind of heavy lifting I guess.

That would also depend on what kind of action has been used. The "Rotary Encoder Canvas" action is much (!) more performance intensive than the normal one (but a lot prettier). Especially when the author used large images for the graphics (=larger than they need to be for the little display) It is also possible that you have errors in the action's parameters that cumulate at certain times. I'd suggest taking a look at the StreamDeck process in the Windows Task Manager, to see if there is an idication that it is drawing too much processing power at certain times. There are also the StreamDeck logs (\AppData\Roaming\Elgato\StreamDeck\logs) and the Elgato developer web console where one can check for runtime errors (Getting Started | Stream Deck SDK (elgato.com) Item 5). Also, the AAO WebAPI that the SD is accessing has a load balancing option, you can direct the SD plugin to use the second port in case you need the first one for other items. But I don't know your actual hard- and software configuration, so this suggestion might be pointless.

Sorry, but I have no idea what would cause this. There are at least a dozen options, not taking into accout that what you do with the dials is relvant too (and can cause hold-ups and general trouble in the sim). On a side note, it is IMO not a good idea to run several tools at the same time that essentially do the same thing (AAO, SPAD, FSUIPC, Mobiflight). You can of course do as you wish, but AAO does not officially support any of these combos (as they can be unpredictable and gut feeling says that they spell trouble. As demonstrated by Mobiflight, when all MIDI devices stopped working in AAO).

Dial Stacks are not a feature of the AAO plugin, they are a feature of the StreamDeck Software. That is the manual you have to look into. The AAO plugin does not contain any special code or methods for stacked actions. That is why they are not in the manual (which is primarily for the authors of StreamDeck profiles, as detailed in the other thread.

Please take note of the red text on the downloads page of the AxisAndOhs website. The StreamDeck plugin is a free hobby project, it is not part of the AAO retail package. The only purpose for the plugin was to demonstrate how to use the AAO WebAPI, it was never meant to become a major feature. To make your own Actions for it, you need to know the basics of the MSFS SDK, RPN programming and ideally a bit of graphics design. No manual or documentation can teach this in such a way that it is easy to do. It requires time and dedication, which is why most people rely on the SD profiles that talented authors provide. "Lorby" =me doesn't provide any profiles - I only provide the hammer, I don't build the house. The Plugin started out as nothing more than the aforementioned demo. Over time, features and items have been added at the request of the authors who were making StreamDeck profiles. There are things in there where I myself don't know how they are used. I don't need to, I only need to know the mechanics. The parameter that you mention determines how often the data on the SD is refreshed. That's all. Set it to 1000 and the SD will only refresh once every second. So if you feel that the SD plugin is being clogged up by too much data, make the refresh time bigger. The parameter has no other practic al implication than making the SD faster or slower, and I doubt that this has anything to do with your problem. You can only try and observe. There is no way to tell what could be causing your troubles, sorry. The problem doesn't even have to be related to the SD or the plugin (or too many of them operating at the same time?), it could be a SimConnect issue, a problem in the sim or something in AAO. There are infinite possibilities, depending on what has been assigned to which action doing what exactly in AAO and/or the sim....etc...

Sorry, I'm away from the computer this week. The aforementioned IE works fine for me, together with the reverser toggle button ( also IE ) There is no reason why it shouldn't work for you??

AAO and SPAD are not related. As I wrote above, AAO doesn't know and doesn't care about custom variables. As every aircraft developer can just invent them, there is IMHO no point in even trying. When you know their names, you can just use the variables in Scripts or add them to the database manually if you really want to. AAO doesn't have to know them in advance, they just work - as you can see in the scripts above. If you insist on seeing a list of the LVars, use "Scripting->Read LVars from sim" in AAO. This will add all currently available LVars to a group called "Local Simulator Variables". Just be aware that there is A LOT of them. Using the MSFS developer mode / Tools->Behaviors / Ctrl-G method to find out about the actual control in question is way better. Mostly because LVars are not the recommended choice for operating controls - that they sometimes work is often more of an accident (again IMHO). Look for "MSFS Input Events" first, which are in the Event treelist anyway in a group of the same name (if the developer chose to implement them)

I've just uploaded a new version of the EJets WebFMC too. There were some styles missing (like the white lines on the Radio page).

I thought that I did just that? Yes, it is working. When the screen is blank, then the Community package "zzz-lorbysi-aao-fsse170mcdu" for that WebFMC is either missing, disabled or otherwise non-functional in your sim.

What you are seeing is the representation in your Windows Registry. Not all of the devices are actually there, but Windows remembers them anyway...

n·(>L:FSS_EXX_AUTOBRAKE,·Number) n goes from 0 to 4 for the 5 positions of the selector The actual solution will depend on what control you want to assign to it (button, axis, rotary encoder..?) For example, this script is a one button toggle that cycles through all positions of the autobrake selector 0·1·2·3·4·3·2·1·(L:FSS_EXX_AUTOBRAKE,·Number)·(L:EJET_AB_IDX)·8·iseq·(>L:FSS_EXX_AUTOBRAKE,·Number)·(>L:EJET_AB_IDX)