Pinky Shift state sticking?
-
Today after a failed first attempt at a flameout landing, I held the Pinky button + paddle on the cougar to eject. Ended the mission and loaded it again and this time successfully landed. Held the paddle button (without pinky) to engage the wheel brakes and was ejected out of the canopy. :rofl:
Loading again paddle ejected again, quit/restarted the game and paddle now engaged the wheel brakes/everything back to normal, that is until I pinky+paddle to eject again. After that (in subsequent missions), the pinky switch appears to remain active until pressed at least once after which it works as normal. I can use shifted functions and unshifted without issue. It seems to only get stuck if I use pinky+paddle to eject, as though the release of pinky button is being lost because the mission has ended?
I’m using Dunc’s BMS keyfile, with a small mod to move trim back to unshifted layer and place rudder on the shifted pov layer, but have tried copying the original/unmodified Dunc key file in and loading/applying that too. Same outcome.
It’s not a biggy as long as I remember to press the picky once on loading into a new mission but I know I’ll forget, ramp start, wheel brake test and go flying out of the jet
Anyone else experienced this? A known bug or issue specific to my setup?
-
Are you using SimHotasPinkyShift callback? It sounds exactly like release of shift is not applied in certain situations like after ejection and probably if you hold shift and leave mission too.
It’s not a thing I can give a fix for except not to put flight critical functions on shifted state so remedy is possible if memory to always cycle shift is not practical.
Another option since joystick is programmable is not to use shift function in BMS but instead write it into TARGET/FOXY script instead.
-
I had the same issue. My problem was that I didn’t map the pinky shift to the “extended” range.
When you push the pinky shift button, it adds a value to all DX input. By default this is 256, but can be changed in the falcon BMS config file with this line:
set g_nHotasPinkyShiftMagnitude 256 // Enable DirectX Shifting and specify button offset
So for example, if you have pinky shift mapped to a button that generates “2” when pressed, then the sim immediately shifts this by adding 256, so it now appears that “258” is pressed. When you release the button, instead of generating a release event for “2”, it generates a release event for “258”. Because of this, the pinky shift gets “stuck”. The fix is to make sure the pinky shift is mapped in both the unshifted and shifted range.
For example, on my joystick the button that generates DX4 (the paddleswitch on the warthog stick). The sim sees this as “3” since it starts at 0 instead of 1. In my key file, I have 3 and 259 mapped to pinky shift:
SimHotasPinkyShift 3 8 -2 0 0x0 -1 “Paddle”
SimHotasPinkyShift 259 8 -2 0 0x0 -1 “Paddle”When I push the button, the sim sees “press 3” which starts the shift, and when I release, the sim sees “release 259” which ends the shift.
-
I sometimes have a similar issue when using the pinky switch on my Warthog HOTAS. For instance when I use it to rotate the outside view the function will sometimes get stuck and the camera rotates around the plane until I press the pinky switch (and only the pinky switch) again. I’ll try your solution and see if it helps to fix these issues, too. Thanks!
Uwe
-
I’m pretty sure I have that Shift Magnitude set already, although I shall double check this evening.
I’m not sure that will be the same issue I see though as my pinky shift works normally in all other uses, it only gets “stuck” when used in combination with the paddle for eject. I wonder if it’s something to do with having foxy setup for the unshifted paddle to emit “k” for wheel brakes.
I’ll have another play around with it tonight, will see if disarming the ejection seat then using shift+paddle still causes a stuck pinky.