BTW: New and improve Airfoil Labs C172 DIGITAL led annunciators (w/exception of OIL PRESS), assuming my bravo isn't just plain scrambled...   "LEDs": [     {       "ByteIndex": 1,       "BitIndex": 0,       "ConditionLogic": "OR",       "Conditions": [         {           "Condition": "sim/cockpit2/autopilot/heading_status",           "ConditionValue": "=1",           "ConditionIsCustom": true         },         {           "Condition": "sim/cockpit2/autopilot/heading_status",           "ConditionValue": "=2",           "ConditionIsCustom": true         }       ]     },     {       "ByteIndex": 1,       "BitIndex": 1,       "ConditionLogic": "OR",       "Conditions": [         {           "Condition": "sim/cockpit2/autopilot/nav_status",           "ConditionValue": "=1",           "ConditionIsCustom": false         },         {           "Condition": "sim/cockpit2/autopilot/nav_status",           "ConditionValue": "=2",           "ConditionIsCustom": false         }       ]     },     {       "ByteIndex": 1,       "BitIndex": 2,       "ConditionLogic": "OR",       "Conditions": [         {           "Condition": "sim/cockpit2/autopilot/approach_status",           "ConditionValue": "=1",           "ConditionIsCustom": false         },         {           "Condition": "sim/cockpit2/autopilot/approach_status",           "ConditionValue": "=2",           "ConditionIsCustom": false         }       ]     },     {       "ByteIndex": 1,       "BitIndex": 3,       "ConditionLogic": "OR",       "Conditions": [         {           "Condition": "sim/cockpit2/autopilot/backcourse_status",           "ConditionValue": "=1",           "ConditionIsCustom": false         },         {           "Condition": "sim/cockpit2/autopilot/backcourse_status",           "ConditionValue": "=2",           "ConditionIsCustom": false         }       ]     },     {       "ByteIndex": 1,       "BitIndex": 4,       "ConditionLogic": "OR",       "Conditions": [         {           "Condition": "sim/cockpit2/autopilot/altitude_hold_status",           "ConditionValue": "=1",           "ConditionIsCustom": false         },         {           "Condition": "sim/cockpit2/autopilot/altitude_hold_status",           "ConditionValue": "=2",           "ConditionIsCustom": false         }       ]     },     {       "ByteIndex": 1,       "BitIndex": 5,       "ConditionLogic": "OR",       "Conditions": [         {           "Condition": "sim/cockpit2/autopilot/vvi_status",           "ConditionValue": "=1",           "ConditionIsCustom": false         },         {           "Condition": "sim/cockpit2/autopilot/vvi_status",           "ConditionValue": "=2",           "ConditionIsCustom": false         }       ]     },     {       "ByteIndex": 1,       "BitIndex": 6,       "ConditionLogic": "OR",       "Conditions": [         {           "Condition": "sim/cockpit2/autopilot/speed_status",           "ConditionValue": "=1",           "ConditionIsCustom": false         },         {           "Condition": "sim/cockpit2/autopilot/speed_status",           "ConditionValue": "=2",           "ConditionIsCustom": false         }       ]     },     {       "ByteIndex": 3,       "BitIndex": 6,       "ConditionLogic": "",       "Conditions": [         {           "Condition": "C172/g1000/alert_OIL_PRESSURE",           "ConditionValue": "=1",           "ConditionIsCustom": true         }       ]     },     {       "ByteIndex": 2,       "BitIndex": 6,       "ConditionLogic": "AND",       "Conditions": [         {           "Condition": "C172/g1000/alert_type",           "ConditionValue": "=1",           "ConditionIsCustom": true         }       ]     },     {       "ByteIndex": 2,       "BitIndex": 7,       "ConditionLogic": "AND",       "Conditions": [         {           "Condition": "C172/g1000/alert_type",           "ConditionValue": "=2",           "ConditionIsCustom": true         }       ]     },     {       "ByteIndex": 3,       "BitIndex": 1,       "ConditionLogic": "",       "Conditions": [         {           "Condition": "sim/cockpit/autopilot/autopilot_mode",           "ConditionValue": "=2",           "ConditionIsCustom": false         }       ]     },     {       "ByteIndex": 3,       "BitIndex": 2,       "ConditionLogic": "OR",       "Conditions": [         {           "Condition": "C172/g1000/alert_LOW_FUEL_L",           "ConditionValue": "=1",           "ConditionIsCustom": true         },         {           "Condition": "C172/g1000/alert_LOW_FUEL_R",           "ConditionValue": "=1",           "ConditionIsCustom": true         }       ]     },     {       "ByteIndex": 3,       "BitIndex": 4,       "ConditionLogic": "",       "Conditions": [         {           "Condition": "sim/flightmodel2/engines/starter_is_running:0",           "ConditionValue": "=1",           "ConditionIsCustom": false         }       ]     },     {       "ByteIndex": 3,       "BitIndex": 5,       "ConditionLogic": "",       "Conditions": [         {           "Condition": "C172/g1000/alert_LOW_VACUUM",           "ConditionValue": "=1",           "ConditionIsCustom": true         }       ]     },     {       "ByteIndex": 3,       "BitIndex": 7,       "ConditionLogic": "",       "Conditions": [         {           "Condition": "sim/cockpit/engine/fuel_pump_on",           "ConditionValue": "=1",           "ConditionIsCustom": true         }       ]     },     {       "ByteIndex": 4,       "BitIndex": 0,       "ConditionLogic": "AND",       "Conditions": [         {           "Condition": "C172/cockpit/parkingBrake",           "ConditionValue": "=1",           "ConditionIsCustom": true         }       ]     },     {       "ByteIndex": 4,       "BitIndex": 1,       "ConditionLogic": "AND",       "Conditions": [         {           "Condition": "C172/g1000/alert_LOW_VOLTS",           "ConditionValue": "=1",           "ConditionIsCustom": true         }       ]     }   ],  

