X52 Pro FSX plug-in does not work

[OT2]

I am new here, but had been reading this thread with some interest. Having just bought a X52 Pro for use with FSX Acceleration, I had installed the drivers and the programming software prior to receipt of the unit. I was looking forward to plugging and playing without delay. I plugged in the unit and found no MFD except for the mode (1, 2, or 3) and the stopwatch. After what I had read here and seeing it all on my unit, I felt like I had made a bad investment. After fiddling around a little, I uninstalled all the Saitek software and rebooted and then installed the downloaded (not beta) drivers only (with the joystick unit connected to my USB). I now have my MFD and it comes up each time I start up FSX for the day! All my settings are done conventionally with the FSX options/controls tab. I am running Windows 7 64 Ultimate.

John

[marquisor]

i can't believe it!

the problem exists SINCE YEARS now! is saitek not be able to get a DECENT version out? we are in times of 2010 with vista, win7 and not with HID devices from 1998 running on Windows ME-reboot-pray'n'have-luck times!!!
it STILL doesn't run. look at my posts, when i wrote about issues back in 2007!!!

and reinstalling FSX/WINDOWS is NO GO! go and get your products and software running or customers buy elsewhere!

[OPTIMIST6]

My first message in this topic was 24 of May, 2009...

I appreciate greatly with this product... thanks saitek but....but... mfd ahhh mfd...

mfd is only green display for me... and renamed it as OGD (only green display)

İt's useless for me

[nikiddawg]

Hi,
I have posted about this on a couple of the other threads addressing this issue. I count at least 5 different threads on this topic so there must be many more and they go back to 2007 if not earlier.

It's really pathetic Saitek. You have known for years that the MFD is useless and is actually not compatible with FSX yet you continue to market it as fully functional with FSX and lie to people that more profiles will be released in the near future. What a crock. I'm contemplating contacting the authorities regarding your false claims and false advertising. In America, where I am, there are laws against this type of false advertising and deception.

BOTTOM LINE: THE MFD HAS NOT WORKED AS ADVERTISED. THE MFD DOES NOT WORK CURRENTLY. THE MFD WILL NEVER WORK!

Why don't you just own up and come clean and offer anybody who purchased the X52 Pro a refund since they purchased it under the false pretence that the MFD was a fully functional feature of this product?

[UKSupport]

I'm afraid you're incorrectly assuming that just because you and and the other people in this thread have this issue, that this:

a) Has always been the case
b) Is affecting everyone

The software team have a vast catalogue of products to support and any reported issues get assigned a priority: this is on top of the work they have to do otherwise, including developing for new products of course. We have been looking into this issue for a while now but, given that we don't have infinite resources, we have had to reprioritise it several times due to other projects.

We thought we had it fixed just before Christmas in fact, but then the testers discovered a problem and the software guys had to take another look. I'm sure you would rather we released an update that fixed the problem, rather than causing new ones.

[nikiddawg]

Originally Posted by UKSupport

I'm afraid you're incorrectly assuming that just because you and and the other people in this thread have this issue, that this:

a) Has always been the case
b) Is affecting everyone

The software team have a vast catalogue of products to support and any reported issues get assigned a priority: this is on top of the work they have to do otherwise, including developing for new products of course. We have been looking into this issue for a while now but, given that we don't have infinite resources, we have had to reprioritise it several times due to other projects.

We thought we had it fixed just before Christmas in fact, but then the testers discovered a problem and the software guys had to take another look. I'm sure you would rather we released an update that fixed the problem, rather than causing new ones.

So basically, if I understand you correctly, those of us unfortunate enough to experience this problem are forced to live with it for an indefinite period of time (permanently?) as this issue gets backburnered (and made a lower priority) while your software team works on other projects, "including developing for new products of course" which would be potential revenue generators (and thus higher priority) rather than serving your existing loyal customer base.

That's great. Like I said....HORRIBLE CUSTOMER SUPPORT!

I'm going to post this string on other websites so that truth gets out there. I'm going to contact all of the gaming websites that support the gaming community and share this information with them. I'm going to share this with your competitors so they can see what their competitor is doing wrong so they can be sure to do things right. People have the right to know how atrocious this product is; how it doesn't deliver on what was promised; and how unresponsive Saitek is at supporting the products they sell.

I can't wait to ebay off my Saitek rudder pedals too (I've already ebayed my Cyborg Evo force feedback and my Pro Yoke and throttle quadrant and returned my Pro X52 to the place of purchase). You've lost me for good Saitek.

