help! pinky switch dx shift breaks all HOTAS buttons
-
I’m not sure what happened, but now using this button - regardless of which DX button on my hotas it’s assigned to - breaks all other hotas buttons. Axes still work tho. I’ve tried deleting my setup.v.100 files and reassigning dx shift with only one other button assigned to test the shift layer, and it still breaks!
**breaks meaning all other non-shifted buttons stop working until restarting BMS. Then as soon as DX shift is used it happens again.
@airtex2019 -
@AWmk1 can you clarify “breaks all other hotas buttons”?
do you mean, your shift-layer doesn’t work … or something more severe and permanent, like all your non-shifted buttons also stop working?
-
@AWmk1 said in help! pinky switch dx shift breaks all HOTAS buttons:
**breaks meaning all other non-shifted buttons stop working until restarting BMS. Then as soon as DX shift is used it happens again.
thanks, well yeah wow that is very weird and I haven’t heard of anyone else experiencing that … really no idea where to look for clues
unless you accidentally mapped it to
SimHotasShiftLock
instead ofSimHotasShift
? -
@airtex2019
Will check that. I’ve had a number of weird problems recently and haven’t been flying for a long time, but anytime I try and get in a quick practice I have a new problem.
I think the sim is against me because it knows I’ve been unfaithful… -
Sound like a Dx Shift Magnitude issue
1st : Do you want to use dx shifting ? Reading the title of the post I suppose the answer is “yes”.
How did you map the shifted layer ?
- with the launcher ?
- or by manually editing the .key file ?
If you are on the second method for your setting :
- What is the
set g_nHotasPinkyShiftMagnitude
line in your Falcon BMS.cfg and/or Falcon BMS User.cfg ? - What are the 2
SimHotasPinkyShift
lines in your .key file ?
-
@CheckPoint
I always use the alt launcher
heres my settings:
from config:
set g_nHotasPinkyShiftMagnitude 256 // Enable DirectX Shifting and specify button offset
set g_nHotasPinkyShiftMagnitude 640 // SETUP OVERRIDEand from user:
set g_nButtonsPerDevice 128// SETUP OVERRIDE
set g_nHotasPinkyShiftMagnitude 768// SETUP OVERRIDEand the key file:
SimPinkySwitch -1 0 0x2F 0 0 0 1 “STICK: PINKY SWITCH”
SimHotasPinkyShift -1 0 0XFFFFFFFF 0 0 0 1 “STICK: PINKY SWITCH (DX SHIFT)” -
This is normal. You have to release SimHotasPinkyShift and how are you going to do that if it’s only bound to the non-shifted DX numbers?
So for example if you press button 9 to start that SimHotasPinkyShift you need to release button 9+640 to stop it. Your key file needs to have both binds, one for button 9 and one for button 649.
-
@Frederf said in help! pinky switch dx shift breaks all HOTAS buttons:
This is normal. You have to release SimHotasPinkyShift and how are you going to do that if it’s only bound to the non-shifted DX numbers?
So for example if you press button 9 to start that SimHotasPinkyShift you need to release button 9+640 to stop it. Your key file needs to have both binds, one for button 9 and one for button 649.
Alt Launcher ordinarily takes care of that, automatically and reliably.
But I’m confused … 0x2F is the ‘V’ key (on standard us-en keyboard layout).
[Edit: and SimPinkySwitch is not a dx-shift callback … it’s just the fov-zoom button for MFDs … SimHotasPinkyShift is the one that does both fov-zoom and dx-shift when held … but 0xFFFFFFFF means it’s not bound to anything here]
Anyway… @AWmk1 what key or button are you using for dx-shift? Can you upload your whole bms-auto.key file to https://pastebin or similar?
-
@airtex2019
@Frederf
@CheckPointit seems like it was probably one of the lines in my user file - maybe:
set g_nButtonsPerDevice 128// SETUP OVERRIDE
set g_nHotasPinkyShiftMagnitude 768// SETUP OVERRIDEno idea when or how this changed! but whatever.
-
@AWmk1
Did you solved it ? -
@CheckPoint Yes thanks, I deleted everything in my user CFG file and it’s fixed.