Configuring Saitek X52 pro mini stick (mouse) for radar cursor
-
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.
-
What button do use for your shift?
-
MorteSil Thanks for the response. I figured it out finally. The key file editor was outputting the wrong mapping due to X-52 Pro being selected on one of the tabs and not the regular X-52.
Once I fixed that and completely cleared out my SST profile (i.e. a profile with nothing mapped) it is working as desired.
Paying attention to the little details saves you time, effort and frustration. Lesson learned, AGAIN!
Thanks again!
UPDATE: As a reference after struggling with this, my preferred solution is below (inputs welcome, just wanted to capture for people like me):
1. Perform complete uninstall / reinstall of the X52 and Mad Catz software (obviously with the latest Win10 drivers from their site)
2. Perform the registry edit to enable mini-stick as an axis. Your choice on what you give up (rudder or slider, I chose slider). Information on this is readily available in this forum. My reinstall did not show ANY axes in the registry so I did the following:
a. Copy and paste registry code from this site with correct device ID into notepad. This is “key” pardon the pun.
b. Define axis 8 as the one you do not want to use
c. save the text file with a .reg file name to a location of choice.
d. Run saved .reg file, system will warn you of doom, accept risk.
e. Open BMS to ensure axes show up3. Create a single axis, un-programmed profile in X-52 Profiler. Use this profile when starting BMS.
a. you can, theoretically, map the non axis as buttons with bands in the profiler to regain that functionality, but I haven’t had need to, yet4. Use Key editor to define DX bindings. Ensure the correct controller is selected on all appropriate screens (DX Settings, Key Editor tabs). Export.
5. In BMS, choose mini-stick axes to run cursor via setup. Load keyfile you exported. Click Apply.
6. Kill Bad Guys!
Hope this helps someone.
-
Hi friends …. I also have a problem with the X-52pro at 4.34 … the slider has stopped working, I have set the FOV in the advanced section on it, and worked well, but suddenly stopped. In the control panels and in the falcon itself, I will say that it is working properly, but in 3d is no reaction … do you know anyone where I could have a mistake? Thanks
i5-2,8ghz … 18gb ram … gforce 1060 6gb … hdd 1tr -
My problem with the radar stick was trackir, moving the stick put the default profile on trackir. I had to change the trackir keys and now it works (BMS 4.34 and WIN10)