X-52 (non pro) Mini Stick and TDC Cursor
-
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?
-
yes, you can. However, you run into a limitation of DirectX, which is the number of axes you can have on one device - up to 8.
Stick X, Stick Y, Throttle, Stick Twist, Rotary 1, Rotary 2, and the Slider makes seven out of 8… and to use the throttle cursor would require adding two more axes.
You can do it, but you have to give up one other axis, to be able to add both the cursor X and cursor Y axes.
My preference is for the twist rudder to be removed.
http://falcon.blu3wolf.com/ - check out the right hand column, second from the bottom is the registry edit that removes the twist rudder and adds both radar cursor axes.
Should look like this:
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
As always, never run a registry edit without checking what it does. Hope that helps, if you have any questions feel free to ask!
-
You just said DirectX has axis limitation, I have always had this doubt in my mind, I’m building my own pit slowly and I’m programming my own board has a HID joystick to interface the switches and buttons.
Does directX has a limitation for the number of input buttons? Lets say, can a device have 200 buttons and be able to send those 200 buttons information to BMS or I must split the connections between several?
I’m asking this because I own a Satike X65F and BMS doesn’t recognize some buttons on the throttle. -
DirectX sets the limit to 32 buttons, 8 axis and a POV-Hat per device.
For cockpit building tips check out these two articles from BMS:
https://www.benchmarksims.org/forum/content.php?153-DirectX-Shifting-Facility
https://www.benchmarksims.org/forum/content.php?173-BMS-Cockpit-Builders-Guide
-
Ran the regedit and selected the ministick x and y but that controls the main cursor in BMS how do I program it to the TDC cursor in the FCR?
-
By default I believe the SST uses the throttle cursor to control mouse movement. You can set the programming of the that sithin the SST to none - the SST is not useful for this.
Within BMS setup page, click controllers and advanced - a window pops up where you can set which physical axis you would like to use for each axis in the game.
-
SST profiler has Mini Stick set to un-programmed. The Mini Stick axis is set to Cursor X and Cursor Y in the advanced setup in the Avionics Tab. But the TDC Cursor keeps moving down and to the right and I cannot control it with the Mini Stick. Any ideas? and it alsp no longer controls the main cursor in the game, that is controlled ny the mouse again.
-
I don’t think you can have it bothways, ministick controlling mouse and cursor on TDC.
-
Not sure why it would be moving down and to the right, if you open the advanced setup avionics tab, it should show what the axes are doing, where they are physically set to - if you move the radar cursor control when in that window, does it move around in the screen in that window?
If not perhaps the cursor is not reading correctly. If it does move normally there, then possibly something else is messing with the controls set for the radar cursor.
-
No its not moving normaly in the avionics tab. How do I uninstall the registry edit? Going to use a hat to slew the cursor.
-
Ay yi yi… correct fix requires some familiarity with regedit. You just renumber the axes in their original order - change the rudder axis to 3 and the ministick X to 8.
An easier fix is to delete the whole group from the OEM file in CurrentControlSet, but that has the problems that you 1) will probably have to uninstall/reinstall the stick to get the values back, and 2) if you delete the wrong group you could seriously screw with your computer.
was it slewing correctly when it was controlling the mouse? and which of the 3 registry edits on my site did you apply? Was it the X52 Pro one?
If you can get it working, it is significantly better using the thumbstick. For one thing, it moves faster or slower depending on how hard you push the cursor.
-
Hi Bluewolf. I have both Saitek X52 and Saitek Cessna Rudder, but in Windows Register I can only see axis for Cessna Rudder. I have checked the whole Win 7’s register and I haven’t found axis for X52.
I want to eliminate the twisting rudder axis of my X52 in order to use its mini stick for radar cursor control.
Do you know what could be wrong?
Thnanks and salute!
Gavilan -
It was slewing the main cursor ok but the antenna elevation is now messed up. Its no longer slewing the main cursor now though. The axis don’t show movement any more in the advanced avionics screen either. Is there a Calibration program somewhere?
-
I downloaded the one for the X-52 not the Pro.
-
UPDATE when I select the mini stick axis for Cursor axis x and y the TDC cursor moves down and right constantly. When I select keyboard for the Cursor x and y the mini stick moves the main cursor in the game just fine and the TDC cursor works normally.
-
@16th:
UPDATE when I select the mini stick axis for Cursor axis x and y the TDC cursor moves down and right constantly. When I select keyboard for the Cursor x and y the mini stick moves the main cursor in the game just fine and the TDC cursor works normally.
You might want to add a little bit of deadzone to the x and y of the ministick. I owned 4 Saitek joysticks until today and i found that every single one of them needed deadzones on the ministick.
-
Tried the Large Deadzone setting and still no joy.
-
Hi Bluewolf. I have both Saitek X52 and Saitek Cessna Rudder, but in Windows Register I can only see axis for Cessna Rudder. I have checked the whole Win 7’s register and I haven’t found axis for X52.
I want to eliminate the twisting rudder axis of my X52 in order to use its mini stick for radar cursor control.
Do you know what could be wrong?
Thnanks and salute!
GavilanRun the regedit, it should replace the X-52 axes only without touching the cessna ones… they have different OEM numbers.
-
@16th:
It was slewing the main cursor ok but the antenna elevation is now messed up. Its no longer slewing the main cursor now though. The axis don’t show movement any more in the advanced avionics screen either. Is there a Calibration program somewhere?
Windows is supposed to auto calibrate joystick axes based on raw input… keyword “supposed to”.
How is the antenna elevation messed up? It sounds like the directX axes are not working correctly for the ministick. If its not working for the antenna thats bad too.
When I get to my computer Ill recheck the file, but thats the same registry settings I used for my X-52 non-Pro…
Honestly what you are describing sounds like incorrect values in the regedit that was applied… can you screenshot that folder of your registry?
-
Compared the registry values to the values in the file I downloaded and they are the same. The antenna elevation doesn’t have the range it used to. I have attached a pic of the setup avionics page.
The Radar Antenna small rotary is maxed out and only moves as far as shown. The X and Y only move slightly when the mini stick is moved thus the difference in the next pic