Well, I’ve had a lot of fun with AAO+Streamdeck and at least I’m not as intimidated or demotivated as I was at first when I didn’t understand very well how to do things

what I’ve noticed, though, is when rotating knobs or dials is that the bug will move like in a chopped fashion, as when you have issues with FPS instead of with that nice flow that happens with a joystick or a keyboard when you just map it within the FS settings/interface

i think my streamdeck is connected directly to the PC and all peripherals (Tca joystick and quadrant and pedals) are plugged to a powered USB hub so all the motherboard surplus power should be feeding the StreamDeck without issues (and I removed that cap on the power that the ports can supply)

is it supposed to update like that, with that stutter refresh mode? 
 

thanks 

Edited April 14Apr 14 by pepetrueno

1 hour ago, pepetrueno said:

is it supposed to update like that, with that stutter refresh mode? 

Depends on what you mean - the display/dial in the sim or the display on the StreamDeck button?

1. Behaviors in the sim: generelly no. But there are probably a dozen things that could theoretically cause this, but none of those is actually "known" or documented.

Off the top of my head I'd say that this would depend on which controls of what aircraft you have assigned exactly how, what else the StreamDeck profile contains and how many scripts are in play in AAO in general that may cause delays. On top of that, the communication between the StreamDeck plugin and AAO is done via your IP Network stack. So, in addition to USB problems you may have, any incursions that involve your network processing would also interfere (like big download streams running in the background).

Mind you, this is all theoretical. I've actually not heard of this behavior before.

2. On the StreamDeck itself: What will happen though is that the display on the StreamDeck itself will be choppy, and that is actually normal. The actions are only refreshed every x milliseconds (depends on what you set in the settings.js file), so there cannot be "fluid" changes by definition. Dialling up the refresh rate will potentially cause other problems, so compromises have to be made. But this would also depend on what the action + plugin + AAO + sim have to do in order to process your input. So this may be an issue with some planes and implementations but not with others. 

Personally, I've never noticed either - but I'm not a "power user".

Edited April 14Apr 14 by Lorby_SI