13 minutes ago, toby23 said:

I can make it work for Rotary Encoder but the image upload / header / text definition has confused me completely.

The Canvas and the MultiGauge are both "painting" on the little screen. Remember the flightsim XML gauges? In general principle they work a bit like that.

• You can define an unlimited number of images (=definitions, where each has its own header and its own variables etc.) that are layered one on top of the other. Like I do in the PDF with several layers that have transparent bits.
• The same goes for text, you can add as many text definitions as you like in different positions and colors, each displaying a different variable, text or whatever.
• You give each definition (image and text) its own header, so you know what is what.
• Each definition is "Save"d separately, and the "Add.." button clears all fields so you can create a new definition.
• At runtime the plugin will combine all these definitions into one single image that is then displayed on the SD. (this is why it is important to resize the images so they fit the little screen - if you make them bigger, the plugin has to scale them every time they are processed, which costs unnecessary CPU cycles.

But this is just the start. There is many more, and the learning curve is quite steep. Which is probably why there aren't that many authors of SD profiles around (who publish their work).

Edited May 8, 20242 yr by Lorby_SI

Unfortunately the display is not updating the Heading when I turn the dials. Can you see why @Lorby_SI?

I couldn't see where to enter the 'value variable = AUTOPILOT HEADING LOCK DIR, Degrees'

Edited May 8, 20242 yr by toby23

2 minutes ago, toby23 said:

Unfortunately the display is not updating the Heading when I turn the dials. Can you see why @Lorby_SI?

I couldn't see where to enter the 'value variable = AUTOPILOT HEADING LOCK DIR, Degrees'

In your screenshot you are displaying the actual heading, right? Why would that variable change when you change the AP heading?
And it is quite big. Where were you planning to add the AP value (visually I mean). 

To add more text to the action, just create another text definition. That is what the "Add" button is for. Then both values will be displayed.

 

Edited May 8, 20242 yr by Lorby_SI

Ah! I figured it out! I was using the wrong variable and displaying the 'Heading' and not the 'Selected AP Heading'!

 

Just now, toby23 said:

Ah! I figured it out! I was using the wrong variable and displaying the 'Heading' and not the 'Selected AP Heading'!

 

Yes.

I thought that you wanted to display both...

Edited May 8, 20242 yr by Lorby_SI

1 minute ago, Lorby_SI said:

Yes.

I thought that you wanted to display both...

Maybe another day, I want to fly not programme now 🙂 Thank you again for your help.

Is it possible to display the numbers with a , e.g. 12,500 instead of 12500?

 

31 minutes ago, toby23 said:

Is it possible to display the numbers with a , e.g. 12,500 instead of 12500?

Either with the Multiplier + Decimals settings (possibly mult 0.001 and 3 decimals?) or use an S: type RPN script to format the number as a string of your choice using the %...%!...! syntax 

Be mindful of performance. Nothing is for free, the more complex you make these gauges, the more CPU power will be eaten up by the StreamDeck software.

Edited May 8, 20242 yr by Lorby_SI

11 minutes ago, Lorby_SI said:

Either with the Multiplier + Decimals settings or use an S: type RPN script to format the number. 

The multiplier only adds or removes 0's, it doesn't add a ','.

If I change Text Variable A: to S: AUTOPILOT ALTITUDE LOCK VAR, Feet, there is no readout.

Admittedly, I don't understand what A: , P: , E: and S: variables are. I know what B,H,K & L are but not the others and I could find no explanation in the manual.

Edited May 8, 20242 yr by toby23

25 minutes ago, toby23 said:

I could find no explanation in the manual.

All variable types except for S: are those from the MSFS SDK documentation. They are not assets of AAO. 
"S:" is a special type that allows you to type actual RPN code into the box which will be processed by AAO.

See MSFS RPN specification, there is a section about the variable types: Reverse Polish Notation (flightsimulator.com)

25 minutes ago, toby23 said:

If I change Text Variable A: to S: AUTOPILOT ALTITUDE LOCK VAR, Feet, there is no readout.

That is not how this works. You will have to format the variable as an RPN string, see MSFS RPN spec above and the AAO manual. 
That S: script would look something like this (not tested, off the top of my head, but this should place a comma in the right spot)
(A:AUTOPILOT ALTITUDE LOCK VAR, Feet) 1000 < if{ %(A:AUTOPILOT ALTITUDE LOCK VAR, Feet)%!03d! } els{ %(A:AUTOPILOT ALTITUDE LOCK VAR, Feet) 1000 / flr%!d! ',' scat %(A:AUTOPILOT ALTITUDE LOCK VAR, Feet) 1000 mod %!03d! scat }

25 minutes ago, toby23 said:

The multiplier only adds or removes 0's, it doesn't add a ','.

Sorry, I don't understand what you mean. A multiplier of 0.001 should divide the value by 1000. With 3 decimals that should result in your intended display?

Edited May 8, 20242 yr by Lorby_SI

23 minutes ago, Lorby_SI said:

All variable types except for S: are those from the MSFS SDK documentation. They are not assets of AAO. - UNDERSTOOD
"S:" is a special type that allows you to type actual RPN code into the box which will be processed by AAO.

See MSFS RPN specification, there is a section about the variable types: Reverse Polish Notation (flightsimulator.com) - I HAVE BEEN PUTTING THAT OFF BUT THANKS

That is not how this works. You will have to format the variable as an RPN string, see MSFS RPN spec above and the AAO manual. 
That would look something like this (not tested, off the top of my head) - THANK YOU, THIS HELPED ME FIGURE OUT HOW TO DISPLAY CURRENT ALT WITH A COMMA USING: 

(A:INDICATED ALTITUDE, Feet) 1000 < if{ %(A:INDICATED ALTITUDE, Feet)%!03d! } els{ %(A:INDICATED ALTITUDE, Feet) 1000 /%!d! ',' scat %(A:INDICATED ALTITUDE, Feet) 1000 mod %!03d! scat }

(A:AUTOPILOT ALTITUDE LOCK VAR, Feet) 1000 < if{ %(A:AUTOPILOT ALTITUDE LOCK VAR, Feet)%!03d! } els{ %(A:AUTOPILOT ALTITUDE LOCK VAR, Feet) 1000 /%!d! ',' scat %(A:AUTOPILOT ALTITUDE LOCK VAR, Feet) 1000 mod %!03d! scat }

Sorry, I don't understand what you mean. A multiplier of 0.001 should divide the value by 1000. With 3 decimals that should result in your intended display?

-> Neither of these options will add a comma. The plugin doesn't have the option to add a "thousands" character. - OK, THIS IS WHAT I WAS AFTER, THANKS
You may have to use three different text definitions, one for the numbers in front of the comma, another with only the comma, and finally one with the digits after the comma. 

 

Edited May 8, 20242 yr by toby23

10 minutes ago, toby23 said:

- THIS DISPLAYS 10,000 WHICH IS NOT THE ACTUAL ALTITUDE. I DON'T UNDERSTAND THE FORMULA BELOW ENOUGH TO FIGURE OUT WHY.

It displays the selected altitude, like you requested? Check the code again, I've added a flr command to make it round correctly)

Be mindful that in MSFS these AP variables are indexed. There isn't just the one (A:AUTOPILOT ALTITUDE LOCK VAR, Feet), there are several
(A:AUTOPILOT ALTITUDE LOCK VAR:0, Feet)
(A:AUTOPILOT ALTITUDE LOCK VAR:1, Feet)
(A:AUTOPILOT ALTITUDE LOCK VAR:2, Feet)
(A:AUTOPILOT ALTITUDE LOCK VAR:3, Feet)

depending on which AP "slot" you are using.

Aircraft Autopilot/Assistant Variables (flightsimulator.com)

(note the "See alt_mode_slot_index for more information." remark in the spec)

Edited May 8, 20242 yr by Lorby_SI

I figured it out, thank you again 🙂

@Lorby_SI , I just wanted to thank you again for your help. I was able to create a full Autopilot page with custom images, Rotary Encoders and push/tap actions thanks to you. I will be sharing my work, which will be for GA flights for people just looking for a simple profile to control Autopilot, Cameras and (when I figure out how) Radios.

Thank you