Configuring Saitek X52 pro mini stick (mouse) for radar cursor
-
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? -
I have mapped my X52 non pro with DX buttons and made a profile specific for the radar cursorsā¦i mean the only thing mapped there is the ministick axis for the cursors. If anyone wants it, just le know. I donĀ“t have it at hand right now but i can share it later today.
-
Hi, I am willing to try almost everything now
-
try what works for you
-
well it works just fine, but ingame the ministick still moves the mouse. any way to avoid that? even if not i could live with it thx
ps: i deinstalled sst completely
-
Hi nomis,
glad you got it to work. Would you be able to share this profile? I cannot get it to work and a stick without radar cursor is pretty useless
Regards Gun -
This post is deleted! -
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.
I tried this registry edit with my x52 and I see no change in the control panel or in-game settings. I tried setting the ministick in SST to āunprogrammedā, āfall backā, and ādirectional axis.ā Stick twist is still Z-rotation axis and the thumb cursor axisā are not available in the advanced settings.
I have windows 10, would that make a difference?
-
So, did you definitely download the x52 version and not the x65 version? Because that is definitely something that will make it not have any effect.
In the SST, you will not see any difference, whether it worked or not. The SST displays axes based on what the hardware is reporting. BMS, and the control panel windows, display axes based on what DirectInput is reporting.
You should load the SST, set the ministick to unprogrammed, run the registry edit, load BMS, and try to assign the new axes within BMS.
I have no idea with windows 10. In theory it shouldnt make a difference, its still windows 6 under the chrome, but in theory and in practice are two different things. I havent tested it on W10, and I dont have any ability to.
-
Yes, definitely x52 version. I can follow that process precisely and even watch the edits being made within regedit. It does nothing for me in-game. Even though the twist rudder axis is #9 in the registry (from 0-8 ) which means it should be left off, itās still in-game and no mouse axisā are created. I also tried these which I found on reddit. (someone posted an x52 fix)
Also tried a PC restart. Itās strange, my x52 is clearly not paying any attention to that part of the registry.
-
I dont recall if it renames the axes accordingly. I know the early versions did not. Also, you definitely have the appropriate version between x52 and x52 pro?
The x52 doesnt listen to the registry at all. It reports its values to directinput, which does look at the registry for details.
-
Okay obviously I donāt know how it works and you do, so Iāll stop assuming. Iām positive I have the correct registry edit though.
I just uninstalled all the drivers and SST software, deleted all the madcatz program files and registry entries beginning with VID_06A3, restartedā¦ then re-installed driver, plugged in x52 when prompted, installed SST, restarted. In SST I set the thumbwheel X and Y to unprogrammed.
I donāt see āJoystick\OEM\VID_06A3&PID_075Cā in the registry, I think that your registry edit creates this entry. I double checked that I have your X-52 NON PRO reg edit and run it again. I see the registry entry created with all 9 axes and rudder is last.
Same result. In-game advanced control settings, Flight stick twist still defaults to the rudder and there are no thumb cursor axes created. I also tested every axis available in the drop-downs regardless of their name. I also tried this joystick testing application, which shows the 8th axis still un-used.
-
If the registry edit creates a new PID rather than edits an existing one, you have the wrong registry edit. The idea is its supposed to overwrite the existing one that was created when the joystick was installed.
do you still have a VID 06A3 in the registry? There should be one of those from when you installed the stick again. If its a different PID, note it, and see if one of the other downloads from my site matches it.
-
Here is a copy of the X52 registry code Iāve copied from your site:
Windows Registry Editor Version 5.00 [-HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_075C\Axes] [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_075C\Axes] [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_075C\Axes\0] @="X" "Attributes"=hex:01,81,00,00,01,00,30,00 [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_075C\Axes\1] @="Y" "Attributes"=hex:01,81,00,00,01,00,31,00 [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_075C\Axes\2] @="Throttle" "Attributes"=hex:01,81,00,00,01,00,32,00 [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_075C\Axes\3] @="Ministick X" "Attributes"=hex:01,81,00,00,05,00,24,00 [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_075C\Axes\4] @="Ministick Y" "Attributes"=hex:01,81,00,00,05,00,26,00 [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_075C\Axes\7] @="Slider" "Attributes"=hex:01,81,00,00,01,00,36,00 [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_075C\Axes\6] @="Rotary big" "Attributes"=hex:01,81,00,00,01,00,34,00 [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_075C\Axes\5] @="Rotary small" "Attributes"=hex:01,81,00,00,01,00,33,00 [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_075C\Axes\8] @="Rudder" "Attributes"=hex:01,81,00,00,01,00,35,00
There are two which were not created by your registry file:
VID_06A3&PID_0255VID_06A3&PID_5081
Neither of these match anything on your site.