X52 pro reg mod on ministick stuck at lower bound
-
Hi I did the registry mod to give up the rudder axis for the analog cursor using X52 pro’s ministick.
The registry mod script and instructions are from here: https://github.com/alex-smtv/X52-PRO-Mouse-Ministick-to-Axes
When I try to assign the axis in the alternative launcher both “Cursor Y” and “Cursor X” does not get registered. So I wondered what was going on and entered the actual BMS Falcon UI in Advanced settings.
I mapped the axis to the respective axis and turns out it is stuck at the lower bound of the curve:
As you can see there is input (shown on the blue bar) and it does have a mid-point and can do increment or decrement but only by a small amount. It is probably a resolution/scale thing I guess. This is also why the Alternative launcher does not register because the movement is too small to notice.
I didn’t use any profiles in the SST software, uninstalled and install them multiple times, and still does not work.
Any ideas what could happen? I also defaulted all deadzone and in Window’s game controller setting.
Probably not related I bought this few months ago so it is Logitech version not Saitek/MadCat ones.
Thanks
-
@gabrielwong1991 Not sure if this will help you but I have had a very similar issue with my cursor. It constantly slid to the lower left for me even after running reg fix. I actually setup a large deadzone within the bms software (I think there is actually the deadzone buttons to the right of the bars you show in the screenshot above. That seems to have worked because I think there is a weird software driver issue and the game is thinking the mini-stick is being activated. By adding the deadzones it takes that out of it. Now my cursor works as needed.
One Thing to remember though is if you are using the Alternative Launcher you need to set the deadzones there because they will overwrite any changes you make in the game controller setup screen in game. If you aren’t using Alternative Launcher, then disregard.
-
I don’t think dead zone has anything to do with it but probably has something to do with DX (from what I gather it is the API the game uses to communicate with the joystick) axis assignment. Though I have absolutely no idea what’s going on, having googled for two days no one seemed to have my problem…
Let me explain…
To make DX recognize the mini stick axis we have to label them by changing the number in the reg file and put the unused (give-up) axis at number ‘8’. It does not matter to me because I don’t need the slider or rudder on the joystick anyway.
From my testing or in my case there is a specific combination to make both axis works. To complicate things further the midpoint of one axis is not at 50% at all. (just like my first post)
I have tested many combinations by putting “Ministick Y” and “MiniStick X” in different orders here are my findings:
Y (order) --- X (order) --- Midpoint Y --- Midpoint X 5 7 Working @50% Stuck 5 6 Working but @10% Stuck 6 5 Stuck Working but @10% 7 6 Working but @ 10% Working @50% 6 7 Working @ 50% Working but at 10%
Clearly, you can see there is a pattern where ministick Y and X must put in 6 or 7 in order to work, and one channel will have full deflection 0%-50%-100% and the other will have limited deflection 0%-10%-20% something like that. One will not able to use this because depending on the axis assigned you will either constantly drift LEFT or UP because one axis will always at the lower bound of the curve (10%).
I did not mess with the order for 0 to 4 as they are unrelated, they are (Joystick X, Y, Throttle, big and small rotary). So I only mess with the rest 5 to 8 (slider, rudder, ministick X and Y).
I am out of clues really, not sure what is going on. Did numerous reinstall Logitech’s driver and SST (I cannot download Saitek’s one as it is gone now). The same problem happens. I am not sure if it is hardware problem but it works fine with non-analog method (setting bands on SST software).
The reason why I drill on this is that:
- people said it feels much better than ‘SST band method’.
- 4.37 introduce a new problem where you can only input one command at a time. Say If you press Up, you cannot press Left or Right diagonally. That means the command cannot stack up and now is incredibly hard to slew with targets moving this is probably the reason why they add a new callbacks for UP-LEFT, UP-RIGHT, DOWN-LEFT, DOWN-RIGHT which is a step back the direction.
For point 2, one guy have the same problem.
And dev responded
Anyways if any of you have ideas please chime in I am out of clues after spending two days diagnosing this on holiday when I could enjoy the game Though I should thanks BMS dev for their hard work because they do this for free!
-
-
For what it’s worth, add me to the list of those experiencing this problem. It’s one of the last “gripes” that I’ve been unable to work around as I’ve set up my HOTAS. Hopefully, someone will come up with a fix and share it here. I will if I do!
-
Same here since 4.37,before Ministick worked fine,hope someone can get the fix soon…
-
Does the Windows calibration-wizard in Joy.cpl have any good effect, for the X52 ministick?
-
@airtex2019 dont know about that ,but you have to be more specific is it X52 or X52pro?!
-
Weird. I don’t have any issues with my X52pro with the reg edit.
Here’s me in the AltLauncher holding the ministick diagonally.
I think a good start is to see if the problem is in BMS or in Windows,
-Click the Windows “Start Button”
-Type “game controller”, and click “Set up USB game controller”
-Highlight ‘Saitek X52 Pro Flight Controller’
-Click ‘Properties’
-Look at the Ministick graph and see how it behaves. Still pushed over to the extreme?
-
@Zeus_ Done and looks like ministick is doing ok,does it mean its Windows problem?drivers?do you have latest driver that you can share? Reg edit meaning ?Thanks
-
@Zeus_ I’m a little (lot?) lost. Please help…where do you type “game controller”? Once there, I might be able to fix the problem as you have. Note…I am not using AL other than to enter the SIM. I’m using an updated setup that I’ve migrated from 4.36.
Thanks for your help!
-
@Nupe2 Windows. Start menu.
-
@AIRBARBA said in X52 pro reg mod on ministick stuck at lower bound:
Done and looks like ministick is doing ok,does it mean its Windows problem?drivers?do you have latest driver that you can share? Reg edit meaning ?Thanks
So if you see that cross moving perfectly in the Windows Game Controller screen, that would assume it’s a BMS issue. Hm, I’m a bit out of ideas now.
I ran the regedit code from this post and the Alt Launcher was able to see the ministick afterwards without any additional steps,
https://www.benchmarksims.org/forum/showthread.php?21930-X-52-(non-pro)-Mini-Stick-and-TDC-Cursor&p=544048&viewfull=1#post544048@Nupe2 said in X52 pro reg mod on ministick stuck at lower bound:
I’m a little (lot?) lost. Please help…where do you type “game controller”?
Woops, I added just that extra step to my post. Airtex got it though, just click “Start” in Windows first.
-
@Zeus_ Looks like U1 did not bring change regarding X52pro mini stick?!
-
@AIRBARBA I was afraid of this. Will check when I get a minute.
-
@AIRBARBA The update seems to have improved the ministick function. I just took a quick flight and it wasn’t as smooth as I’m used to but maybe a deadzone adjustment will fix it.
-
@Nupe2 thx for info,what kind of saitek x52 pro profile and key file are you using?
Also do you use alt launcher or overrride launch?Saitek profile is active on task bar (green )? -
Glad to help! I’m using the profile and keyfile migrated from 4.36 (and prior). My profile is based on one setup and shared by a simmer named SCUBY.
I use the override launch. Not sure about your last question. -
@Nupe2 thats great,by me all was ok including 4.36,Iwas using Flounder profile since 4/5year ago…would you consider to share profile and send PM?
Is your Saitek profile active(green ) or like this?! -
I think I’ve used that Flounder program as well. Will send you the SCUBY setup as soon as I can.
-