Can't load Saitek X52 pro 64bit profile

[335th_GRAthos]

OK, then,

you should check whether the SST_Software_64_6_6_6_9.exe (229Mb) is compatible with your X52Pro and if so, download this one and install it.


~S~

[zl2bmh]

Hello All.

Why use SST at all, can smeone tell me that. I have CLoD and a X52Pro controller, and just configured the game from the 'keys and axis'. No need for SST. I am very interested to know why SST is used.
regards,
zl2bmh jim.

[335th_GRAthos]

Originally Posted by zl2bmh

Hello All.

Why use SST at all, can smeone tell me that. I have CLoD and a X52Pro controller, and just configured the game from the 'keys and axis'. No need for SST. I am very interested to know why SST is used.
regards,
zl2bmh jim.

How about pressing the key ... on your joystick and that will:
Open the cockpit
open radiator
open oil radiator
turn off mirror
turn fuel cock on
select eng #1
turn magneto on eng#1
set prop pitch to 12:00 eng#1
set throttle to 20% eng #1
start engine #1
select eng #2
turn magneto on eng#2
set throttle to 20% eng #1
set prop pitch to 12:00 eng#2
set throttle to 20% eng #2
start engine #2
select all engines
(with all the required delays between the keystrokes)


or a key to
eject the cockpit cover
bail out

[Flying H]

SST is there so you´ll be able to configure 3 modes and 2 shiftsates to all your buttons on the stick. If you learn to set it up to full you´ll rarely have to use your KB! AND you can activate your setup with two clicks from your taskbar icon. That´s the beauty of the SST! If you don´t use the full features of the stick and supporting programs you should have bought a lesser (cheaper) setup!

[zahnartz62]

I have an ingame profile which includes many key board keys to keep it simple. I have the x52pro with updated sst SW..I would like to use the modes and mulitple key commands as mentioned above but was not sure it would work in CoD.. If I do a new SST profile, may I assign command keys as I choose, the ones originally used by Cod, or the ones I have changed for ingame profile use?? I am new to this so your advice welcome. Mode one for general flying and combat, mode 2 for takeoff and landing, mode 3 for emergencys..? IR5 frees up many keys and helps me keep it simple. GRSwaty command index forms above have motivated me to do a new SST profile and I assume it will be recognized by CoD?? These aircraft were flying when I was a boy..I remember a simulator I ordered and it was a cardboard box theater with the AC hung and flown by thin strings..??!! Things have changed and I am delighted to have RoF and CoD. Many modern AC are beautiful..but the Spit, Emil, Bf110 etc..the sim plus my history books equal hours of pleasure. I finally landed the 110 and didn't know it!!

[SEE]

For SST, you use the keyboard keys that are used by CloD - these will either be the original ones or ones you assigned to replace the original ones.

You can create and save different custom key assignments in CloD and load them (when in clod) if you want to use different keystrokes to work with different joytsicks and use a different SST files to suit.

[salmo]

Still having great problems setting up my X52 Pro stick & throttle.

From device manager:
Saitek X52 Flight Controller (HID) driver ver 5.5.0.82
Saitek X52 Flight Controller (USB) driver ver 5.5.0.82
SST Saitek Pro Flight software ver 7.0.2.7

No device errors in harware manager. Magic bus setup appears to be OK. I've tried to update device drivers by (1) windows 7 automatic update search (reports driver are up to date) & (2) by running the Saitek_X52Pro_Flight_Controller_SD6_64 driver exe from Saitek (launches OK but then get to a "plug Saitek device in" screen with a greyed out Next button. When I plug the controller in, nothing happens & the driver update does not progress any further).

Here's my symptoms:
1. I can load & edit X52 Pro profiles OK in the SST editor software.
2. Using the "test profile" button in the SST software fails, no mapped keystrokes are being sent to the screen (or to notepad).
3. Loading a saved profile fails with error "Salmo.pr0 does not contain a profile for this device. The device has not been profiled".

