Hardware & Technical Saitek X52 Pro - Works, but no Mouse stalk/scroll wheel controls?

Gunshow

Gunshow
[Solved] Saitek X52 Pro - Works, but no Mouse stalk/scroll wheel controls?

Hello all, (I know this is technically off-topic and deserving of the "hardware & technical" pit, but there is little to no exposure there, and I need some help ASAP)

Quite lost on this one, annoyed too because I was all geared and ready to play PP last night too, Google didn't turn up anything much of relevance.

I've recently formatted my OS and reinstalled the drivers and programming software I was using for ED previously which worked perfectly with no issues, however now the mouse stalk/ministick, mouse button, scroll wheel and scroll mouse button on the throttle are no longer controlling my cursor in Windows or in-game where they did before.

Opening the control panel, all movements and inputs are being registered as they should, also all other throttle axis and buttons work in-game.

Really hoping someone with more know how than I can give me some pointers to get this working as it should again so I can get on ED to try out 1.3!
 
Last edited:

Ferret06

Ferret06
Valethar said:
Make sure to disable any binds in the profile. Those can block functionality as well, especially in ED.
Click to expand...

To go into a bit more detail.

If it's anything like it was for my standard x52.

Open the profile editor, then go to programming.

In there on mine when i installed it had 6 modes to use, delete the 3 that are using the pinkie switch as the mode shift key.

Worked for me.

Hope that makes sense :)
 
Last edited:

b0rg9

b0rg9
Uncheck the clutch mode in the MFD tab??? I'm hunting around looking for answers too. Mine seems to be fine but I don't use the profile software and just have stuff set in the .bind file in-game.
 

Gunshow

Gunshow
Ahh, spotted this did get moved over. Shame, I'll reply anyway in the hope that *someone* can still see this.

I have already deleted the "shift" profiles so there are only 3 modes. The clutch mode is also disabled in the control panel.

Annoyingly, like I said, all other buttons and axis' work and are usable in game, the only things that aren't working are:

- Mouse stalk (for use in menus etc)
- Button below that for Mouse 1
- Scroll wheel
- Scroll wheel button

All of these I was using and had worked prior to my format, so I'm not sure what I'm missing
 
Last edited:

CMDR Pewp

C
I'm having the same problem. My mouse nub doesn't do anything, in game or in OS (Win 7, x64) the game doesn't recognize the inputs or the "mouse" button, or scroll wheel - oddly enough in the default x52 Pro profile it DOES still use the scroll wheel button to toggle flight assist.

I hope someone figures this out...

One thought is that I do use a Razr mouse and keyboard, and perhaps their drivers and/or Synapse interfere with the mouse stick being used - but the Saitek driver control panel shows the input, so I know the hardware is fine... odd.

- - - Updated - - -

Oh, and while the x52 Pro in-game profile does see the scroll wheel button, if I make a custom profile, it doesn't see it any more... very strange... and I'd also like ot add I am about 8 hours into this problem, I've installed and reinstalled and uninstalled and reinstalled every driver and profiler for the joystick multiple times. I am VERY well aware of the need to modify the profiler software's default profile to remove shift modes, I have clutch turned off, I have read and followed dozens of threads here, on reddit, and on some Star Citizen and IL-2 sites (where most people want to know how to turn the mouse nub off, because they bump it) ...

I just want it to control the UI mode and/or freelook.
 

DeimosXid

