Configuring Saitek X52 pro mini stick (mouse) for radar cursor
-
ok guys so ive been playing around with the Saitek X52 pro mini stick and I finally got it to work for the radar cursor
I got some pictures to follow, there not the best but its something. the good thing about it for me that it frees up one of my head hats
if you guys have any question feel free to ask
once you are done make sure you save and load your profile with the profile button or it wont work
.zip file is the joystick profile if you just wanna download the file
-
Yeah, thats a painful way of doing it.
You can just make a small registry change which makes the cursor use directX axes instead, which means you actually get variable sensitivity - move the cursor slightly, the on screen cursor moves slowly, move it a lot and the MFD cursor moves fast.
Much better and less fiddling around with the SST.
-
yeah man it was painful making those pictures lol, I thought if you did that registry thing you had to remove one of the axis from the fight stick for the mini stick?
-
In effect, yeah. You dont actually have to remove anything as such, but windows will only ‘see’ 8 axes, and it has 7 already. If you add 1 more for each cursor axis (x and y) that makes 9… so the first 8 will be recognised (numbered 0 to 7) and the 9th (number
will not be.So in practice, yes, you have to pick an axis and choose that one to be the new 9th axis which does not work as a directX axis any more. However, it should still work with the SST, which means if you pick an axis you never used anyway, its not a big loss. One example would be to remove the slider axis, and then program the slider axis to use bands as the speedbrakes.
-
cool, ive read somewhere that you could do that, didnt really understand it. thank you for the information. i just got out of a flight messing with it and i get the hang of it, I dont have any issues with its sensitivity, took awhile to get used to but got the hang of it, now that I can use the full TMS left right up down, I like how now I can switch to TWS and RWS, makes targeting alot easier
again thank you for the info!
-
Thanks for posting this. I’m researching HOTAS products and may eventually go with this due to cost.
Have all the kinks I’ve read concerning USB 3.0 been worked out?
-Happy flying -
Glad it helps dont know about the issue with usb 3.0 =/
-
Thanks for the post….
Was easy to do, works like it should now!Cheers mate!
-
Hi!!
Thx for posting this.
Somehow i came untill 6 of 9 but cant figure out how to change this volumes!!?
Thx for help,
Regards -
@AIRKING:
Hi!!
Thx for posting this.
Somehow i came untill 6 of 9 but cant figure out how to change this volumes!!?
Thx for help,
Regardsyou still need help?
-
Yeah, thats a painful way of doing it.
You can just make a small registry change which makes the cursor use directX axes instead, which means you actually get variable sensitivity - move the cursor slightly, the on screen cursor moves slowly, move it a lot and the MFD cursor moves fast.
Much better and less fiddling around with the SST.
Blue3wolf
How exatlty would you go about creating this registry? I have been messing with the SST program and I cannot get it to work. My cursor just get stuck moving up or down whichever way and I cannot make it to stop.
Your help is greatly appreciated
Pika out -
With this setup, the SST setting is first set to none - so that moving the ministick does not result in moving the mouse cursor.
As an aside, the registry edit does mean the twist rudder no longer works as a DirectX axis - although it still works with SST.
You can download the registry edit from falcon.blu3wolf.com and it makes changes to your windows registry - note that there isnt an uninstaller for it, and it is provided without warranty, without even the implied warranty of merchantability.
For an X-65F the download should be on the right hand column. Double clicking the downloaded file should merge it with your registry.
It renumbers the DirectX axes, adding the ministick and making the twist rudder the 9th instead of the 3rd. In turn windows no longer recognises it - although it can still be programmed through the SST.
Final step is to assign the new ministick axes in the BMS advanced controller window, to the cursor x and cursor y axes.
-
Blue3wolf
How exatlty would you go about creating this registry? I have been messing with the SST program and I cannot get it to work. My cursor just get stuck moving up or down whichever way and I cannot make it to stop.
Your help is greatly appreciated
Pika out@Flounder:
Did this today. Since changing my stick to a Warthog, I no longer have a twist rudder, and hence, do not need the twist rudder axis.
Following this post on BMS (https://www.benchmarksims.org/forum/showthread.php?11428-how-to-set-the-mouse-on-throttle-to-work&p=151158&viewfull=1#post151158) I hacked my registry entry for the X52 and created an ‘X’ and ‘Y’ axis for the X52 cursor nub.
Reset my axis assignments in BMS Setup and tested in-game. Works like a charm.
This is the registry update script I used. The highlighted device/PID info is user specific as I understand it. Anyone else doing this would need to add their device/PID in place of what I have:
Windows Registry Editor Version 5.00 [-HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM[COLOR="#B22222"]VID_06A3&PID_0762\Axes] [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM[COLOR="#B22222"]VID_06A3&PID_0762\Axes] [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM[COLOR="#B22222"]VID_06A3&PID_0762\Axes\0] @="X" "Attributes"=hex:01,81,00,00,01,00,30,00 [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM[COLOR="#B22222"]VID_06A3&PID_0762\Axes\1] @="Y" "Attributes"=hex:01,81,00,00,01,00,31,00 [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM[COLOR="#B22222"]VID_06A3&PID_0762\Axes\2] @="Throttle 1" "Attributes"=hex:01,81,00,00,01,00,32,00 [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM[COLOR="#B22222"]VID_06A3&PID_0762\Axes\3] @="Ministick X" "Attributes"=hex:01,81,00,00,05,00,24,00 [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM[COLOR="#B22222"]VID_06A3&PID_0762\Axes\4] @="Ministick Y" "Attributes"=hex:01,81,00,00,05,00,26,00 [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM[COLOR="#B22222"]VID_06A3&PID_0762\Axes\7] @="Slider" "Attributes"=hex:01,81,00,00,01,00,36,00 [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM[COLOR="#B22222"]VID_06A3&PID_0762\Axes\6] @="Rotary 2" "Attributes"=hex:01,81,00,00,01,00,34,00 [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM[COLOR="#B22222"]VID_06A3&PID_0762\Axes\5] @="Rotary 1" "Attributes"=hex:01,81,00,00,01,00,33,00 [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM[COLOR="#B22222"][color]VID_06A3&PID_0762[/color]\Axes\8] @="Rudder" "Attributes"=hex:01,81,00,00,01,00,35,00I now have NOTHING in BMS working off of the Saitek SST programming. The only key emulation on the HOTAS is the TeamSpeak PTT button (a non-BMS function).
You fool with/edit your registry at your own risk.
-
awesome due!!
Thanks
I will report back
-
I did it!!!:bdance:
I edited the registry just like you said and now my mini stick is working as radar cursor :munch:
I just need to set up the slider (which is my 9th DX axis as a zoom feature in SST.
Thanks Agave Blue!! and Blu3Wolf!!Pika out
-
Hi guys,
I have a problem with microstick on Hotas in Falcon 4.33… I have downloaded BMS profile for Siatek X52pro (Falcon BMS X-52.pr0) (I used it in 4.32).
In settings everything works OK, even when I start the sim - in setup the microstick is working in all of directions. Then in the game when I am trying to lock on someone suddenly is possible to move it only in direction to down/right (or sometimes - down, right, up)… Move the brackets in to the left is impossible until the restart of the game… Then it works for a while again and then it stop… When I pauze the game and switch to control profiller of Saitek - everything seems to be OK. I assume that deadzone could be set wrong… Any idea how to fix it? -
I’ve seen a lot of people have this problem, including myself. I have not seen anyone identify (to my satisfaction) the actual cause or solution. In my own case, it seemed that reverting to an older version of TeamSpeak was the difference (
- don’t ask me why).The only ‘permanent’ solution I know of is above …. remove any/all SST programmed commands and put your mini-stick on an axis.
-
If teamspeak affects it, it is likely TS trying to use the inputs. In the TS settings there is a dropdown box which has a ‘mouse and keyboard only’ option - selecting that may fix it.
-
OK guys, I will try it tommorow and ´ll let you know if it helps…
-
Hi guys, thanks for help - it works…
It was necessary also to reinstal drivers as well, because suddenly MadCatz stopped working, but it works now…
But I have another issue - after reinstaling and downloading the drivers from saitek webpage I have now problem with the stick. Hotas is working properly… But stick is working like in 2 zones - if I move slightly the plane response is quit weak and the response is after while (no laging). If I want to turn properly I must pull harder (time period is significantly shorter, but still the response is not immediatelly) - a lot harder… In setup in the falcon seems the moves fine, but in the controler window I can see this zonation… Dead zone seems to be setting fine… Some advice?EDIT:
So bad news again… Microstick stopped work in lefta axis again. Suddenly even if I start setup in Falcon there is no response in left direction. In controler settings everything is working…EDIT2:
Now it seems that problem is in the interaction between mouse and microstick… But still I have no idea how to solve it… Try another profile?
