It’s not always easy, when installing software which is not up to date. So I had to do several tries, to get this up and running, but it has been worth every minute…
First of all install the saitek drivers (from website for win7 64bit, not the winXP-drivers from the cd) and check the software-entrys from windows, if the „Saitek DirectOutput Vxxx“ has been installed too. If not, go to the „C:WindowsTempSaitekSaitek_X52Pro_Flight_Controller_SD6_64_Drivers0000013“-folder and run the DirectOutput.msi.
After this check the following directories:
1) C:Program Files (x86)SaitekDirectOutput
If there is no file called DirectOutputX86.dll in the folder, copy the DirectOutput.dll and rename it, so that both filenames exists.
2) C:Program FilesSaitekDirectOutput
Do the same as with the files on (1)
3) Goto the SDK/Examples-Folder (in directory 2) and test the connection of DirectOutput with the both tools.
Here is a screenshot with the files in both directories:
When this is working you can proceed with the installation of the „X52 Pro Interface for FS9“
For this you should visit the blog http://blackswift.free.fr/blog and download“ version 1.0 and version 1.3 (you need both!).
* The blackswift-blog is no longer available online, so I provided the files on skydrive:
https://skydrive.live.com/redir?resid=2C735D4719418022!2998&authkey=!AKJnCdnf-YS_rlc
When the download is finished first install Version 1.0 to your FS9-folder. Then copy the „X52 Pro Interface for FS9.exe“ from version 1.3-zip to the „\FS9X52 Pro Interface for FS9“-folder and replace the original file.
That’s it – start the exe and you should get direct output is running – start flightsim and fsconnect should be activated also and on this point, the MFD is already working.
Thanks for this great tool!!
Hi!
Die blackswift website ist down und ich weiÖ? nicht wo ich das tool sonst herbekommen soll.
Bitte Hilfe!
Hab die Dateien jetzt am Skydrive hochgeladen – die beiden zip-dateien sollten frei zugänglich sein:
https://skydrive.live.com/redir?resid=2C735D4719418022!2998&authkey=!AKJnCdnf-YS_rlc
He super. danke! 🙂
Hello sir,
I’ve Saitek X52 pro and my computer Wın7 32bıt. I need ‚X52 Pro Interface for FS9 32 bıt‘, ıf you have this program please sent me. Thanks for your helps. Best regards.
a temporary Download-Link has already been posted in the comments above 😉
hello again sir,
Thanks for your fast answers:):)
However my Windows 7 32-bit operating system. Win 7 64-bit for the above program. Produced for 64-bit to 32-bit programs running?
Again my thanks for your help.
Regards.
The X52pro Interface should be 32bit Software an so also working on 64bit systems as described.
On 32bit systems you can jump over the step with the two program-files folders as only one exists.
Sicherlich hast du recht :),Nach dem ersten Flug in die Programmoberfläche sehr lustig. I hope google translate is correct.? 🙂 thanks again.
Yes, translation is quiet as well as in english.
have fun with this great tool 🙂
Dear Blackswift, I have been using for yeras X52pro interfase with FS9 without any problems with XP 32 bit however, I have a new computer with Windows 7 64 bit and I have followed the instructions above, I have tested the connection with DirectOutput and it works fine however, when starting the Interface it does not give any errors, but I do not see the Interface window splash screen with the connect and it is not running (I cannot see the process in task manager). Please, can you help or have any idea what might be happening, many thanks.
I know it’s very old post but meybae you can help me, I’m trying to work with the FS9 interface and:
– Saitek’s test file is working (from SDK).
– The Blackswift Interfaceis always crashing
Problem Event Name: APPCRASH
Application Name: X52 Pro Interface for FS9.exe
Application Version: 1.3.0.47
Application Timestamp: 468f5070
Fault Module Name: StackHash_6fec
I have installed VB6.0, I tried compatibility modes – nothing.
Hi Robert, old post, but still important for FS9 – hopefully also working on Windows 10…
Just noticed that I have a different version active (after flightsim re-installation) but also working.
Please try the X52-exe from this Link again: http://1drv.ms/1GVrB7b
This is version 1.2.0.45 (is this the default installer-version?) – working for me perfectly.
Compatibility mode should not be necessary.
Is it already crashing when starting without flightsim in „waiting for fsconnect“ position? then it seems to be an directoutput-problem… directories should be like the screenshot to work but it’s always a little bit try and error with the „good old things“.
Thank You, I’ll try at home later, for now i should maybe ask you if you using SD6 drivers or newer? I’m asking because I made mashup with SD6 (6.2.24) drivers and new SST software (7.0.39.0), it’s working with X52 1.3.0.47
Just took a look at my config – also had a mashup with SD6 (6.2.2.4) driver version but software 7.0.2.7 – I wouldn’t try to change it as long it is working and Win10 lets me keep this configuration.
By the way, it was crashing on drivers/directOutput newer than SD6, with open FS9 and without it.
I have one more question, where to find a list of command to use with LED? I have seen Autopilot, gear, flaps. I can quessing randomly but maybe is any doc with the list.
docs are included in the „reference manual.pdf“ which is in the FS9/“X52 Pro Interface for FS9″ folder.
examples and possibilities of [LEDs] section are described as commentary in the „X52 Pro Interface for FS9.ini“.
The only options are:
gear?, Autopilot?, flaps?, Landinglights?
for backup reason I put my LED-config section below:
; LEDs
; —-
; Color of the different LEDs on the controler. For each LED, the value
; defines the color:
; 0=Off, 1=On/Green, 2=On/Red, 3=On/Amber, Autopilot?ColorYes:ColorNo
;
[LEDs]
;Fire indicates „SAFE“ when Gear is locked (3 greens)
Fire=gear?1:0:0
;FireA+B indicates AP when activated
FireA=Autopilot?3:0
FireB=Autopilot?3:0
;FireD indicates Flaps Full|Set|Zero
FireD=flaps?2:3:0
;FireE and Clutch (I) indicates when AP is activated
FireE=Autopilot?1:0
;POV 2 indicates gear operations
POV2=gear?0:2:0
Clutch=Autopilot?1:0
Throttle=1
ToggleLeft=0
ToggleCenter=0
ToggleRight=0
ToggleLeft=Landinglights?0:3
Thank you so much, My LED config is a bit different (incl. now Landing Lights – By the way in my ref. manual is nothing about the Ladinglights)
[LEDs]
Fire=1
FireA=gear?1:2:0
FireB=flaps?2:3:1
FireD=flaps?2:3:1
FireE=1
POV2=Autopilot?2:1
Clutch=gear?1:2:0
Throttle=1
ToggleLeft=1
ToggleCenter=Landinglights?3:2
ToggleRight=1
But I checked it (this Landinglights) and it’s not working (X52 v1.3.47)
If Directoutput is running, but quitting saying „Device not found“ try run FS9 NOT in Administrator mode.