D
I just got the x52 Pro and am having the same problem. The Saitek Control Panel and Profiler correctly detects that I move the mouse nub around but no matter what settings I use, it does not seem to translate into mouse movement or key presses in or out of game (it's supposed to also be able to move the mouse in other applications and the desktop, right?)

I've found that if you set the mouse click, scroll wheel, and scroll wheel click to "Unprogrammed" in the profiler, Elite will then recognize them and allow you to bind them to actions in-game. But this doesn't help with the little mouse stick itself, which I want to use for headlook.

Some questions though, what OS are you running? And when you reinstalled the x52, did you have it unplugged at first and then only plugged it in when the installer told you to? I wonder if it was a mistake for me to plug the devices in before starting to install the drivers and software...
 

Gunshow

Gunshow
I am so glad that it's not only me that's having this issue!. Looking around online I've found more people asking how to *disable* mouse movement with the stalk than anything else...

Exactly the same for me, Saitek control panel and Profiler both acknowledge and track movement on the stalk and mouse buttons, but does not apply any movement in or out of game. I can confirm that prior to the new OS install, the stalk, buttons and wheel did all work in Windows.

My OS is Win 7 Professional, x64. I think I did also plug the device in before installing drivers, however, to the best of my knowledge, I have since; manually removed the software, drivers and edited the registry to complete remove them and attempt again, no fewer than 3 times, but always the same issue.

Everything goes as planned, the only thing that stands out to me as odd, is after installing the drivers, installing the Profiler triggers Windows to acknowledge the hardware again and register drives for "programming of hot keys" and "programming of keyboard and mouse", however these all fail.

- - - Updated - - -

I have also opened a support ticket with Saitek/MadCatz for this, but I've yet to hear back (although I wasn't expecting them to over the weekend anyway).

If I hear back and have any progress I'll post the steps here
 
Last edited:

Gunshow

Gunshow
Right!, I've managed to solve the issue with me, hopefully the same works for you guys. It's a bit of information I managed to eventually find from Google. Seems to be a problem with conflicting drivers from a failed installation.

Here are the instructions you have to follow them all or the same problem happens again:

1. Unplug your device from the computer

2. Uninstall the drivers:
  • Control Panel > Device Manager > Human Interface Devices > Uninstall 'Saitek X52 Flight Controller'
  • Control Panel > Device Manager > Programming Support > Uninstall all Programmables
3. Uninstall the SST programming software & Saitek DirectOutput

4. Delete the Saitek/MadCatz folders from the following paths :
  • C:\Program Files
  • C:\Windows\Temp
5. Delete Saitek registry entries:
  • Press and hold the Windows key on your keyboard and then press the letter R. This will open the Run box. Type regedit and then click ok.
  • The Registry Editor will have a list of folders on the left hand side. Go down into the following folders in order by clicking the + next to the folder name.
+HKEY_CURRENT_USER
+System
+CurrentControlSet
+Control
+Media Properties
+Private Properties
+Direct Input

  • Delete any folder inside the Direct Input & Joystick>OEM folder that begins VID_06A3.
6. Reboot

7. Disable/disconnect Internet Connection

8. Install the latest drivers and DO NOT PLUG IN YOUR X52 until the install program ASKS you to or you will have to redo this whole process.

9. Install SST Programming software, Windows should begin checking for drivers for programmable support for keyboard, mouse and hotkeys.

10. Ensuring Mouse X and Y axis are bound to Mouse X and Y on your profile, Save and then test.
 

DeimosXid

D
Thanks! I'll give this a try. Was the problem solved for you completely? And after doing this did the little stick on the throttle immediately start controlling the mouse? Was the SST Programming software required for it to work?

EDIT: Oh praise Braben, it works!!! This makes me ridiculously happy. Cheers!
 
Last edited:

hubo

hubo
I have the same problem with latest 1.3 and the latest Saitek Driver 7.0.39.0 with my Saitek X52Pro. Mentioned steps didn't worked for me. I even did not installed SST Programming Software back (not using it).

But I found another strange thing. When I put the mode selector (1/2/3) between two positions then the game is able to detect at least the scroll wheel, scroll wheel button and mouse stalk button. And they are displayed like [X52PROB16], [X52PROB17], [X52PROB18] and clicking the scroll wheel shows its icon properly. As soon as I get the mode selector back to some position, it will disable the buttons.
 

DeimosXid

D
For me, I had to install the SST Programming Software for the mouse to work.

Also, like I said before, if you set the mouse click, scroll wheel, and scroll wheel click to "Unprogrammed" in the profiler, Elite will then recognize them and allow you to bind them to actions in-game.
 

hubo