[pulsar21]

I can understand how you feel nikiddawg....it's a shame what saitek perform.
People are complaining about this issue for year now but saitek don't care. I'm tired to wait more.....Logitech I'm coming. Saitek you lost another customer.

[pedro]

I have windows 7 64 bit and I had the same problem with mfd. I have found a test program, at C:\Program Files\Saitek\DirectOutput\SDK\Examples\OutputTest, while the actual SaiFlightSim.exe is at C:\Program Files (x86)\Saitek\DirectOutput. If it is working with this, it is working with fsx too.
With this OutputTest.exe I made same "tests". After a normal boot of windows mfd is not working, but after restarting the 'Saitek DirectOutput' it is working always.
I have the feeling that the DirectOutput service is starting before windows can finish loading drivers, so it can not find the proper device to use. I have modified the startup type of 'Saitek DirectOutput' from 'Automatic' to 'Automatic (Delayed start)'. Like this after a boot have to wait a little, in my machine it is two minutes, and mfd is working properly. I hope this will work for others too.

[eaglepilot]

I solved the MFD issue. (At least for myself). I uninstalled FSX and everything associated with Saitek from the "remove programs." Then I reinstalled FSX. After, I hooked my X52 pro into the USB that I will always use for the joystick.

Note: I have found using other ports than where you initially plugged it in can change things like your led settings.

Next, instead of inserting the CD, I downloaded the drivers and software right from the Saitek website.

Note: I suggest saving the drivers somewhere just in case (see later in post)

Everything works just fine. I am able to use the programming software without it crashing, and the MFD works correctly. I had one instance where the display went back to showing nothing but I simply ran the installation of the drivers (this is why you should save it) again, and it's back to working good as new

I am running Vista home premium on a Dell Studio laptop with FSX and Acceleration.

[mannybiker]

Originally Posted by pedro

I have windows 7 64 bit and I had the same problem with mfd. I have found a test program, at C:\Program Files\Saitek\DirectOutput\SDK\Examples\OutputTest, while the actual SaiFlightSim.exe is at C:\Program Files (x86)\Saitek\DirectOutput. If it is working with this, it is working with fsx too.
With this OutputTest.exe I made same "tests". After a normal boot of windows mfd is not working, but after restarting the 'Saitek DirectOutput' it is working always.
I have the feeling that the DirectOutput service is starting before windows can finish loading drivers, so it can not find the proper device to use. I have modified the startup type of 'Saitek DirectOutput' from 'Automatic' to 'Automatic (Delayed start)'. Like this after a boot have to wait a little, in my machine it is two minutes, and mfd is working properly. I hope this will work for others too.

I don't even say that I have the same problem. Anyway this reasoning about the starting of the service makes sense, so I tried to restart the service from the control panel and this works. I've now tried to put Automatic Delayed start, but just restarting the service is already a great advantage than reinstall the driver. Good job pedro!!

[topd0g]

Originally Posted by pedro

...
I have the feeling that the DirectOutput service is starting before windows can finish loading drivers, so it can not find the proper device to use. I have modified the startup type of 'Saitek DirectOutput' from 'Automatic' to 'Automatic (Delayed start)'. Like this after a boot have to wait a little, in my machine it is two minutes, and mfd is working properly. I hope this will work for others too.

I'll give this a go, I had run into the service bug myself and learnt to restart it before it would work (pulled my hair out many a time trying to get my own software to work with the SDK first though ). Incidentally this is on Vista 32-bit for me, and I was going to include the advice of restarting the service with the software I distribute; this might be a better advice to give the users though so thank you.

[Gunterius]

This is really too bad. I am thrilling excited about the X52 pro, but the MFD keeps giving problems which is very very annoying. I just noticed that the drivers are still from 04/04/2008. That means no update or whatever have been made in over 2 years.

Knowing that windows 7 is not out so long, no wondering that it still doesn't work.

What do we have to do to get an update that solves the problem ? I have to reinstall the driver often to get an radio stack sometimes.

please help

[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.

[Gunterius]

It has been working for a few days without a problem now, so it is not always when I startup, but i will put it to delayed start (win 7) to see if it continues to work.

thanks

Gunter

[pulsar21]

have we waited enough?.........or should we wait another 2-3 year?

Ask please the development team (if one exist).

Let us know.