Keyfiles - again!
-
I never asked for help. I asked what functions would be lost. You shot your mouth off without providing a relevant answer. You’re wasting everyone’s time with ambiguous uninformative posts.
-
Asking for info is asking for help. Figure it out for yourself.
-
Your first response essentially said “figure it out for yourself” so why are you continuing to waste your breath? FFS people in the sim community drive me insane sometimes. If you don’t want to give info then don’t waste everyone’s time with a useless post.
-
I use the precision slider for the speedbrakes so DX won’t work there–I have to use the SST program for that. HOTAS-only functions (as in what’s in the real Viper) haven’t changed from 4.32 to 4.33 have they? I just went though the -1 and assigned HOTAS functions to the X52 as close to real-life placement as I could.
If you used the HOTAS commands then you will be fine. Its the arcade style callbacks that are in danger, like cycling through AA/AG weapons for instance.
-
well, copy pasting the DX assignments, then going through them individually looking for changed callbacks with reference to the manual so generously provided for that specific purpose, is what I did. Took the blank keyfile included in the install and copied my DX assignments into it.
I had to disable my shift button through the bms cfg to get it to work as well.
The speed brakes directX has not changed. If you set it up with directX that should not have needed changing.
When I say depending on keyfile, its because the default keyfile in BMS that so many used, used old and dated callbacks, a number of which are no longer working in 4.33 - and if your DX assignments included those, then they plain wont work. If you used a nonstandard keyfile such as those developed by Kolbe (and which are now default in 4.33), then you wont have to worry about that.
+1
That is what I did. Its easy and took about an hour to do 200+ buttons. -
+1
That is what I did. Its easy and took about an hour to do 200+ buttons.My hardest point was working out which set of keyboard scancodes I needed to use… ended up coping Set 3 scancodes into it and having problems XD
On rereading that section, I see Kolbe did actually say that it uses XT scancodes… I just didnt put XT together with Set 1 mentally. Whoops! Problem all sorted now… I only have like 5 keypresses in my keyfile. Its almost entirely directX.
On that note, the new spotlight feature for night starts is great! I kinda feel like it should be a small torchlight though, maybe that follows the mouse?
-
Mine is 100% DX. Any keystrokes (I think I have 2) are handled by my CH MFP’s. Those command names are left blank in the keyfile.
-
yeah, I need the keyboard for a few things. Like the spotlight for example. And my ICP/numpad. And my buttons to change views. I dont forsee myself ever having a keyfile which is only DX.
-
DX callback if you need it for your HOTAS
SimSpotLight -1 0 0x1F 1 0 0 1 “CKPIT: Spotlight - Toggle”
-
Thanks, but its not on my HOTAS by choice. Its not a button on the real SSC so its not a button on my HOTAS. Ive mapped it to “S” in my keyfile already. I note you’ve pasted the keyboard line rather than the DX line too?
-
Spotlight isn’t a clickable cockpit button/switch/rotary?
-
Not to my knowledge? It doesnt simulate an actual cockpit light. The point is that it lets you light up the cockpit enough to start it, before the actual cockpit floodlights work. RL pilots often use a torch for this purpose on night starts.
-
I note you’ve pasted the keyboard line rather than the DX line too?
Ooops
The second part
SimSpotLight 6 -1 -2 0 0x0 0 -
Not to my knowledge? It doesnt simulate an actual cockpit light. The point is that it lets you light up the cockpit enough to start it, before the actual cockpit floodlights work. RL pilots often use a torch for this purpose on night starts.
Right. My mistake. I was thinking floodlight.
-
It does simulate an actual cockpit light on an articulated stalk behind and to the right of the pilot iirc.
-
It does simulate an actual cockpit light on an articulated stalk behind and to the right of the pilot iirc.
Apparently so! Didnt know that; apparently there is the utility light on the stalk behind and to the right of the pilot, and spotlights on the left and right under the glareshield as well. I stand corrected!
Seems they are powered by the battery bus No.1, while the normal floodlights are powered by the nonessential AC bus No.2 - the former having power as soon as the MAIN PWR switch is moved to BATT or MAIN PWR, while the latter needs a generator running. Hmm. Says in the dash that the standby generator has power available whenever the ADG is rotating, such as for example during a ramp start after the JFS light illuminates. Doesnt flood lighting take longer than that to come on in BMS?
-
Wing Fold
AFWingFoldToggle -1 0 0x11 1 0 0 1 “CKPIT: Wing Fold - Toggle”
AFWingFoldUp -1 0 0XFFFFFFFF 0 0 0 1 “CKPIT: Wing Fold - Up”
AFWingFoldDown -1 0 0XFFFFFFFF 0 0 0 1 “CKPIT: Wing Fold - Down”Thrust Reverse
AFTriggerReverseThrust -1 0 0x14 4 0 0 1 “FCTRL: ENGINE - Togg. Thrust Reverser”
All found in the BMS - Full keyfile. Hope this helps
Thanks Tiffy.
Do I then:
- copy & paste these lines into my keyfile
- then go into the UI to see what key presses are allocated
- resolve any conflicts with what I’ve assigned in my 4.32
Are there in in fact also cockpit switches that can be used for wing fold and Thrust reverse?
@Kolbe
Sorry! I was just so frustrated faced with a new jar of sweets unable to open them properly! And I can’t face the stress of porking Falcon if I try and use a tool without really understanding it.The SimSpotlight command was in my old keyfile with no assigned key, so I used Foxy to find a spare and then allocated one in the UI.
-
Once you paste these lines into your keyfile and reload it in bms, you’ll be able to scroll to the CKPIT section in the key list and assign buttons and / or keys to these functions.
HTH
Uwe
-
The SimSpotlight command was in my old keyfile with no assigned key, so I used Foxy to find a spare and then allocated one in the UI.
Hmm. I had thought it was a feature new to 4.33.
-
When I say depending on keyfile, its because the default keyfile in BMS that so many used, used old and dated callbacks, a number of which are no longer working in 4.33 - and if your DX assignments included those, then they plain wont work. If you used a nonstandard keyfile such as those developed by Kolbe (and which are now default in 4.33), then you wont have to worry about that.
I thought the style of the keyfile shown in the setup section looked familiar. I use/used one of Kolbe’s keyfiles in 4.32. However, I’ve decided to use the full keyfile that came with 4.33, which means I’ll have to completely reassign all stick, TQS, and MFD buttons.