gaab

Thanks Ben, Any ETA ? Gérard

No, The "use for" is just not existing and would be of very poor interest compared to the input needed. Most of the profiles available have a pdf documentation... Cheers Gérard

Hi Ben, It seams that I have another backward compatibility problem. In LED section, I get this Seams to be linked the L:Vars only ... and only at "check variable integrity", because the LED are lighting as expected. EDIT : deleting the LED conditions and recreating sems to fix the error message, by suppressing the ", Bool" ... EDIT 2: All LED condition with A:Vars use the format (A:XYZ, unit). So, should I keep the ", Bool" for L:Vars ??? Please help... before I make further updates. Cheers,

Hi Ben, In a old thread about this ">" question you answered Easy to fix with Notepad++, but maybe the Import Configurator function should take care of it ??? Just a suggestion for people afraid to tweak the json files (and you don't like it either...) Cheers, Gérard

Ben, Sorry to bring another topic, but I keep getting configuration issue when using "old" (working) profiles : the ">" is no more recognised with the new bridge I get it for all the >K: (and >L:) variables... Cheers Gérard

Hi Ben, My reference is this one Units Of Measurement And if you try "Pounds per square foot" for ENG OIL PRESSURE, you will get an error in ContentError.txt file. More interesting, if you look at "GENERAL ENG OIL PRESSURE:index" you will see the unit listed as Psf ! I did not try the Helicopter Specific Variable... So, once more, we can see inconsistencies on LM officiai documentation... Have fun ! Cheers, Gérard

Hi Ben, I regularly cross-check using the official Learning Center of LM (V5) - "Pound-force per square foot" is listed in the list of units (as well as Psf), but not "Pounds per square foot" And there is no such unit as - PSI scalar 16K Just to clarify... Gérard

Hello Ben, I want to let you know I had difficulties to install the latest version of the configurator. The uninstall does not delete the old version and the installer does not overwrite it. I had to manually remove the old folder to get the last version. I was "alerted" by the About displaying 2.0 (now shows 2.1, at last...) Nota : the Bridge was correctly updated and the Aerosoft Updater reported that BUT the updater don't take care of the Configurator ! Hope this can help other users. EDIT : Sorry to let

Can't wait I was coming to the conclusion that I need multiple press... Thanks Gérard

Thanks Ben, On some "advanced" aircraft the Autopilot is managed by local variable booleans - in order to use the corresponding button on the Bravo, we need to have something like (L:Switch, bool) ! (>l:Switch, bool) You convinced my to read and reread this thread ;), and I discovered it was possible to use a variable assignement inside conditions , and found a solution which needs to create 2 conditions for the APMaster "toggle" "Conditions": [ { "Variable": "L:ApMaster", "Value": "1", "

Hi Ben, Still asking questions Is it (or will it be) possible to assign a L:Var value in a PressEvent, instead of a fixed value : "PressEvent": [ { "Variables": [ { "Variable": "L:ApRudderServoOn", "Value": "1", Would like to assign L:MyVar, number "VariableIsCustom": true } the objective being to have a ApRudderServoOn toggle Thanks Gérard

Hi Ben, Could you give us more information about L:Vars Incr/Decr - I would like to use this kind of facility for some aircraft (not PMDG). Thanks Gérard

Great - thanks Dave ... and the driver team Gérard

Hi, Axis support through P3D for the Yoke made sense (I can't imagine a different configuration for them !) But now with the Bravo, the 6 axis configuration can change from one aircraft to another and it becomes tedious to separately load a Yoke profile, a Throttle profile, and after in P3D startup screen a P3D configuration file ! A minimalist solution would be to associate for an aircraft these 3 config profile in a single "configuration set". But the best would be allow axis configuration for each device (one day we should get also a rudder pedal ...)

Hi Ben, Thanks for your feedback Gérard