3 hours ago, Lorby_SI said:

The AAO StreamDeck plugin version 13.01 is available for download on the AAO page, it has a new action for rotary encoders now. The action is described in the PDF that comes with the download.

I've also uploaded the example above, demonstrating the basic concepts using the controls for the default autopilot.

All this is still in prototype state. 

Thank you!

18 hours ago, Lorby_SI said:

The AAO StreamDeck plugin version 13.01 is available for download on the AAO page, it has a new action for rotary encoders now. The action is described in the PDF that comes with the download.

I've also uploaded the example above, demonstrating the basic concepts using the controls for the default autopilot.

All this is still in prototype state. 

Great job and Thank you!
I wonder if this enhancement works with "dial stack" (pile of action) available for Stream Deck Plus.

1 hour ago, Peppuzzo said:

Great job and Thank you!
I wonder if this enhancement works with "dial stack" (pile of action) available for Stream Deck Plus.

Yes, it does.

Is this updated plugin only required if one uses the Stream Deck Plus?

37 minutes ago, mrm0508 said:

Is this updated plugin only required if one uses the Stream Deck Plus?

At the moment yes, that is the only change. There will be a version 14 which will be redesigned on a larger scale - that would be one that everybody may want. 

Why the redesign - I have three StreamDecks at the moment, and it turned out that there can be issues when the plugin tries to handle them. Cleaning up the whole thing and making it more modular seems like a good idea.

Hi there, I've been working with your plugin getting all my stream decks (15 key, XL, and now SD+) configured. I have a question with the rotary encoders on the SD+. Do you know how I can make it so that I can choose between 100 and 1000ft when selecting altitude? I fly the Longitude, and in the real aircraft you just push in on the altitude selector knob to change between 100 and 1000. I know I can do a rotary stack (I think it's called) to where I can emulate that action, but I'm having a hard time figuring out how to make the encoder go from 100 to 1000. I use the stream deck C700 mod from flightsim.to and it has two buttons that'll let you change between 100 and 1000, but the value field used in those buttons to differentiate between 100 and 1000 I can't seem to find in the rotatory knob functions.

10 hours ago, skytation said:

Hi there, I've been working with your plugin getting all my stream decks (15 key, XL, and now SD+) configured. I have a question with the rotary encoders on the SD+. Do you know how I can make it so that I can choose between 100 and 1000ft when selecting altitude? I fly the Longitude, and in the real aircraft you just push in on the altitude selector knob to change between 100 and 1000. I know I can do a rotary stack (I think it's called) to where I can emulate that action, but I'm having a hard time figuring out how to make the encoder go from 100 to 1000. I use the stream deck C700 mod from flightsim.to and it has two buttons that'll let you change between 100 and 1000, but the value field used in those buttons to differentiate between 100 and 1000 I can't seem to find in the rotatory knob functions.

Generally speaking, you can either assign the script to the click of the button itself or assign it to the touch strip above the button (like I did in my sample autopilot profile).

If you are considering a stack, that is like having several encoders all at once. Make one that changes alt by 100 and another that changes by 1000 and stack them. Then you click on the encoder to switch between them.

As for that specific profile - can you please post a screenshot or description of the "value field" that you are looking for? I only provide the simple StreamDeck example profiles, so I need a bit of guidance about what the author may have done there.

Edited December 2, 20223 yr by Lorby_SI

Sure thing! This is what's tied to the button on the stream deck XL profile from flightsim.to.  This is the button that will change your altitude in 1000ft increments, and the 100ft increment button looks exactly the same except event value=100.  I have my altitude selector set up on my stream deck+ encoder now (using the same events... K:AP_ALT_VAR_DEC and K:AP_ALT_VAR_INC), and it changes in 100ft increments.

This isn't a life or death thing, more of just a "realism" effect I'd like to be able to have if possible. I'm fine with it either being an encoder stack where if I click the encoder if cycles me between 100 and 1000, but I also thought just putting a button on the touch bar for that encoder that would switch between 100 and 1000 would work too. I just can't find that "event value" or something similar in any of the Stream Deck+ button options to allow this.

I can easily spin the altitude knob and get to the altitude I need fast enough, but if there was an easy way to allow me to switch between 100 and 1000 increments while using the encoder knob, that would be awesome. Thanks again!

 

28 minutes ago, skytation said:

except event value=100

Check the property inspector for the Rotary Encoder action. For every "move" there is the selection of type + the input box for the event name, and below each of those there is a textbox for the value that is sent with the event. 

left turn  + left value
right turn  + right value

key down event  + key down value
key up event  + key up value

touch tap event  + touch tap value.

Same thing as with the button actions really.

So if you want to do it that way, you "stack" two rotary encoders over each other, and select K: AP_ALT_VAR_INC for the right turn with "right value" 100, K: AP_ALT_VAR_DEC for the left turn, also with value 100. and on the encoder "above" it you select the same events + value 1000. 
Pressing the knob already switches between these "layers" , the StreamDeck Plus does that by default without any configuration.

 

