X52Pro + Vista x64 - DirectOutput SDK wont install properly

[Slayer]

Driver Version 6.0.4.1
Software Version 6.0.10.7

I've tried the version that comes on the install CD. If I run the SaiFlightSimX.exe for FSX I get the message "The application has failed to start because it's side-by-side configuration is incorrect see the application log for more detail"

I removed all of the software and installed the newest SST 64 and SD6 64 from the saitek website.

The device drivers and profiler seem to work OK but the SDK will not properly install with this version of the drivers. It only created the DirectOutput folder and installed the following 4 files: Directoutput.dll SaiFlightSimX.exe, SaiFlightSimX.exe.manifest and SaiWinMediaPlayer.dll. The SDK subfolder is missing as are all the files contained therein. I've tried uninstalling, reinstalling , rebooting several times but it still fails to install properly and fails to work.

I opened the Saitek_X52Pro_Flight_Controller_SD6_64.exe using WinRAR and extracted the DirectOutput.msi. If I then open the .msi file it appears the SDK stuff is in there as well as the 64 bit dll's but it will not install any of this at all.

I've tried running everything as admin etc to no avail, redownloaded rextraced etc etc. Theres something wrong with the MSI file in the new drivers and the old DirectOutput doesnt seem to work with the newer drivers and software.....

[Slayer]

I discovered that when you install the newest drivers over the top of the CD installation, it will relocate all of the program files from: C:\Program files(x86), to C:\Program Files, except it leaves the 32 bit versions of those files there( the SDK)

hello world etc runs fine now. I still cant make the FSX MFD work though. I have a feeling is because its 32 bit and it has installed directoutput 64 bit drivers ( just a guess)

[Winglet]

Originally Posted by Slayer

I discovered that when you install the newest drivers over the top of the CD installation, it will relocate all of the program files from: C:\Program files(x86), to C:\Program Files, except it leaves the 32 bit versions of those files there( the SDK)

hello world etc runs fine now. I still cant make the FSX MFD work though. I have a feeling is because its 32 bit and it has installed directoutput 64 bit drivers ( just a guess)

I have the same issues with Windows 7 x64 as Slayer described.

I didn't used the CD installation, I direct downloaded the Saitek_X52Pro_Flight_Controller_SD6_64.exe and the SST_Software_64_6_6_6_9.exe, installed both but the MFD doesn't work in FSX.

Any help is highly appreciated.

[Winglet]

Originally Posted by Winglet

I have the same issues with Windows 7 x64 as Slayer described.

I didn't used the CD installation, I direct downloaded the Saitek_X52Pro_Flight_Controller_SD6_64.exe and the SST_Software_64_6_6_6_9.exe, installed both but the MFD doesn't work in FSX.

Any help is highly appreciated.

Problem is solved!!!

Another quote pointed me into the right direction: I checked my Windows\TEMP\Saitek-directory, found the x64 drivers and installed the DirectOutput.msi manually again. This fixed the problem.

[Winglet]

Originally Posted by Winglet

Problem is solved!!!

Another quote pointed me into the right direction: I checked my Windows\TEMP\Saitek-directory, found the x64 drivers and installed the DirectOutput.msi manually again. This fixed the problem.

I have to retract that it is solved... It worked - until I rebooted my computer.

So here is what I have done: De-installed all FSX and Saitek drivers completely. Deleted the adequate directories.

Then I installed FSX + Acceleration and the latest Saitek_X52Pro_Flight_Controller_SD6_64.exe driver. FSX prompted me for the SaiFlightSimX.exe which I accepted, but the SaiFlightSimX.exe doesn't show up in my Task Manager when FSX is running (and the MFD always shows 'Mode 1 No Profile')

DirectOutputService.exe is running.

The Hello_World.exe clears the MFD and shows nothing, when I exit the demo I see the 'Mode 1 No Profile' message again.

What else do I need to do to use the MFD in FSX?

[UKSupport]

Hi,

We're very aware that people are having trouble with the MFD and DirectOutput and we have a driver update which seems to fix it but we're waiting at the moment for a slot at the test lab for the driver to be run through Microsoft's driver signing process.

We'll let people know on here once it's been released, but it may be a while yet.

[Raptor007]

I'm glad to hear an updated driver is on the way!

In the meantime, the workaround that I've been using (in Windows 7 64-bit) is to restart the DirectOutput service whenever it stops working:

Originally Posted by Raptor007

If you need to reinstall the drivers after every reboot, it's likely that the DirectOutput service is simply not getting started automatically.

The first thing you should try is setting the startup type of the Saitek DirectOutput service to "Automatic (Delayed Start)" and reboot. Instructions can be found here:
http://www.saitekforum.com/showpost.php?p=79558


If that doesn't solve the issue, try creating a new text file with NotePad, with the following content:

net stop SaiDOutput
net start SaiDOutput

Make sure Windows is showing all file extensions, and rename the file "Restart DirectOutput.cmd". If you did it right, double-clicking the file should open a DOS console window and restart DirectOutput. Then put a shortcut to that file in your Start\Programs\Startup folder.