pegeka

Hi Funatic, Yes everything is working now, fault was on my side in naming the script group with a -, after replacing the - with _ all went smooth sailing again :) Thanks for response en thanks for great interface with XTouch gauge, daily user here.

Yes I made a script group for my 'INI' files, just for my own use, with a wrong name convention. I've never published any scripts.

I think you pointed me in the right direction, I seems to work ok now after some renaming of scripts :) Thanks for your quick response! And thanks again for a great tool I use everytime I 'fly' :)

It is when I try to manage/add an automated script in the app it does not load/respond to my request. Maybe there is a bottleneck? These scripts do have a "-" in the name so maybe that's the culprit....

I use Behringer xtouch mini as an interface / input device to operate msfs. https://flightsim.to/addon/38162/x-touch-mini-gauge-for-use-with-aao-axis-and-ohs I use the option to show the gauge for the xtouch mini that are implemented in your software to show the function of the different buttons on mij screen or on my ipad via web connection. Now with the latest update I do see the gauges, but they stay empty, where normally every button shows it's function.

Hi Lorby, I just updated to v 4.57 and now my web FIPS and desktop FIPs stay empty, has something changed? This is with Touch Mini, 4.56 works ok with same settings. thanks

I can use the LVars quoted above to dial in the altitudes in the plane. What I meant is that you don't need to dial them in yourselve when using simbrief to load the route.

Flight altitude dec 38 (>L:VC_Air_Systems_trigger_VAL, number) Flight altitude inc 39 (>L:VC_Air_Systems_trigger_VAL, number) Land altitude dec 40 (>L:VC_Air_Systems_trigger_VAL, number) Land altitude inc 41 (>L:VC_Air_Systems_trigger_VAL, number) But in my experience if you load via Simbrief these are set automatically.

If you mean the LED on the xTouch; this is my setting for the LED: ext power 1: (L:switch_08_b, Number) 1 == alternative to this is: (L:switch_08_b, Number) 0 > Ext power 2 LED: (L:switch_07_b, Number) 1 == Scripts for 777 are on flightsim.to https://flightsim.to/file/78016/streamdeck-xl-and-sd-profile-for-pmdg777-300-incl-compl-script-package-aao Ext power primary switch set: 800 1 + (>K:ROTOR_BRAKE) Ext power secondary switch set: 700 1 + (>K:ROTOR_BRAKE) prim + sec toggle: 800 1 + (>K:ROTOR_BRAKE) (WAIT:2000) 700 1 + (>K:ROTOR_BRAKE)

Hi Lorby, Today I tried the copy from the grey box, as you state above, and spaces still keep dots in them. I think it's since v 4.50?