hubo
Ok, so I have installed SST Programming Software back and create (and apply) the new profile where I set the problematic buttons to Unprogrammed. Buttons are now recognized in game as [X52PROB16], [X52PROB17], [X52PROB18], but mouse is still not working. Even if I try to set the head look axis, it is not reacting even to a real mouse movement, so it is not possible to map back to mouse (if I change it).

SOLVED: Problem was with the ST Programming Software and it's update 7.0.39.0 from previous version. I had to open Device Manager and rollback the previous driver for Programming Support -> Programmable Root Enumerator. Then other devices apears (with the error sign) like Programmable Hotkeys, Programmable Support for Keyboard and Programmable Support for Mouse. I removed them one by one with the remove driver option and then I removed even the older version of Programmable Root Enumerator (which was without the error sign). Then I unistalled even the ST Programming Software. (I think I was asked to restart the computer after removing the devices or uninstalling the software, so I done so.) After that I installed the latest ST Programming Software 7.0.39.0 again and after successful installation all mentioned devices reapears in the Device Manager without the error sign and mouse ministick starts working immediately.

ST Programming Software is responsible for mouse emulation (using the ministick, button and scroll wheel) and Elite is not detecting/supporting the ministick itself, so that's why is the ST Programming Software needed to have the ministick working. Using the ST Programming Software, Elite is actually detecting a mouse movement (and not the ministick).
 
Last edited:

Tapirninja

T
Gunshow said:
Right!, I've managed to solve the issue with me, hopefully the same works for you guys. It's a bit of information I managed to eventually find from Google. Seems to be a problem with conflicting drivers from a failed installation.

Here are the instructions you have to follow them all or the same problem happens again:

1. Unplug your device from the computer

2. Uninstall the drivers:
  • Control Panel > Device Manager > Human Interface Devices > Uninstall 'Saitek X52 Flight Controller'
  • Control Panel > Device Manager > Programming Support > Uninstall all Programmables
3. Uninstall the SST programming software & Saitek DirectOutput

4. Delete the Saitek/MadCatz folders from the following paths :
  • C:\Program Files
  • C:\Windows\Temp
5. Delete Saitek registry entries:
  • Press and hold the Windows key on your keyboard and then press the letter R. This will open the Run box. Type regedit and then click ok.
  • The Registry Editor will have a list of folders on the left hand side. Go down into the following folders in order by clicking the + next to the folder name.
+HKEY_CURRENT_USER
+System
+CurrentControlSet
+Control
+Media Properties
+Private Properties
+Direct Input

  • Delete any folder inside the Direct Input & Joystick>OEM folder that begins VID_06A3.
6. Reboot

7. Disable/disconnect Internet Connection

8. Install the latest drivers and DO NOT PLUG IN YOUR X52 until the install program ASKS you to or you will have to redo this whole process.

9. Install SST Programming software, Windows should begin checking for drivers for programmable support for keyboard, mouse and hotkeys.

10. Ensuring Mouse X and Y axis are bound to Mouse X and Y on your profile, Save and then test.
Click to expand...

Worked perfectly! Thx for info. :D
 

ArmsLikeNoodles

ArmsLikeNoodles
It does indeed appears the Windows 10 beta drivers are signed and able to resolve windows 7 user issues with the mouse buttons on the throttle

For a clean install go to ftp://ftp.saitek.com/pub/software/beta/Windows10/
and pick up the driver and software downloads for your x82 or x64 system (ignore that it's for win 10)

1 Go to Control Panel > Programs and Features sort the Publisher Column and uninstall:
Saitek/Mad Catz Programming Software
Saitek Direct Output, or any additional software related to your product from Saitek/Mad Catz.
2 Go to Control Panel > System > Device Manager:
Locate the section called Programming Support and open it by clicking the little arrow next to it.
Right click and uninstall each entry in Programming Support.
When prompted, select the option to delete the driver from the system.
3 unplug the HOTAS USB connection
4 Reboot your PC.
plug in the HOTAS USB connection
Install the new product driver. (It will more than likely make you restart and then continue the installation)
Install the new programming software.
5 Set up some bindings using the profile software, load them into the active profile and use the test button in the software.
??? Profit.

PS at the time of testing I have had success with version _7_0_42_12_x64
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom