DaveM1970

@Lorby_SI is my understanding correct? How do I get the fonts working in the streamdeck? Thanks for your support.

Thanks for the clarification. So if I add other fonts to the same location, they will be in the dropdown to use? The 2 fonts mentioned above are not populating into the font selection box and I need them for my F18 buttons.

Hey guys Anyone else have issues with the SDFontsTool app? Tried adding a couple of system fonts (Algerian & MS 33558). They show in the app as AAO Plugin fonts now but on clicking APPLY & restarting the StreamDeck app from system tray, they are still not available.

Thanks again for the prompt response. I'll give that a go.

Apologies Lorbi, the above toggles have 3 states: 1 = off 2 = armed (white) 3 = captured (Green) Thanks again.

Thanks Lorby_Si - works like a charm. There are a couple of toggles though that have multiple states - is there any way of adding these states to a single toggle? The toggles are: NAV led State (L:CS_HeliSAS_Lights_Green, Number) 4 & ON value: 4 also has: NAV led State (L:CS_HeliSAS_Lights_White, Number) 4 & ON value: 4 VRT led State (L:CS_HeliSAS_Lights_Green, Number) 32 & ON value: 32 also has: VRT led State (L:CS_HeliSAS_Lights_White, Number) 32 & ON value: 32 So, the buttons once pressed should be white, and then when Nav kicks in (once it captures lock, it needs to go to green. Would that be via multigauge & if so, could you direct me how to accomplish it? There's a great video of how the HeliSAS autopilot works here: Many thanks again for your time & support - very much appreciated 🙂

Thanks again for the quick response. Yes - it is a single toggle button for each item (AP, HDg, etc). I'll try your suggestion. The CS HELI is the CowanSim HELISAS module - new Autopilot for Cowna sim Helicopters. Currently running it on The CS H125.

SOmeone who is using Mobilflight said the follwoing work in that app but I prefer AxisANDOhs and streamdeck doesnt see to work with Mobiflight. From another group: For my Mobiflight profile i configure: AUTOPILOT led state **(L:CS_HeliSAS_Lights_Green) int 1 &** HDG led State **(L:CS_HeliSAS_Lights_Green) int 2 &** NAV led State **(L:CS_HeliSAS_Lights_Green) int 4 &** SPD led State **(L:CS_HeliSAS_Lights_Green) int 8 &** ALT led State **(L:CS_HeliSAS_Lights_Green) int 16 &** VRT led State **(L:CS_HeliSAS_Lights_Green) int 32 &**

Thanks for the quick response. I think the issue is that each button can have more than 1 state/value but the variable is the same for each button. EG AP Master can have values: 1 = Autopilot Master on 3 = Autopilot Master on AND HDG On 11 = Autopilot Master, HDG AND SPD on 18 = Autopilot Master, HDG AND ALT on (SPD & ALT cancel each other out - only 1 can be used at a time) etc For 1 x toggle switch, how do I add all of the values for on and any other value = off? The same will be for other switches - they will have multiple values depending on which switches are on at the time. I can map out the different values that each button could be, but I don't know how to either script this or add to a toggle button or gauge.

Hi. I'm currently using the AxisandOhs streamdeck plugin to control aircraft in MSFS24 (A&O ver 4.55 b26 and streamdeck plugin ver 45.01). Works great - thanks LorbySi. I have an issue with the read variables for on/off functionality for the newly released SAS autopilot module for CS Helis. For each button light, they use the same variable with a different integer: Sim Variable: L:CS_HeliSAS_Lights_Green Integers: LED Mask AP 1 HDG 2 NAV 4 SPD 8 ALT 16 VRT 32 I want to create a script that checks specific LED states from the HeliSAS system via the local simvar (L:CS_HeliSAS_Lights_Green) with bitmask values for different modes (HDG, NAV, ALT, etc.) The integr can change based on which button/s are switched on. EG Autopilot on state is value 1, but when the HDG state is also on, the integer becomes 3 (1 + 2) so both lights on the toggle button go out. I tried using chatgpt and it gave me the following but I cant seem to get it to work: Example OHS Axis Script (per LED state) For each LED (say HDG), you can define a script like: // HDG LED (L:CS_HeliSAS_Lights_Green) 2 & if{ 1 } els{ 0 } Explanation: (L:CS_HeliSAS_Lights_Green) → retrieves the integer value. 2 & → performs bitwise AND with 2 (HDG’s bit). if{1} els{0} → returns 1 if active, otherwise 0. You’d repeat this for each mode, just changing the mask: AUTOPILOT → (L:CS_HeliSAS_Lights_Green) 1 & if{ 1 } els{ 0 } HDG → (L:CS_HeliSAS_Lights_Green) 2 & if{ 1 } els{ 0 } NAV → (L:CS_HeliSAS_Lights_Green) 4 & if{ 1 } els{ 0 } SPD → (L:CS_HeliSAS_Lights_Green) 8 & if{ 1 } els{ 0 } ALT → (L:CS_HeliSAS_Lights_Green) 16 & if{ 1 } els{ 0 } VRT → (L:CS_HeliSAS_Lights_Green) 32 & if{ 1 } els{ 0 } Using in Axis & OHS / StreamDeck In AxisAndOhs, create a script for each LED state with the above expressions. In the StreamDeck plugin, bind each button’s “LED logic” or “indicator” to the corresponding script. Example: HDG button uses the HDG LED script, NAV uses NAV LED script, etc. This way, your StreamDeck button will light up only if the bit for that mode is active. Would really appreciate the help. Thanks.