Hardware & Technical X52 pro: modes not working

I apologize for another "X52 pro help" thread, but I've been at this for 3 hours and a very simple functionality is not working.

I am trying to setup advanced commands when turning the "modes" wheel on the stick. I have followed all of the guides that I can find on the forums here, and also from the SAITEK website, but turning the modes wheel does not execute any commands.

I have setup an advanced command that is supposed to press "L-down-left-left-up" to deploy landing gear and set sys and engines to 3 pips each, when the mode wheel is changed. I have clicked the "macro" check box (I have tried with and without this). I have set the release command to press "L-down" to retract landing gear and reset pips. I have checked the controls in-game and the L and arrow keys are doing what I expect. Somehow the X52 is just not running the command.

Can anyone help? I'm pulling my hair out here, spending my whole day just trying to get this simple thing to work.
 
Modes arent supported in FD
There are a few posts were comments have been made on the fact.
Dunno why, perhaps they explain more.
 
There are alot of threads about people setting up modes, and even the saitek website has advice in their ED FAQ about setting up modes.

So was this changed at some point?
 
It may have changed since last I checked, but when I did it wasnt supported, so I could be wrong and you could be right.
Sorry
 
I have uploaded it here: https://www.sendspace.com/file/csy08z

Inside you find the Profile file and my Elite Bindings file. In case you want to try it ingame, than it should be sufficient to copy the file from the Bindings folder inside the archive to your Elite Bindings Folder. You should then be able to activate as a Preset it without loosing your own custom definition.
If you only want to take a look inside the Profile then it should be sufficient to open the .pr0 file ;)

Here is a short explanation of the actions when I switch modes:

Battle Mode: On activation deploy hardpoints, select highest threat Target and recofigure energy. On Leave retract hardpoints.
Flight Mode: On activation reconfigure energy distribution. On Leave balance energy distribution again.
Landing Mode: On activation deploy landing gear and reconfigure energy distribution. On leave retract landing gear and reconfigure energy distribution again.

I hope this helps :)
 
I have uploaded it here: https://www.sendspace.com/file/csy08z

Inside you find the Profile file and my Elite Bindings file. In case you want to try it ingame, than it should be sufficient to copy the file from the Bindings folder inside the archive to your Elite Bindings Folder. You should then be able to activate as a Preset it without loosing your own custom definition.
If you only want to take a look inside the Profile then it should be sufficient to open the .pr0 file ;)

Here is a short explanation of the actions when I switch modes:

Battle Mode: On activation deploy hardpoints, select highest threat Target and recofigure energy. On Leave retract hardpoints.
Flight Mode: On activation reconfigure energy distribution. On Leave balance energy distribution again.
Landing Mode: On activation deploy landing gear and reconfigure energy distribution. On leave retract landing gear and reconfigure energy distribution again.

I hope this helps :)

I hope it does too....I'm re-installing the drivers and software from scratch and then I'll test this.
 
Well, now doing anything in the SST software causes an immediate blue screen of death.

I don't think I'm going to be able to use the SST software.
 
Hmm I only get BSOD when I activate a profile twice between reboots, so everytime I change the profile I have to reboot first. Then it is working fine. I use it on Windows 7 and Windows 8.1
Sadly, the SST as well as the driver is a crappy peace of software, but I cannot play without it ;)
 
Last edited:
I have also the 7.0.27.13 Sofware, but with the 7.0.34.109 Driver. And I use a USB2 Port instead of USB3 for the x52 Pro.
 
Ensure you have the correct drivers and software for your windows version, this will happen if you install 32bit on a 64bit by mistake and vice versa. And I believe the X52 pro has some usb issues too, mine is about 5 years old and requires usb2, newer ones are usb3 I believe. I have also discovered that some Microsoft mice conflict with the built in throttle mouse, only solution I found for that was to get rid of the Microsoft mouse.

If its any help, I use sst version 7.0.27.13 and driver version 6.2.2.4 and I have no issues at all with win7 64bit.

I am on windows 7 64 bit and I've re-downloaded the software and the drivers three different times, including manually removing all traces of the drivers from the registry two different times.

This X52 Pro is brand new, and I'm running it through what I believe is a USB2.0 port. I have read about lots of problems with using the X52 Pro in a USB3.0, but I haven't seen any problems with the reverse. I do have a USB3.0 port, and I will try starting over from scratch with that one. Unfortunately the USB cord on the throttle is stupid-short, and on the wrong side of my desk setup, and the USB3.0 is on the back of the system :/

I am using a Razer Naga mouse, and so far, I haven't noticed any problems with the mouse button or movement on the throttle.

I will have to try to find the older version of the SST software; the newest versions are 7.0.39.0 for both the drivers and the software, and that's what I am using. I will try to locate the older version that you're using.

Thanks for the suggestions. I'll try this stuff in a little bit and report back.
 
Ok, I've done everything including going all the way back to version 6 versions of both the driver and the software, and the advanced command in the mode box just will not run.
 
I think I have a strong clue of what's going on. When installing the SST software, it comes to a step where it tries to get windows to install some drivers called "programmable support for keyboard", "programmable support for mouse" and "programmable hotkeys". Windows is failing these installations for some reason.
 
Ok, I fixed it!

Those drivers were the key, and the problem was sneaking past me each time because they're installed with the SST software, not the actual drivers.

What happens is windows tries to find the drivers for those "programmable support" items, but it can't because it isn't in the windows update system. So it gives up.

You have to manually connect these devices to the Saitek drivers in the device manager.

-click the windows button, type "device manager" into the search box.
- There will be a device called "programmable support"
- for each item underneath the programmable support tree, you need to manually connect that item to the saitek drivers
- right click the item, pick "Update Driver Software"
- select "Browse my computer for driver software"
- select "Let me pick from as list of device drivers on my computer"
- select the saitek drivers from the list

Do this for each of the items under programming support and you should be good to go!
 
Back
Top Bottom