Mal&Ind button opens canopy
-
Hi folks
I am trying to solve a problem which keeps puzzling me. When I push the Mal&Ind Lights test button, the canopy opens. I have no idea what is causing this behaviour. Anyone out there who is experiencing the same problem or better yet, has a solution?
Any help ist greatly appreciated.
Bikeman -
Hi folks
I am trying to solve a problem which keeps puzzling me. When I push the Mal&Ind Lights test button, the canopy opens. I have no idea what is causing this behaviour. Anyone out there who is experiencing the same problem or better yet, has a solution?
Any help ist greatly appreciated.
BikemanWhat Block F-16?
-
Are you clicking the cockpit button with the mouse, or are you pressing a keyboard combination, or a joystick button mapped to a keyboard combination, or a joystick button with that input assigned to its directx output…
Most obvious problem would be if its due to input issues like a shifted layer being applied when it shouldnt.
-
I haven’t paid attention to the block the problem occurs in. It feels like in all blocks. I can positively confirm the behaviour in a F-16B-15 (BMS 4.34 training mission TR_BMS_01_GroundOPS.
-
The keyboard shortcut is F3 for SimMailIndLights. The cockpit opens both when I press the keyboard key F3 and when I push the cockpit button MAL&IND Lights with the mouse. The canopy open is keyboard Alt-Shift-V and close is Ctrl-Alt-V.
-
Since you gave a very specific example that was easily tested I got into the Ground Ops TE and tried to duplicate this problem. Sorry but either your .key file or your install is borked. I put the canopy down and waited for it to finish and lock then I held the Mal&Ind button down. Both done via mouse button press. I let the voice warning indications run all the way through. The canopy never moved.
-
Bikeman, On my keyfile MalInd is _shift_F3 and canopy is control+c. I just confirmed that on my keyboard print out and in the 4.34 UI. My point is that it’s very easy to get a keyfile messed up. What keyfile are you using? IS it one you’ve modified? Is it from 4.34?(assuming you’re flying that)
Here’s my advice…Quick Fix- go into the UI and load the Full keyfile. Se what that does
Best Fix- go into x/falcon bms 4.34/user/config and find your keyfile . In my install it’s the second thing on the list. If it’s a modified one, it’s whatever you named it(ex:Airwolf.key) Pull that up to your desktop.
Then, in a separate window pull up a clean 4.34 “full” keyfile. have them side by side on your desktop.
Go into “your” keyfile and delete every callback regarding MalInd and the canopy. Be aware that there can be 2 or more callbacks for each.
Then, copy and paste the callbacks for Malind and the canopy from the “clean” Full keyfile to yours, and save the changes.
See what that does. -
tnx guys for your help. I hope I’ll get around to trying your suggestions over the weekend. Right now it’s just too darn hot to fly
-
Hi folks
After a lot of trial and error it turned out to be my Helios cockpit emulation software which I am using on a touchscreen monitor (https://github.com/Gadroc/helios). For some reason the Mal&&Ind button fired the cockpit open callback. Activating the option “bypass cascading triggers” on the Mal&Ind button solved the problem.
Bikeman
-
Glad to hear it. That was a strange one.