Dx shift
-
Hi, could someone take me step by step to teach me how to use the dx shift, or point me towards a thread that does so
Please -
DX, 8 devices, 32 ‘buttons’ for each device.
Numbered (in BMS) 0-31, 32-63, 64-95, etc. up to 255 …. 256 total DX ‘buttons’ … 8 x 32.
Shift creates a ‘virtual’ device for each of the 8 devices (at most). The shift ‘buttons’ are:
Device1 256-287; Device2 289-319, etc. (assuming I’ve counted correctly).
The shift command is: SimHotasPinkyShift
You add that command to a button … say your pinky button. That command has dual purpose. On short press it acts as an F16 Pinky Button … increase FOV on TGP/FCR/MAV WPN etc. When held is ‘shifts’ all devices to the virtual shifted layer. When released you return the unshifted device layer (buttons 0 - 255)
What ever button you assign that command to, you must DUPLICATE the command on the same button in the shift layer.
So if you put the shift command on button #0, you must also put the shift command on button #256.
In your config file there are two variable lines. One for the amount of offset between the ‘normal’ numbers and the shifted numbers. By default that should be 256:
set g_nHotasPinkyShiftMagnitude 256 // Enable DirectX Shifting and specify button offset
The other is the amount of time that defines a ‘short’ press, which I can’t seem to find at the moment (maybe it was removed from config?). I think it defaults to 200 or 250 miliiseconds … in other words, tap the pinky for less than that and you get the ‘pinky’ function for whatever mode or sensor is active.
Once the above is done (shift command on the same button in both layers, confirm the 256 offset in the bms config file and set the ‘tap time’) you can assign and execute commands for all your devices on their respective ‘shift layer’ buttons.
-
Worth checking out this manual: x:\Falcon BMS 4.33 U1\Docs\Key Files & Input\BMS Key File Manual.pdf
Also Kolbe’s Keyfile Editor and it’s associated documentation:
x:\Falcon BMS 4.33 U1\Docs\Key Files & Input\BMS Key File Editor.xls
x:\Falcon BMS 4.33 U1\Docs\Key Files & Input\BMS Key File Editor Manual.pdf
-
Hi Agave Blue
Your excellent reply demonstrates once again to me how little I know about coding, shifting and using Config etc.
I wonder if I’m alone in the BMS community?
For example, “8 devices”……what?
I know, I’m a lost cause!
I’m reluctant to have a go, for fear that I’d make a mistake and be unable to rectify it.
I’ll study, once again, the links you include.
Is there a video which explains the step by step road to “shift heaven”?Regards,
Bayonet.
-
Hi Agave Blue
Your excellent reply demonstrates once again to me how little I know about coding, shifting and using Config etc.
I wonder if I’m alone in the BMS community?
For example, “8 devices”……what?
I know, I’m a lost cause!
I’m reluctant to have a go, for fear that I’d make a mistake and be unable to rectify it.
I’ll study, once again, the links you include.
Is there a video which explains the step by step road to “shift heaven”?Regards,
Bayonet.
Each ‘button pushing DX thing’ you connect to control BMS is a ‘device’.
Typically:
-
Stick
-
Throttle
(Sometimes combined as one HOTAS) -
MFD’s
-
Rudders
-
Keypads
-
ICPs
-
etc.
Windows allocates to each single device 32 ‘DX buttons pushing slots’, hence the numbering …… device#1 has buttons 0-31; device#2 has buttons 32-63; device #3 has buttons 64-95, etc. … up to device#8 with buttons 224-255. Like so:
-
-
Another thought:
If you can’t create or modify your own keyfile (outside of the BMS Setup GUI) and add/edit DX commands in that keyfile, worrying about ‘shift’ is putting the cart before the horse.
Learn those first …. modify the keyfile key binds; add/edit DX command assignments. THEN worry about how to add the shift.
-
Understood, thanks again.
Bayonet.
-
Question regarding DX keystrokes and HOTAS programming… if I have a separate USB stick and USB throttle, so two different hardware devices not linked together, is it possible to use the pinkyshift button on the stick to activate a shift-function on the throttle?
In my case we’re talking about two separate converted FLCS and TQS uses two Arduino Micro’s with MMJoy2 firmware that will act as two independent USB HID devices.
-
An active shift command on ANY single device, lifts ALL devices to the shift state.
IOW, yes. That’s exactly how I do it. My pinky shift is on the stick. I press it to use a shifted command on the throttle.
-
Hi Agave Blue
Your excellent reply demonstrates once again to me how little I know about coding, shifting and using Config etc.
I wonder if I’m alone in the BMS community?
For example, “8 devices”……what?
I know, I’m a lost cause!
I’m reluctant to have a go, for fear that I’d make a mistake and be unable to rectify it.
I’ll study, once again, the links you include.
Is there a video which explains the step by step road to “shift heaven”?Regards,
Bayonet.
LMAO No, you are definitely not alone. I’m just now getting my head wrapped around the concept of callbacks rather than alphanumeric button assignments. My next big hurdle is making changes in the keyfile editor without screwing the pooch. Wish me luck!!!:rofl::rofl:
-
Backups are essential at this point!