X52 Pro - pinky blocking buttons
-
@syringe there are many threads on this but I’m not clear what the solution is
https://forum.falcon-bms.com/search?term=x52+pinky&in=titlesposts&matchWords=all -
I saw most od them.
My problem is different.
Same profile works on 4.35, 4.36 and It works on 4.37. Now after u2 profile works normal till i push pinky. And then It lock.
Also It works normal in setup but lock on 3D. -
@syringe Is the pinky shift button defined in both the unshifted and shifted layer ?
Sounds like that is your issue ? -
@syringe said in X52 Pro - pinky blocking buttons:
Hello.
I am using Falconeer .key profile and after updating my BMS to latest version using pinky is blocking all HOTAS buttons. It’s like pinky is still pressed.
I checked latch and clutch and they are off. Also i reinstall BMS and profiler.
I have also BMS 4.35 on my hdd and there pinky working ok.If you are using my Falconeer profile for X52 Pro, you need to be sure that you release any other buttons before releasing the pinky button. If you do not, it will remain locked.
You need to get into a physical habit of “Press Pinky, press other button, release other button, Release Pinky” with at least 0.05 seconds between these actions.
Pressing and releasing the Pinky should have the effect of a Pinky Button Press, with various functions. Holding it down should allow access to the Shifted layer, but you must release any other buttons before you release the Pinky.
The Joystick Button Layouts have this note in the bottom right:
If you are sure you are performing this action correctly, as the image above states, and still have this issue, let me know and I’ll be happy to help you troubleshoot further.
-
@syringe said in X52 Pro - pinky blocking buttons:
My problem is different.
Same profile works on 4.35, 4.36 and It works on 4.37. Now after u2 profile works normal till i push pinky. And then It lock.
Also It works normal in setup but lock on 3D.that is weird if true … not a problem anyone else is having, and can’t see how it would be specific to X52.
you have compared your active key files, 4.36 vs 4.37, and they’re identical? (using a tool like https://www.diffchecker.com/ ?)
-
@airtex2019 They happen to be using a pre-made profile for their X52, my Falconeer set. These keyfiles haven’t changed since April 2021. The only thing I could imagine would be a shift magnitude change as this must be exactly as expected by the keyfiles for my Falconeer profile setup to function correctly.
EDIT: I would suggest simply Notepad++ and the Compare plugin, not that a website wouldn’t do ofc
-
@SemlerPDX yeah my first guess is to blame Alt Launcher for tweaking the shift-magnitude or completely overriding the key file…
but that typically results in “shift layer doesn’t work” or “shift layer does wrong/random things” … not “pinky button gets stuck and breaks my entire jet”
I’ve heard other X52 users voice similar complaints, but I don’t have one, so I’m not much help… just trying to narrow down possible sources of problem/confusion
-
@SemlerPDX - Yes I aware of using pinky with Your profile. Also I used It in 4.37u1 flying campaing in VR. I updated tu u2 and then problem starts.
I have also older BMS ver on my hdd. I tested profile on 4.36 and 4.35 and there is ok.Next thing I noticed - when I enter setup and check my controls pinky is working fine.
When I use It in 3d It’s locked. For example - I use DMS, next pinky and all I can to with DMS hat is only trim. When I go to menu and settings to check controls then BMS can’t see my inputs. After restarting BMS all works fine till I pres pinky again. -
@SemlerPDX Can you explain the intention for this section?
I admit I never fully understood the “up vs down vs up/down” semantics, as described in technical-manual pdf.
To me, this reads like
onPressPinky(5) => activateShift
onHoldPinky(261) => continueShifting
onReleasePinky(5) => activatePinkyWithoutShift and/or deactivateShift? unclear -
@airtex2019 I am not sure what you mean, as in I don’t understand what you don’t understand based on your pseudo, though it helps a little… I think you are asking about DX button press and release events as you have “0x42” highlighted in your screenshot.
These are explained better than I could around page 151 of the BMS Technical Manual. With this setup, when pressing and releasing the Pinky like a button, it acts like the Pinky button – but when held down for a time, it engages the shifted layer until released.
-
@SemlerPDX I am saying, I don’t understand what line 1306 is intending.
I think you want
set g_nHotasShiftQuickPressTimeLimit 250 //milliseconds - timeout for disambiguating pinky-switch (tap) vs DX-shift (hold)
in cfg, to achieve what you are describing. Then line 1306 is unnecessary.
My hypothesis: something changed in BMS code … line 1306 used to work (or at least, do no harm) but now it doesn’t.
[Edit: I haven’t done any testing… just baseless speculation. @syringe you can try deleting that line (or put a
#
character in front of it, to skip it) to see if it helps?] -
@airtex2019 said in X52 Pro - pinky blocking buttons:
@SemlerPDX I am saying, I don’t understand what line 1306 is intending.
I think you want
set g_nHotasShiftQuickPressTimeLimit 250 //milliseconds - timeout for disambiguating pinky-switch (tap) vs DX-shift (hold)
in cfg, to achieve what you are describing. Then line 1306 is unnecessary.
My hypothesis: something changed in BMS code … line 1306 used to work (or at least, do no harm) but now it doesn’t.
[Edit: I haven’t done any testing… just baseless speculation. @syringe you can try deleting that line (or put a
#
character in front of it, to skip it) to see if it helps?]No offense, good friend - but your baseless speculation not exactly incorrect but equally not required - though I totally appreciate the assist! I am so lost!! I have just confirmed that the Falconeer setup works out-of-the-box as-is, and that the Pinky section of the keyfile is correct and accurate. I have tested using Instant Action, and setting an autopilot course - holding Pinky plus the dual-stage trigger on the X52 Pro functions like the autopilot disengage while held, and so I can clearly see that I can hold a course and releasing it re-engages my autopilot immediately banking the jet accordingly. And with the SOI as FCR, pressing and releasing Pinky button also clearly has accurate effect.
I have tested this in default as-is keyfiles, and it works, and also tried commenting out line 1306 - same thing, it still works. At this time, I had not added the g_nHotasShiftQuickPressTimeLimit line to the cfg. After doing so, same result - still works. After uncommenting line 1306 with this still in the cfg, also still works.
Regardless of anything we do with these lines, apparently Pinky button will act as a pinky button when pressed as such, and will act as a shifted layer when held and do nothing but release the shifted layer upon release.
For this reason, I would suggest to @syringe to ensure that the device order is correct, that the STT Software has the “BMS Falconeer” profile properly selected and set as the active profile, and perhaps to double-check that button presses on the stick and throttle while under Setup > Controllers show the numbers you’d expect from them when pressed (can’t test shifted button numbers, but will still help get an idea of what is happening).
I’d ask that before you use the Pinky that you verify all other buttons are working as expected, such as the HAT switches and such, and then be sure you confirm that they are stuck by holding Pinky, then pressing some shifted button to test it working, then releasing that button, and waiting a good second before releasing the Pinky - see if it is still stuck. If it is stuck, try holding it down for a few seconds, doing nothing else, and then release it - see if it has become unstuck through such an action.
Will watch for your replies, so sorry you are having this issue. If I could only replicate it on my machine, I may be able to help further. Maybe if you include your Device Sorting file and the exact keyfile you currently have set in a “.zip” file here, I can download them and test them to see if they work as expected on my PC.
-
@SemlerPDX said in X52 Pro - pinky blocking buttons:
Regardless of anything we do with these lines, apparently Pinky button will act as a pinky button when pressed as such, and will act as a shifted layer when held and do nothing but release the shifted layer upon release.
Yeah apparently (per docs) it’s on by default and the hold-delay is 200ms.
-
@SemlerPDX
As i wrote before:- Pinky works on BMS 4.35 and 4.36
Your profile works also in 4.37u2 till I use pinky in 3D. Then in example DMS HAT is working as trimmer - so pinky is locked.
When i use It in Setup/controls It show me S6 button “Stick: Pinky Switch (DX Shift)”
My DeviceSorting is only one device:
{076206A3-0000-0000-0000-504944564944} “X52 Professional HOTAS”I use Your profile long time. I fly with It in BMS 4.37u1 and It was ok. After updating to u2 pinky start to lock.
Also i reinstall BMS and Logitech profiler - no luck.I just made video. In 1:30 I use pinky and DMS top working. I steer plane by trimmer.
- Pinky works on BMS 4.35 and 4.36
-
This post is deleted! -
@syringe said in X52 Pro - pinky blocking buttons:
My DeviceSorting is only one device:
{076206A3-0000-0000-0000-504944564944} “X52 Professional HOTAS”Please review your
falcon bms.cfg
andfalcon bms user.cfg
files … ensure g_nHotasPinkyShiftMagnitude is set to 256 as required by the key file. -
repro confirmed … I also only have 1 device (not an X52) and when I use a hand-managed key file expecting shift-magnitude == 256 … but I have
set g_nHotasPinkyShiftMagnitude 128
in cfg … which is what AL would append by default when it counts n=1 device … all buttons stop working for me, when I press pinky -
@airtex2019 - thanks Bro for help.
In falcon bms.cfg I oryginally had “set g_nHotasPinkyShiftMagnitude 256”, but falcon bms user.cfg file was empty.
I add “set g_nHotasPinkyShiftMagnitude 256” line and pinky is now working.
But now I have another issue - every time I start BMS i must go to setup and choose X52Pro instead of keyboard, and manually load key file. -
@syringe if you’re going to use a oldschool hand-crafted key file … you have to either avoid the Alt Launcher – or always ensure to select its “don’t apply overrides” checkbox, before launching
also be aware – the Alt Launcher will keep trying to change your g_nHotasPinkyShiftMagnitude back to 128…
once you get things working and stable – I recommend make a backup subfolder (or zip) of everything in your Config folder
-
So it was an issue of the Pinky switch not being seen on the shifted layer. Not the same cause as I stated above, but same consequence