I recently got a Bravo throttle quadrant and the Airfoil Labs C172 throttle quadrant profile.   I noticed that the anunciators seemed a bit off.  Master warning didn't light up, parking brake on showed as something else, etc.   Yet, when I went into the honeycomb configurator, all the xplane 12 datarefs seemed to be mapped to the right annunciators.   I got tired of this and started mapping the byteindex and bitindexes from BFC_Throttle_Config.json and here is what I wound up with:   (Note that I tried the Christmas Tree app (https://forum.aerosoft.com/index.php?/files/file/6080-honeycomb-bravo-throttle-christmas-tree-application/) and it in no way reflects what I came up with below.  Not even it can light up the oil press light!)   TOP ROW   HDG  NAV  APR  REV  ALT  VS   IAS             AUTOPILOT 1/0  1/1  1/2  1/3  1/4  1/5  1/6             3/1     MIDDLE ROW   WARN  FIRE  OIL   FUEL  ICE   START APU 2/7   3/0   ???   3/2   3/3   3/4   4/3   BOTTOM ROW   CAUT  VAC   HYD   PUMP  PB    VOLT  DOOR 2/6   3/5   3/6   3/7   4/0   4/1   4/2     LANDING GEAR   L-G  2/0 L-R  2/1 N-G  2/2 N-R  2/3 R-G  2/4 R-R  2/5     I still haven't figured out the ByteIndex and BitIndex of the OIL PRESS annunciator.  I also think I have some other switches and detents that aren't triggering, and my lever 1 TOGA button seems to be shorted ON.   I can't therefore figure out if my Bravo throttle quadrant is miswired in some way, has a bad firmware, whether I have a different hardware rev where the annunciators moved around, or whether the honeycomb configurator software just has no idea which annunciators are wired to which bitindexes.   Do the numbers above agree with everyone else's config or is mine the odd one out.  And does anyone know which byteindex/bitindex the OIL PRESS annunciator is wired to?        

Thank you for your efforts but again these are for MSFS 2024, not for MSFS 2020

Danke sehr. Ich werde es morgen versuchen. Heute ist mein Kopf von der Installations und Einrichtungsorgie leer.

Hello, can the Piper Cheyenne for FSX, article number AS10617, still update the navigation database with Navigraph?   thanks christian

During the daytime the EFB seems to dim for me and difficult to see.  I found the EFB brightness control and turned it up to 100%, but even then the EFB is still too dim.  Is there an auto-dim setting that I am missing?  If there a .cfg file or something that I can edit to increase the EFB brightness? New Bitmap Image.bmp

Hi, hast Du das neue Update zum RC1 ausprobiert?

