-
Who's Online 682 all people including: 2 Members, 1 Anonymous, 679 Guests (See full list)
-
Recent Achievements
-
Recently Browsing
- No registered users viewing this page.
-
Posts
-
By Andre_RX85 · Posted
Ich finde Symbolische Links in Windows komplizierter. LOL Wie oben geschrieben, Linux Mint Datei Browser Nemo, zwei Fenster nebeneinander und SHIFT und STRG drücken und per Drag and Drop symbolischer Link anlegen -
Ja, mir geht es oft auch so. Aber, im vorliegenden Fall gibt es ja angenehmerweise eine Alternative, die funktioniert. Also viel Erfolg.
-
By stevebiker · Posted
Das habe ich gestern wohl falsch interpretiert. Ich war allerdings seit 2 Tagen mit fast nur dem Versuch einer erfolgreichen Installation von Linuc Mint 22.3 ausgelastet. Ich werde es nun wohl mit dem Kopieren erledigen. Aber, es ärgert mich prinzipiell, wenn etwas nicht funktioniert. Danke für dei Erklärung. -
Horst hat es einen Post früher doch beschrieben. Auch ich bin diesen Schritt gegangen MIT ERFOLG. Ich zitiere: Wo ist jetzt das Problem?
-
By stevebiker · Posted
Leider komme ich keinen Schritt weiter! Wenn ich im Terminal den Pfad angebe un den Befehl ausführe bekomme ich " Zu viele Argumente"! So kompliziert habe ich mir das Verwenden von X-plane in Linux nicht vorgestellt! Keine Ahnung ob es sich überhaupt lohnt. In Windows kann ich es mit 2 Klicks erledigen. -
Indeed, altough the unit is recognized and assignable from within MSFS2020, Honeycomb hasn't yet developed software for it. It must be configured manually by the user.
-
For the ease of reading and understanding, next time please pst the files as attachments, not embedded in the post.
-
By Dr. Software · Posted
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 } ] } ], -
By Dr. Software · Posted
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? -
By Silent Wolf · Posted
Thank you for your efforts but again these are for MSFS 2024, not for MSFS 2020
-
-
Popular Contributors
-
Forum Statistics
-
Total Topics121.9k
-
Total Posts842.1k
-
-
Files
-