Edited December 2, 20223 yr by Lorby_SI

Yep, that's exactly what I tried last night....no go. Still only cycles through the altitude in 100's. I stacked two encoders, and then did 100 for the left/right values on one, and 1000 on the other. Both just turned it in 100ft increments.

Again, not a huge deal, it turns fast enough where I can go from 0-10,000ft in just a handful of turns, so I'll survive. Thanks for the quick replies, though, I appreciate it!

Weird. I'll check it out. Sounds like the actions in the stack are not as separated as they should be. Not that I could do anything about that though, this is all Elgato internal logic.

I did this completely differently in my AP example. I am using an LVar that stores the 100/1000 and the tap on the touch strip changes between the two. Coding is a little bit more involved though. Doesn'T require a stack, it is just the single encoder.

I am using this for the left turn:
Event: S: (L:AaoAltVarAm) 0 == if{ 100 } els{ 1000 } (>K:AP_ALT_VAR_DEC)
Value: 0

this for the right turn:
Event: S: (L:AaoAltVarAm) 0 == if{ 100 } els{ 1000 } (>K:AP_ALT_VAR_INC)
Value: 0

And this for the tap (this is the switcher for the increment value variable
Event: S: 1 (L:AaoAltVarAm) - (>L:AaoAltVarAm)
Value: 0

Edited December 2, 20223 yr by Lorby_SI

Just pasted your code in above, and it worked great! Started at 100 increments, and then when I tapped the touchscreen it changed to 1000! However, when I tap it again I can't get it to go back to 100. Hmmm.

Also, sort of related to this, but is it possible to get a variable to show on the touch that'll show what "increment" you're in? Like if you're on 100 have it either display '100', and if on 1000 have it show '1000' (or something similar)? This question comes from my use of a "speed" knob I created on one encoder, and then have a touch function that allows me to switch the speed mode between "manual" and "FMS" (again, this is in the Longitude...I realize that's not a common function in all aircraft). I was able to create the function by using H:SD-C700 Longditude-AP_SPD_MODE on the touch tap event, and then in the value variable I have L:XMLVAR_SpeedIsManuallySet, BOOL. This simply returns a 0 or 1 on the touchtap screen. I was just curious if it was possible to modify that variable code to say if the boolean result = 0, then display "FMS" and if boolean = 1, then display "MAN".

I may be asking for too much here hahahaha, but thought I'd ask since you seem VERY knowledgeable in this.

8 minutes ago, skytation said:

Just pasted your code in above, and it worked great! Started at 100 increments, and then when I tapped the touchscreen it changed to 1000! However, when I tap it again I can't get it to go back to 100. Hmmm.

Also, sort of related to this, but is it possible to get a variable to show on the touch that'll show what "increment" you're in? Like if you're on 100 have it either display '100', and if on 1000 have it show '1000' (or something similar)? This question comes from my use of a "speed" knob I created on one encoder, and then have a touch function that allows me to switch the speed mode between "manual" and "FMS" (again, this is in the Longitude...I realize that's not a common function in all aircraft). I was able to create the function by using H:SD-C700 Longditude-AP_SPD_MODE on the touch tap event, and then in the value variable I have L:XMLVAR_SpeedIsManuallySet, BOOL. This simply returns a 0 or 1 on the touchtap screen. I was just curious if it was possible to modify that variable code to say if the boolean result = 0, then display "FMS" and if boolean = 1, then display "MAN".

I may be asking for too much here hahahaha, but thought I'd ask since you seem VERY knowledgeable in this.

You should really check out my Autopilot example profile... and the PDF manual that comes with the AAO StreamDeck plugin. Of course you can show any value(s) in the touch screen.

As for the previous problem with 100/1000 that is actually a bug in the Rotary Encoder Action of the AAO plugin. I will fix that in version 14, but that is tied to AxisAndOhs version 2.71 and I have to get the main app ready for release first.

If you want to fix it yourself and are comfortable with a little bit of editing:

1. Open this file in a text editor: C:\Users\...\AppData\Roaming\Elgato\StreamDeck\Plugins\com.lorbysi.aao.sdPlugin\js\rotaryEncoderAction.js
2. In the lines 90, 94, 116, 120, 147 and 151 replace <settings["onevtval"]> with <evtval>
   So for example line 151 looks like this after the change: "requestObj.setvars[0].value = evtval;"
3. Save, Close, then restart the StreamDeck software.

 

Edited December 2, 20223 yr by Lorby_SI

Awesome, I will check out your example and the manual and see if I can get the touch value to show the way I want.  Thanks!

As for the coding change to fix the 100/1000 thing, I'll just wait for your release and then revisit it. I don't want to go changing any core coding just in case...like I said, i can easily spin it to the altitude I need going in 100s just fine....and honestly, I may just leave it that once I start using it that way and get used to it.

Thanks again for all the help! 

14 minutes ago, skytation said:

However, when I tap it again I can't get it to go back to 100. Hmmm.

Sounds like you may have a syntax error in there somewhere?