I wonder what device driver versions do pilots have? Does anyone have ver 7.0.2.7 (same as the SST sofware)?

[ramstein]

Win7 with X64
---------
Saitek_X52Pro_Flight_Controller_SD6_64.exe
Driver:6224
file size = 4,260 kb
===========

Software:7027
Smart_Technology_7_0_2_7_64bit.exe
file size = 58,855 kb
========

sizes and names were read off the control panel / 'about' tab, when you right click the icon in the task bar..
=====
From device manager:
Saitek X52 Flight Controller (HID) driver ver 6.2.2.4 Date 4/4/2008
Saitek X52 Flight Controller (USB) driver ver 6.2.2.4 Date 4/4/2008
====

when you install the drivers, you must only plug in the stick when it asks you to, not before..
if you messed something up, you might need to do the complete Saitek removal procedure, which not only includes uninstall through control panel, but removing registry entries for Saitek,,, (don't screw up and remove files you want to keep...).
There are more procedures if you need to do a real clean sweep, but you probably hopefully don't need to..

It's possible, you either got the wrong file, got the wrong profile for the software version. Or, when you try to place a correct file over a wrong one, it is not overwriting the old file with the new corrrect one.

Also, I personally never use 'Windows Update' for the Saitek update.. it has no clue... it just wants you to use a file it thinks you might need..

btw, do you use the Saitek forum ??

[SEE]

You are using an X52 Pro (Black) and not a X52 std (silver/Black) - the drivers are different - each needs the correct driver.

BTW, Is the first X52 that has been installed on the PC?

Do you have access to another PC or Laptop?
If so, install the stick using the correct Saitek driver for the windows OS version installed (to eliminate any possible fault in the stick itself).

Once the Driver has been installed - open Control Panel and check the driver has installed correctly by checking that you can access all the features for the X52 Pro, such as LED/MFD brightness, deadzone adjustments etc.

Then Install the SST software and see if it works.


If it works on another pc then I would delete SST, the registry files for Saitek, etc, then re-install again but using a different USB port

[Ra'Kaan]

Originally Posted by salmo

Still having great problems setting up my X52 Pro stick & throttle.

Here's my symptoms:
1. I can load & edit X52 Pro profiles OK in the SST editor software.
2. Using the "test profile" button in the SST software fails, no mapped keystrokes are being sent to the screen (or to notepad).

I was dealing with these two exact issues recently but also, custom profiles were not working in-game - only the main axes and primary buttons such as fire. Anything I had programmed in the profile editor were not working in game.

Here is what I did to correct all these issues.

Your *.pr0 files should be located in:

C:\Users\Public\Documents\Saitek SD6 Profiles.

I advise making a copy of this folder in a safe place just to be sure, but the install routine described below will not delete these files.

1.) Download Correct Drivers and Software: <--- Click

Selecting from : Pro Flight range
Selected product : X52 Pro
Selected OS : Windows 7 and Vista 64 bit

2.) Leaving X52 Pro plugged in - Un-install both software and drivers.

There are two entries in Control Panel\Programs and Features:

a. Smart Technology Programming Software 7.0.2.7 (Mad Catz)
b. Saitek DirectOutput 6.2.2.4 (Saitek)

3.) (IMPORTANT) UN-PLUG the X52 Pro and Rudder pedals (if you have them.)

note: At this point I did not re-start the computer although it may be a good idea to do so just to make sure the drivers are unloaded.

4.) Re-Install new Drivers then Software (In that order)

a. Run the Saitek_X52Pro_Flight_Controller_SD6_64.exe and plug in the X52 Pro and rudders when told to.
b. Run the Smart_Technology_7_0_2_7_64bit.exe

Now I was finally able to test my profiles in the built in profile tester, and also, my profiles were working in games again.

I have a sneaky feeling this issue started from installing fresh drivers without un-installing old ones first.