Jump to content


  • Content Count

  • Joined

  • Last visited

Everything posted by gaab

  1. 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
  2. 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,
  3. 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
  4. 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
  5. 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
  6. 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
  7. 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
  8. Can't wait I was coming to the conclusion that I need multiple press... Thanks Gérard
  9. 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", "
  10. 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
  11. 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
  12. 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 ...)
  13. Thanks for the feedback. Great job - I really appreciate the follow up you are doing on this great piece of hardware and software. Cheers Gérard
  14. I understand the idea and found it very insteresting. I borrowed this approach from one of your PMDG profile - and I saw it first on PMDG forum concerning Bravo and Reverses... I implemented it in a non-PDMG I built for a turboprop. It is why I was wondering if that could be the reason. The error is in the infamous(!) ContentError.txt which is always ON on my PC (and helped me to address a lot of XML errors in a lot of aircraft - no name I have found the reason (my error) and was able to fix it, but the configurator is partly guilty ! When creatin
  15. Looks like "INT:REV_0, bool" is not internal to the bridge and P3D dislikes it ! Error: Invalid variable (missing ':', did you forget a macro?): INT:REV_0. Is this syntax only meaningful with the "PDMG" interface ? Anyway, this could be replaced by an usual LVar.... I really start to like this Beta Throttle - and Notepad++ is my friend Gérard
  16. Hi Ben, I feel stupid - forgot to desactivate all key assignements automatically done by P3D for a new equipment Looks like this solved my problems - lesson learned Gérard
  17. Hi Ben, My usb connection is directly on the PC (replacing the old Saitek connection). Is there a log file created somewhere by the AFC ? Gérard
  18. I was using the untouched "Default_Throttle" Got several issues, the most disturbing being (I really fear a short circuit ...) - Autopilot switch = set on/off autopilot (which is OK) AND activate a "Gear_toggle" which of course does not exist - few minutes after I got a message from AFCBridge : "Woopsie! Somehow BFC_Trottle got discontected" - and ONLY the Autopilot switch was acting and continuing to maneuver the GEAR, no other switch recognized and no LED lighted - nevertheless the Axis assigned throught P3D Axis Management are still acting
  19. After several Configuration Profiles built, considering the number of switches (specially on the Bravo), it would be very useful to have a "Configuration" summary : An html file, with ONE line per Button (or LED), listing only the variable(s) and assigned value (one extra line only in case of existing Release Event), with the option to list also the unassigned buttons. Example : Elevator Trim A Up Press [K:ELEV_TRIM_UP] Elevator Trim A Down Press [K:ELEV_TRIM_DN] .... Toggle 3 ON Press [L:DC_Gen1_sw (1)] Toggle 3 OFF Press [L:DC_Ge
  20. I undertand and it's OK. Some suggestions for the configurator : - confirm that the profile as been updated (and activated). - for a next version : allow to customize the name of the buttons. For example your "Bus1 On" is my "Seat Belt Off". (could be a kind a "translation" table...) Happy new year Gérard
  21. Hi, It would be great to get a picture showing the .json button number. The Pdf supplied with the profiles makes it very difficult to understand, clone and adapt a profile for another aircraft. Question also. The button json description for the press event has - a variable zone "Variable": "", "Value": "", "Condition": "", "ConditionValue": "", "Conditions": [], "Repeat": false - and a variables array, with other contions array... "Variables": [ {
  • Create New...