X52 Pro and FS2004: MFD can now be used.

[UKSupport]

Are you using the latest beta drivers and software from the Announcements section here on the forum?

[bv2el]

Originally Posted by UKSupport

Are you using the latest beta drivers and software from the Announcements section here on the forum?

Yes, I'm using the latest beta drivers and software from the Announcements section here on the forum.

[UKSupport]

That's odd then, because no one else has reported it. What's the driver version number showing in the About tab in the Properties for the X52 Pro in Device Manager, and are you definitely using a 32-bit version of Vista?

[wassupben]

Originally Posted by UKSupport

That's odd then, because no one else has reported it. What's the driver version number showing in the About tab in the Properties for the X52 Pro in Device Manager, and are you definitely using a 32-bit version of Vista?

Originally Posted by bv2el

I did rename DirectOutput.dll to DirectOutputX86.dll in C:\Program Files\Saitek\DirectOutput folder.
I installed this software, but it doesn't work for my X52 pro & always show me "No X52 Pro Flight Control System Found. Exiting.".
but my X52 pro works fine for my FS2004, what can I do for this problem ?

I Have a same problem on it.

==========
CPU:
Intel(R) Pentium(R) 4 CPU 2.80GHz

DirectX Info:
Version 9.0c Long Version 4.09.00.0904

Display Device:
Radeon X1600 Series (Omega 3.8.330) Driver 6.14.10.6660
Description Radeon X1600 Series (Omega 3.8.330)
Manufacturer ATI Technologies Inc. (Omega 3.8.330)
Total Local Video Memory 520 MB
Total Local Texture Memory 520 MB
Driver File ati2dvag.dll
Driver Version 6.14.10.6660
Driver Details 8.33-061220m-040997C-ATI-OMEGA

Sound Device:
Description SB Audigy 2 Audio [8000]
Manufacturer Creative Technology, Ltd.
Driver File ctaud2k.sys
Driver Version 5.12.4.1196

Description SB Live! Audio [8400]
Manufacturer Creative Technology, Ltd.
Driver File ctaud2k.sys
Driver Version 5.12.4.1196

Memory Info:
Total Physical Memory 2.00 GB

USB Devices :
Description Saitek X52 Pro Flight Controller (USB)
Driver Date 5-1-2007
Driver Version 6.0.4.1
Device Class Human Interface Device

Description Saitek Pro Flight Rudder Pedals (USB)
Driver Date 5-1-2007
Driver Version 6.0.4.1
Device Class Human Interface Device

Description NaturalPoint TrackIR 4
Driver Date 12-6-2006
Driver Version 3.2.30.0
Device Class Universal Serial Bus Controller

Operating System Info:
Name Microsoft Windows XP
Version 5.1.2600
PlatformId 2
Service Pack Service Pack 2 (v2.0)


I think those information can help to fix the problem.


Thank you

Regard
Ben

[UKSupport]

Are you able to get the sample apps working that are provided in the SDK folder? Go to C:\Program Files\Saitek\DirectOutput\SDK\Samples\OutputTest and run the OutputTest.exe file. See if that will output the correct text as you input it to the MFD.

[micky1803]

Hi,

first many thanks to BlackSwift for programing that wonderful tool. It is that what we need and it works fine.
I have only the problem that with the Flight 1 ATR and the Level-D 767 the main gauges in the VC are not visible if the tool is loaded. In 2-D they are okay. The main gauge of the 767 shows many crazy lines like painted by a child. Have you an Idea what is wrong? For Example the Feelthere ERJ 145 and the CS 757 working fine in the VC.

Thank you

Michael

Germany

[wassupben]

Originally Posted by UKSupport

Are you able to get the sample apps working that are provided in the SDK folder? Go to C:\Program Files\Saitek\DirectOutput\SDK\Samples\OutputTest and run the OutputTest.exe file. See if that will output the correct text as you input it to the MFD.

I tried the Output Test, it's ok show the text on my MFD.

[bv2el]

Originally Posted by wassupben

I tried the Output Test, it's ok show the text on my MFD.

I did same thing & also showed the text on my MFD.

[UKSupport]

In that case I think you'd best contact BlackSwift, because it would appear to be something in his plug-in that isn't quite working correctly. If the OutputTest works then we know that the communication with the X52 Pro is working.

[CheeseJai]

Originally Posted by bv2el

I did rename DirectOutput.dll to DirectOutputX86.dll in C:\Program Files\Saitek\DirectOutput folder.
I installed this software, but it doesn't work for my X52 pro & always show me "No X52 Pro Flight Control System Found. Exiting.".
but my X52 pro works fine for my FS2004, what can I do for this problem ?

I have the same problem.... i'm a HongKong user... i'm wondering if the x52pro share the same Product ID around the world? coz in the log saying "GUID" difference stuff... quote from the log:

22:15:48 No X52 Pro Flight Control System found. Controler GUID is {06DA293B-3F4F-FA1E-024F3F0000000000}. Exiting

however, i can install the universal driver for x52pro provided by saitek website........ so it confused me ....

[UKSupport]

Are you able to run the OutputTest program and get response on the MFD and stick LEDs?

[CheeseJai]

Originally Posted by UKSupport

Are you able to run the OutputTest program and get response on the MFD and stick LEDs?

yes, i can see what i type....

[CheeseJai]

ok guys, here is the log file generated from blackswift's programme as an attachment... it is very appreciated if u can help me fix it!

i can't wait to use such great function on my FS9...

[Spksh]

Originally Posted by CheeseJai

ok guys, here is the log file generated from blackswift's programme as an attachment... it is very appreciated if u can help me fix it!

i can't wait to use such great function on my FS9...

On Blackswift's site, he says to use the latest drivers, but not the beta drivers.

If I recall his code correctly, he's looking for a specific GUID that represents the X52 Pro. His app isn't finding the GUID it expects (probably because you're using the beta drivers) and so throws an exception.

Blackswift needs to update his app to work with the beta, or you could go back to the latest non-beta drivers/SST package.

EDIT:

Hmm... I don't have FS2004 myself, but I just tried the app:

16:12:23 X52 Pro Interface for FS9 started.
16:12:23 Log enabled.
16:12:23 DirectOutput folder is "C:\Program Files\Saitek\DirectOutput".
16:12:23 Timer tick occurs every 250 ms.
16:12:23 Refresh occurs every 20 ticks (5000 ms).
16:12:23 Boost mode at startup: no
16:12:23 Pages list:
16:12:23 Page 1: Aircraft
16:12:23 Page 2: Location
16:12:23 Page 3: AltHdgSpd
16:12:23 Page 4: Fuel
16:12:23 Page 5: COM
16:12:23 Page 6: NAV
16:12:23 Page 7: XPNDR
16:12:23 Page 8: ILS
16:12:23 Page 9: Lights
16:12:23 Page 10: Weather
16:12:23 Page 11: Checklists
16:12:23 Page 12: Airports
16:12:23 Page 13: Copyright
16:12:23 DirectOutput Initialized.
16:12:23 DirectOutput Device Change Callback registered.
16:12:23 DirectOutput devices enumeration performed.
16:12:23 DirectOutput controller found.
16:12:23 Found device: X52 Pro Flight Control System
16:12:23 Unregistration of DirectOutput Device Change Callback done.
16:12:23 Timer set with a tick every 250 ms.

So it's finding my X52 Pro fine, and I'm using beta2.

Are you using the latest version of Blackswift's app? Maybe try downloading it again. What driver/SST version are you using?

[Spksh]

If Blackswift's VB example code matches his app, the GUID he's looking for is this: 06D5DA29-3BF9-204F-85FA1E02C04FAC17