Configuring Saitek X52 pro mini stick (mouse) for radar cursor
-
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.
-
As above, this is offered without any warranty, representation of fitness for a particular purpose, and all liability is disclaimed. If you somehow set off a nuclear reaction with this, I accept no responsibility.
http://blu3wolf.com/falconbms/jstickaxesmod5.reg
This is the same changes made, for the PID your joystick seems to want to use. Hopefully it will work for you. If it doesnt, either Ive made a silly mistake, or you are SOL. Fingers crossed!
-
That did the trick! Thankyou so much for your patience and help. I’m sure glad I mentioned the PID discrepancy.
Very strange how mine uses a different PID. Chalk it up as Windows 10? It’s also plugged into a USB 3 port, if that could matter.
-
Could be a newer or older production model x52, also. Id be surprised if the Product ID was changed specifically for W10. I hadnt known there were other PIDs for X52s other than the difference between pro and non pro, before now.
-
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
Did you figure this issue out? When I was having X52 woes I found it harder than it should be to “Completely” uninstall the Saitek software. It’s more than just the SST, there is some other stuff that had to be removed as well for the mouse/keyboard emulation. It was not uninstalled by default when removing SST.
-
Specifically, Magic Key and Magic Mouse drivers should be removed also.
Alternatively you can retain SST software, and set the profile for the ministick to just be unprogrammed. From the SSTs point that means its not useful, but as we have added it as DX axes, we can still map it through the keyfile for BMS.
-
Is the registry modification going to affect other sims as well other than subtracting one axis from them?
-
Er. Okay, technically speaking, the registry modification does not directly affect any sims. It changes the order that axes are declared to DirectX in, as well as adding two that are not normally declared at all to DX. This rearrangement leaves the rudder axis at 8, which (starting from 0) is the 9th axis. DX normally only likes playing with 8 axes per device (exceptions apply, but I dont know how to make them apply).
So, this modification will in effect cause the rudder axis to stop sending DX position updates, which in turn means the sim wont see it. SST will still see it, because the joystick programming software doesnt use DX to communicate with the stick.
Its sim agnostic, this change. It doesntmatter what sim you run, the registry change will mean that none of them see the rudder axis ( unless the sim developers programmed their sim to communicate specifically with your stick, and not through DX - a terrible idea, but entirely possible, and its what DX was developed to stop).
So for basically every sim out there (sims that support DX), the registry modification is going to indirectly affect them, by causing there to be two new axes on the hotas, and one old one will be missing.
-
Hi, after some time I have a problem with microstick once again. This time the bracket on FCR is slewing to the left side itself… This problem started with update of TeamSpeak - of course it could be a coincidence, but anyway… After removing of TS the problem persists… Changing the axes in profile didn´t help… Any idea please?
-
Could be hardware… what does the windows controller window show for the axis?
TS3 has a history of having issues with controllers. You can disable TS3 interacting with them, though.
-
Hi Blu3wolf,
well axis for micorstick are moving themself little bit. Worst is, that they are moving also when I pull the throtlle forward/backward… It si doing the same on PC and notebook also… Uninstaling of TS3 didnt help…EDIT:
I instaled Saitek for another notebook - the problem persisted, so it seems as a problem with HW -
I’ve wanted to apply this mod for quite a while now, the only thing that stopped me is that I have no rudder pedals, so disabling twist-rudder was not an option, especially that I play some other flight sims too. Fortunately, turns out that you can “sacrifice” other axes just as easily, so I edited the Blu3wolf’s .reg file so it puts the Precision Slide as 9th axis. I’ve barely used it as real axis anyway. It’s still possible to assign a function to the disabled axis through the profiling software - in my case it’s set to “bands” to open and close air brakes in modern combat sims.
Here’s the content of the .reg file. It disables the Precision Slide (still programmable through SST) and enables micro-stick as regular axes. As always, use at your own risk and make registry backup before changing anything!. Make sure the stick reports as VID_06A3 & PID_0762 in Device Manager. Save this as .reg file, double-click and apply changes, afterwards you may need to restart the system. As it renumbers axes, there may be need to reassign them in games.
Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_0762\Axes] [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\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\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\VID_06A3&PID_0762\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_0762\Axes\3] @="Rotary 1" "Attributes"=hex:01,81,00,00,01,00,33,00 [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_0762\Axes\4] @="Rotary 2" "Attributes"=hex:01,81,00,00,01,00,34,00 [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_0762\Axes\5] @="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_0762\Axes\6] @="Rudder" "Attributes"=hex:01,81,00,00,01,00,35,00 [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_0762\Axes\7] @="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_0762\Axes\8] @="Precision slide" "Attributes"=hex:01,81,00,00,01,00,36,00
-
I have a fix for the cursor stuck moving/speed brake not holding (if someone uses the slider for speed brake) issue. I’m kind of surprised no one posted it since I’ve been searching for the solution yesterday as well and it struck me immediately when I read about stuck keys in the keyfile manual.
Since BMS requires the keys to be released in a certain order, the default SST assignments are useless because they release them in an opposite order (modifier first). This causes whatever combination you assigned to it to get stuck on release. To solve this you have to use advanced commands instead.
For each button/band you have a combination assigned to in SST:
1. Open menu for the given input > new advanced command
2. Click on the first line (press) and repeat the key combination you assigned previously, releasing the keys in a proper order (modified key first, then the modifier, e.g. for cursor up you would have Shift|Up|Up|Shift in that line, with the latter two using different graphics to show release)
3. Cut and paste the latter half of icons (i.e. the release events) in “press” line to “release”
4. Right click on both lines > quantize time > set to 0.01 (this is important, if you leave it as is you’re gonna have a huge delay on release leading to unwanted inputs)
5. “OK” everythingIf you’re using the slider as bands you might want to assign non-modified keys only to it anyway, since it’s noncentering and if you keep it in a position you’re going to shift other inputs.
If you want to assign MRM/SRM override to the slider just repeat the steps above but don’t copy the release events to release, as you want them to only be pressed once upon moving the slider into position and immediately released. You can disregard the above paragraph in this case.
EDIT: This is what it should look like in SST once you’re done:
EDIT2: Someone already mentioned it in this thread.
-
Alright, I my ineptitude is showing. My registry showed both PIDs, but the one with the Axes keys did not ID as X52, and X52 had no Axes keys at all.
So I added the keys to the X52 entry and it still is not showing up in game as an axis. I had previously modded the no-X52 PID axes as well, but that didn’t work either.Any thoughts?
Update 1: After removing software and drivers and reinstalling, I now show the PID 075C with no axes, but it does ID as an X52.
Update 2: Made teh registry change and it worked, I now have the mini stick axes available in the sim.
Next issue: DX controls on the stick don’t seem to persist after a couple of missions. I lose all shift functionality., but that may be another thread.