Per subject, I am unable to bind Avionics On/Off to any key switch on either the alpha or bravo.
Also unable to bind them on the keyboard.
Ironically, the MSFS version has the same issue. Think its a core sim bug…
Per subject, I am unable to bind Avionics On/Off to any key switch on either the alpha or bravo.
Also unable to bind them on the keyboard.
Ironically, the MSFS version has the same issue. Think its a core sim bug…
You might get a quicker answer on their Discord Server.
Hi, I have a method using Spad.Next and a custom event that functions fine. PM me if you have full version if Spad.Next and I will let you have the details
Would you kindly be willing to share with me too? I managed to bind most events except some lights and bus#1 & #2. I am still green at SpadNext. Thank you
I don’t have Spad but you need the following commands:
Bus1:
input the values 3 and 4 into K:2:ELECTRICAL_BUS_TO_BUS_CONNECTION_TOGGLE
If you use RPN it will look like this (dots are spaces): 3·4·(>K:2:ELECTRICAL_BUS_TO_BUS_CONNECTION_TOGGLE)
Bus 2:
3·5·(>K:2:ELECTRICAL_BUS_TO_BUS_CONNECTION_TOGGLE)
BusTie:
5·4·(>K:2:ELECTRICAL_BUS_TO_BUS_CONNECTION_TOGGLE)
Take a look at this for further explanation: Aircraft Electrical Events
I saw a post this morning about reseting the warning lights, perhaps that was from you also? Anyhow, here are the scripts. They are a bit complicated because each failure is handled on its own:
Warning reset script:
0·(>L:PropBetaFlagAlert,·Number)·1·(>L:PropBetaFlagAck,·Number)·0·(>L:TrimFlagAlert,·Number)·1·(>L:TrimFlagAck,·Number)·0·(>L:GenBusFlagAlert,·Number)·1·(>L:GenBusFlagAck,·Number)·0·(>L:BattBusFlagAlert,·Number)·1·(>L:BattBusFlagAck,·Number)
Caution reset:
0·(>L:GenFailFlagAlert,·Number)·1·(>L:GenFailFlagAck,·Number)·0·(>L:FuelPressFlagAlert,·Number)·1·(>L:FuelPressFlagAck,·Number)·0·(>L:RFuelTankFlagAlert,·Number)·1·(>L:RFuelTankFlagAck,·Number)·0·(>L:LFuelTankFlagAlert,·Number)·1·(>L:LFuelTankFlagAck,·Number)·0·(>L:RFuelFlowFlagAlert,·Number)·1·(>L:RFuelFlowFlagAck,·Number)·0·(>L:LFuelFlowFlagAlert,·Number)·1·(>L:LFuelFlowFlagAck,·Number)·0·(>L:BattHotFlagAlert,·Number)·1·(>L:BattHotFlagAck,·Number)·0·(>L:ChipDetectFlagAlert,·Number)·1·(>L:ChipDetectFlagAck,·Number)
And now we’re at it, you might as well get the sunshade script as well:
(L:MV_XMLVAR_LeftWindowShade,·Bool)·!·(>L:MV_XMLVAR_LeftWindowShade,·Bool)·AND·(L:MV_XMLVAR_RightWindowShade,·Bool)·!·(>L:MV_XMLVAR_RightWindowShade,·Bool)
The only things you can’t do with normal RPN scripts/Spad programming are opening the the Ignition switch guard and Starter switch guard. That’s handled by Bvars. You will need Axis and Ohs or Mobiflight code for that.
For SPAD.next since it doesn’t support RPN:
Create a Client Event:
DO NOT COPY-PASTE RPN CODE! The DOTS will cause it to fail. Type it out or paste it into notepad first to remove the dots before pasting it into SPAD.
In SPAD Next set BUS1 on Alpha to custom client event:
Repeat for BUS TIE and AV BUS 2:
Works GREAT
Such super response and guidance. Thank you very much!
Your response exceeded my expectations🙏
Hi, I’ve mapped almost all of the PC-6 quite similar to what’s been mentioned in this discussion (the Warnings/Cautions were a real pain).
I’ve gotten stuck on the instrument brightness knob though. It moves LVAR LIGHTING_PANEL_1_Power_Setting between 0 and 100 but setting that directly does not change the lighting.
I tried a few events and other data elements but no luck.
Hoping you’ve done the instrument lighting and can share which data/event I need?
Thanks!
I haven’t started making scripts for Porter yet (still waiting for the steamy version), but I’m pre-emptively interested in this one too.
What you are normally looking for the light knob is not LVAR, but you want to know what light potentiometer it is. Actual script would be something like (AAO):
(A:LIGHT·POTENTIOMETER:1, Percent) 10 + 100 min 1 (>K:LIGHT_POTENTIOMETER_INC)
(A:LIGHT·POTENTIOMETER:2, Percent) 10 + 100 min 2 (>K:LIGHT_POTENTIOMETER_INC)
Etc. those are increase light potentiometer 1 or 2 by 10 percent up 100% respectively. Sometimes you need to add 1 (>K:PANEL_LIGHTS_SET) or 1 (>K:GLARESHIELD_LIGHTS_SET) etc. to the script too.
Unfortunately the light potentiometer is often not available through the dev mode and you need to either guess it or look at airplane code, systems.cfg is my go-to for this, though sometimes you need to look at model/airplanename_interior.xml. Unfortunately I don’t have either of those available since I have the marketplace version and those files are encrypted, hence why I’m interested.
Aha you’re a genius, I forgot to check the files I had previously used PC6_Interior.xml to find out how to make the Warning/Caution button work.
I had assumed lights would be easy that they would only use Potentiometers 1 and 2 and originally testing those did nothing.
For some reason they chose to use #3 for main lighting & G1000, #12 for ambient, and #16 for ADF.
I’m not sure of the AAO syntax because I use SPAD but does that mean you’re incrementing by 10 and a maximum of 100?
I need to set safety limits eg 0 to 100 so I don’t go out of bounds which can cause crashes sometimes.
Looks like I don’t need to set light potentiometers #12 and #16 as setting the just the main #3 seems to manage the whole lot.
I assumed the limit would be 0 to 100 and used an increment of 10.
The cockpit knob does not move and it’s value is stored in the LVAR so I update that also - so if you click it with the mouse it will move from the same point (although the visual position of the knob doesn’t change until you click it then it jumps to the value).
This is the result if anyone wants to map it:
Thanks for giving the right pot number.
I don’t think the animations on the knobs ever work unless the developer set the knob animation in the interior.xml.