Hier die Änderungen:   Aircraft Airbus A330-300     Fixed an issue where the EQUI-TIME POINT page wasn’t clearing the previous text correctly when updating ETP data (XPD-17729) Piper PA-18 Super Cub     Fixed an issue with the audio panel where the radio transmission couldn’t be heard Beechcraft Baron 58     Fixed an issue with the weather radar where some returns were drawn outside the map area ATC     Fixed an issue where nearby ATIS frequencies were missing from the ATC window Graphics     Fixed an issue where Vsync was not working as expected (XPD-17762) Scenery     Slightly improved decals around roads     Adjusted runway centerline light brightness Systems     Fixed an issue where dataref sim/cockpit2/electrical/APU_starter_switch wasn’t set correctly when trying to start the APU (XPD-17761) VR     Fixed a crash when resizing windows in VR (XPD-17763) User Interface & Controls     Updated translations   Und die Übersetzung:   Flugzeuge Airbus A330-300 Ein Fehler wurde behoben, durch den die Seite „EQUI-TIME POINT“ den vorherigen Text beim Aktualisieren der ETP-Daten nicht korrekt löschte (XPD-17729). Piper PA-18 Super Cub Ein Fehler im Audiopanel wurde behoben, durch den die Funkübertragung nicht hörbar war. Beechcraft Baron 58 Ein Fehler im Wetterradar wurde behoben, durch den einige Echos außerhalb des Kartenbereichs angezeigt wurden. Flugverkehrskontrolle Ein Fehler wurde behoben, durch den nahegelegene ATIS-Frequenzen im Flugverkehrskontrollenfenster fehlten. Grafik Ein Fehler wurde behoben, durch den Vsync nicht wie erwartet funktionierte (XPD-17762). Szenerie Die Decals um die Straßen wurden leicht verbessert. Die Helligkeit der Startbahnmittellinienbeleuchtung wurde angepasst. Systeme Ein Fehler wurde behoben, durch den dataref sim/cockpit2/electrical/APU_starter_switch beim Starten der APU nicht korrekt eingestellt war. (XPD-17761) VR Absturz beim Ändern der Fenstergröße in VR behoben (XPD-17763) Benutzeroberfläche & Steuerung Übersetzungen aktualisiert

Hallo Stefan,   hier die Infos aus der simHeaven-FAQ, damit sollte es zumindest mit der Alternative 2 klappen:   Der Text wurde vom Google-Translator übersetzt, das Original findest du hier: https://simheaven.com/faq/   Mac/Linux: navigieren zu “X-Plane 12/Custom Scenery/simHeaven_X-World_Vegetation_Library” Öffnen Sie das Terminal, führen Sie diese Befehle aus (PATH-TO-X-Plane-12 muss angepasst werden😞 $ cd / PATH-TO-X-Plane-12 /Custom\ Landschaft/simHeaven_X-World_Vegetation_Library $ ln -sf “.. /.. /Ressourcen/Standard\ Landschaft/1200\ Wälder“ “1200\ Wälder” Sie sollten einen neuen Ordner "1200 forests" in diesem Verzeichnis sehen Wenn Sie das PATH-TO-X-Plane-12 nicht kennen, öffnen Sie den FINDER und navigieren Sie zu X-Plane 12, berühren Sie diesen Ordner mit der Maus und ziehen Sie ihn an das Terminal, Sie sollten so etwas wie „/Users/yourname/Documents/.../X-Plane\ 12/“ sehen. Alternative 1: Sie könnten sich ein ordentliches kleines Programm namens „SymbolicLinker 2.2“ ansehen. Es ist kostenlos und macht es, sobald es installiert ist, das Erstellen eines Links extrem einfach. Alternative 2: Sie können auch manuell „1200 forests“ von „X-Plane 12/Resources/default scenery/“ in „X-Plane 12/Custom Scenery/simHeaven_X-World_Vegetation_Library/“ kopieren, aber es ist besser, den Link einzustellen, der die Vegetation auf dem neuesten Stand hält und Speicherplatz spart.   VG Horst  

Hi Leute,   nachdem ich fast 2 Tage mit der Installation und Einrichten von Linux Mint 22.3 verbracht habe habe ich nun Xplane12 aktualisiert, LittleNavMap installiert und nun wollte ich simHeaven installieren. Leider funktioniert es nicht, ich scheitere am Ausführen des Mac-Linux scripts. Die Date 1000 forests erscheint einfach nicht. Ich habe zuerst die Datei simHeaven_X-Woeld_Vegetation_Library.7z im Ordner Custom Scenery entpackt und dann das Sript angeklickt. Keine forest1000. Dann die darin enthaltene Unterdatei mit selben Namen in Custom Scenery und das ganze wiederholt. Immer die Meldung:   ERROR installing the library. You are not in the correct directory. Move or symlink the folder " Tja, was mache ich falsch?