X-52 (non pro) Mini Stick and TDC Cursor
-
Tried adjusting the saturation at all?
-
Yes all three or four different settings.
-
Then, Im not sure what could be going wrong there.
The rotaries should not be affected by the edit, and I can’t see why the ministick would work to control the mouse cursor normally, but not present working axes to DirectX…
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\8] @="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\3] @="Rudder" "Attributes"=hex:01,81,00,00,01,00,35,00
Copy that text to a text file, and save it with the .reg extension. That should change the twist rudder back to working order, if you just want to give up on it.
If the antenna elevation is still screwy after that, your best option is for a full removal of the drivers before reinstall them - deleting the registry keys under VID_06A3&PID_075C with the stick unplugged, and then plugging it back in should do the job.
If you want the thumbstick working as a radar cursor, the next step would be to go into the windows game controller settings and see how far the axes move in there - there is usually, but not always, a calibration option from that menu. If the axes move incorrectly there, that could indicate any number of things…
Im not really sure what to suggest. Maybe I could work something out with physical access to the machine, but I dont know for sure. I know I spent about 9 months trying to get this working on my first joystick myself, so Im used to frustration and Im used to things not working right the first or second time. If you do keep messing with it, please do post updates/questions as you go. If you can get it working, its worthwhile just having a cursor with a variable speed.
-
@16th:
I used the SST software to program the Mini Stick to move the TDC Cursor and when I move it in any direction it won’t stop when I take my finger off the mini stick! The cursor continues to move in the direction until I try to move it in another direction at which time it continues to move in the new direction! Any ideas what is going on? If I move it to the left and let go of the stick it keeps going left! If I then move it up it continues to move up etc. Is there a way to program it in DX?
Hi Widowmaker.
I use a very simple profile for my X-52. This profile only uses Radar Cursor assignments and other non-falcon stuffs. Related to Radar Cursor, I had to program mini stick position with “Advance Command” because I experimented the same issue that you have. In BMS I have ALT+Arrow to move the cursor, and after some testing I have realized that if you release ALT key before Arrow key, radar cursos will keep moving without stopping indefinitely. So, in STT with Advance Command I programmed “release sequence” releasing Arrow Key before ALT key. For both Press and Release command I adjusted the timing for the first key (Press–>ALT, Release -->Arrow) to 0, and for the last one (Press–>Arrow, Release -->Alt) to 100 ms. It works for me.
I suggest you to try this setup.
Salute.
Gavilan -
Hi, I clicked on the link on your page for the X-52 (non pro) and it shows what registry keys are needed. It just pulls up a page showing what the registry should look like. How do I create those registry entries? I navigated to the location listed above, but I do not have an “axes” subsection under HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_075C.
-
If you right click it and Save As… (depends on which browser you are using as to exact behavior), you should be prompted to choose a location to save the respective .reg file.
I had been under the impression that the driver install process for the X-52 created the VID&PID key specific to the vendor/product combination, and a subkey called Axes, which in turn has subkeys with the Attributes value as described above. It would be worth checking if you have any other keys in the OEM key that start with the VID_06A3 - as this is specific to Saitek. There are several different Product IDs for the X-52 non-Pro, depending on how new it is.
Whichever PID you have it for, you can create the keys and values manually using regedit, but this is probably best left alone if you are new to regedit. Normally the way I would recommend adding the keys is by downloading the appropriate .reg file from my site, and double-clicking it to run regedit and merge the values into the registry.
As an aside, if you do accidentally download the wrong file and add its values to the registry, it will not harm your computer - although it will rearrange the axes for whichever other joystick the file was meant to apply to. If you have only the one joystick, its just going to mean your registry is a few kilobytes larger than it needs to be (a drop of water in the ocean).
To answer your actual question, though I recommend against it, you can manually add the entries to the registry using regedit. You can browse to the lowest level node that matches the location given above, and right click anywhere in the right hand window. Select New > Key and name the key created (a ‘Key’ in this context is much like a Folder in the normal Windows Explorer context). In this case, you would browse to HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_075C and right click the right hand window, select New > Key, and name the key ‘Axes’ (sans quote marks). Then you would need to do the same thing again inside Axes, to create subkeys named 0 through 8 (technically the last one can be omitted). Then inside each numbered subkey, you would right click again, with New > Binary value. The name of the value is Attributes, and the value of the string is 01,81,00,00,01,00,30,00.
As you can see, its much quicker and far less error prone from typos, to use the existing files, so I would recommend that instead.
Hope that helps!
-
Hi, I clicked on the link on your page for the X-52 (non pro) and it shows what registry keys are needed. It just pulls up a page showing what the registry should look like. How do I create those registry entries? I navigated to the location listed above, but I do not have an “axes” subsection under HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_075C.
Belated realisation: Another concern you might end up with is that there is not just one such link on my downloads page. There are 3 different links, 1 for the Pro and 2 different ones for the non-Pro version. It likely would not hurt to check out which PID values you have already in your registry, before installing one or either of the ones available for download.
-
Thank you for the help on getting the registry edit to take for the mini-stick, works properly now.
-
Hi Widowmaker.
I use a very simple profile for my X-52. This profile only uses Radar Cursor assignments and other non-falcon stuffs. Related to Radar Cursor, I had to program mini stick position with “Advance Command” because I experimented the same issue that you have. In BMS I have ALT+Arrow to move the cursor, and after some testing I have realized that if you release ALT key before Arrow key, radar cursos will keep moving without stopping indefinitely. So, in STT with Advance Command I programmed “release sequence” releasing Arrow Key before ALT key. For both Press and Release command I adjusted the timing for the first key (Press–>ALT, Release -->Arrow) to 0, and for the last one (Press–>Arrow, Release -->Alt) to 100 ms. It works for me.
Hello everyone,
i tested this suggestion from gavilan with my Saitek X52 Joystick and it works for me. With this solution i have not to
change the registry. Maybe some others helps this profile file, that i have attached.I attachend the profile file
-
I had exactly the same problem. I had luck following the directions from this thread -> https://www.benchmarksims.org/forum/showthread.php?27042-X52-Ministick-Bands-Radar-Cursors-Issue-with-latest-saitek-drivers Thanks nomis
Essentially uninstall the current drivers and STT (profile software) and install these older drivers and STT software from the Saitek FTP site listed below.
"Driver version: 6.0.4.1
Software version: 9.9.9.9They are provided by these two files available at saitek ftp site (ftp://ftp.saitek.com/pub/software/full/)
Saitek_X52_Flight_Controller_SD6_64.exe
SST_Software_64_6_6_6_9.exePS.: It beats me why the SST version is “9.9.9.9” and the filename has “6_6_6_6_9” on it."
I was then able to use the X52 profile supplied in 4.34 and the mouse works fine now.
-
Even so I switched my X52 for an X65F I always had the ministick as cursor X/Y axes set up through registry by giving up the twist rudder. With the new setting for exponential curves and saturation for cursor X/Y that a difference like day and night compared to having the ministick setup with bands and keystrokes for cursor slew.
-
Hello oakdesign !!!
Thanks for your attention and help, it looks really good!
Take Care !!
malpaso -
I have the exact same problem as 16th Widowmakr, just that I’m using the Pro version of the X52.
The ministick works fine in Windows and when I calibrate the joystick. However, in the game it’s making the radar cursor move sideways and all the way down. In the Settings screen, I’m also getting the small blue line for the Y axis. The X axis seems to work fine. I used Blu3wolf’s Registry fix to get the X and Y axes into the game (instead of my rudder axis).
Does anyone know what else I can try to get it to work? It’s obviously working for other people and I’m sure it’s not a hardware error since it works fine in Windows.
I am using the 8.0.213.0 Logitech drivers. I am using only DX-Buttons, not the Logitech Profile software.
Screnshot of the Cursor Y issue: https://imgur.com/a/KjnSJYc -
If you are using the registry fix you still need a Logitech Profile loaded through the Logitech Profie software which is basically empty but has the ministick X and Y set to unnassigned.
And your screenshot is not available maybe upload it directly to the forum attachments -
If you are using the registry fix you still need a Logitech Profile loaded through the Logitech Profie software which is basically empty but has the ministick X and Y set to unnassigned.
And your screenshot is not available maybe upload it directly to the forum attachmentsI have set the ministick X and Y to unassigned in the Logitech software. Screenshot: https://ibb.co/V9gnvwV
Here’s a video of the almost unresponsive Y axis: https://streamable.com/k9ie26
These are the Registry modifications I have used (I checked that the ID is the right one, 0762):Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\Joystick\OEM\VID_06A3&PID_0762] "OEMName"="Saitek X52 Pro Flight Controller" "ConfigCLSID"="{A1902D8A-F8C8-483b-A5E3-D4FCB47CB264}" "OEMData"=hex:03,00,88,11,27,00,00,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] @="Precision slide" "Attributes"=hex:01,81,00,00,01,00,36,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] @="Rudder" "Attributes"=hex:01,81,00,00,01,00,35,00
I have also disabled the Ministick “Mouse” in Windows (in the device manager), because it was annoying. There was no change with or without it in regards to the Y axis.
What else could I try?FIXED IT
I have managed to fix this.
Install the official drivers (I have a Logitech one, so I used their latest drivers).
Then I disabled (unmapped) all the buttons in the Logitech software. The important thing is to hit the small blue crosshair button next to the “Views” button. That’s the button for actually loading/applying your profile. The icon in the taskbar should turn green and your MFD display should display your profile.
Then I applied Agave_Blue’s registry fix from here.
Then I assigned the X and Y axes in Falcon BMS.
Everything works now.