I've had my new computer for about 3 months now and have been using a Logitech 3d Extreme for WOFF. It's an OK stick but I have used it mainly because it was quick and easy to set up with the WOFF controller program.
Previously I used the Saitek X-52 Pro but I just have not had a chance to get it all set up again - mainly programming all the thousand buttons and features.
I really like the X-52 though so I finally broke it out of war reserve and am going to get it all programmed this weekend. Just d/l'ed the 64-bit drivers.

My question for users of this stick:
Do think think it is easier (or better) to use the 52's programming software to configure it or the controller assignment feature built into the WOFF Workshop? I have used both (Saitek software for WOFF 1.26 on my old system and the Workshop controller configure program for WOFF 2.0 for the Logitech ) and both seem to work well however I was wondering if the WOFF configure system can be used to program all the buttons and features found on the 52 if I decide to use it.

I have the X52, I just programmed the keys I needed from the the WOFF key guide. I did not use the Saitek program.

Beard

Alrighty thank you.
I just started using the WOFF program fairly recently to configure and have been pretty impressed by it.

I have it, too, and though I don't get to fly much, I have used a mix of WOFF key assignments and the Saitek software. In particular I used the Saitek software to set the recenter key (F12, I think) for TrackIR to the little thumb button on the right side of the joystick. I'm wondering about maybe setting precision (TrackIR) and even gunsite view (WOFF) to one of these, but you'll probably get to it before I do.

I miss force feedback, though.

Ah. Both programs can be used for programming at the same time eh?
Guess I was fixated on one or the other. If you can use both at the same time no worries. Thanks

Do either of you gentlemen have Win 7 Pro 64-bit and did you have issues trying to install the driver?
Off the top it is not going smoothly and I am currently on my third try.

EDIT: Got the drivers installed - I guess - but my system acts like it doesn't like something. Maybe the software, maybe the stick. Here we go for Internet searches. I am supposed to be flying not goofing with hardware!

I hate that. I'm using Win64 Pro., Can't say tha I've had any problems with drivers & WOFF. I had to update TrackIR like everybody when WOFF 2.0 came out.

My idiot system gets screwed up on the monitor's EDID info, so the monitor boots low-res with the old Vista green bar boot screen. And for some reason, CFS3-ETO lost sound in the cockpit. So you have my sympathies.

FWIW the Internet is full of Win 7 folks having issues with their driver software. One post describes multiple issues that I have been having exactly. Lot of solutions too. Just getting ready to slog thru some.
Figures I like my Saitek much better than the Logitech or I wouldn't be putting up with all this.

Well, don't get me wrong - I like mine, too, and I even sprang for the rudder pedals. But force feedback would make them perfect, IMHO. The rough part of simulators is that tactile feedback is tough to even pretend to mimic.

I just read your system stats. Your system is almost the same as mine.
You didn't have any problems installing the software? Right now it's partially installed, I think, but in looking at the WOFF configure program there looks to be no way to use it. Button #1 thru #50+. What in the heck do I do with that. Now going thru one of the 10 minute shutdowns before I can try suggestion 2. Disable xHCL via the computers set up screen. What a nightmare. Nice. Just now instead of shut down I got a BSOD.

Yowsir, I wish I could help! I'm at work now, but no, I sure didn't. It's been over three years now, and WOFF 2.0 went right in. I did have a little trouble figuring out how to assign that slider on the throttle to the mixture axis (via WOFF configuration), and yeah, figuring out which one is button "X" is a problem - I just poked around looking for a diagram and can't find one.

I'll try to get back with you later, but I have to work on my chain saws tonight, so it's kinda iffy. Sorry, good luck!

Got this off the internet:

"Saitek drivers are bad. Really bad. I had more trouble installing my x52 Pro than I have had installing any kind of hardware since about 1995.
One of the problems with the x52 drivers (or perhaps the hardware itself, I don't know) is that it doesn't play nicely with xHCI and this information is not well documented. This means that if you have a modern system with USB2 and/or USB3 your motherboard probably supports xHCI and therefore will might cause all sorts of problems when installing an x52. Your symptoms might be things like:

Windows crashing
x52 driver installer locking up
your x52 LED indicators not lighting up properly
Windows not shutting down
Windows not booting up
Disrupted internet access (yes, really)

If you experience these problems 1) completely uninstall Saitek software; 2) go into BIOS and disable xHCI; 3) reboot windows and install the latest Saitek drivers.

Unless you run into any of the other typical problems seen by x52 users, this might solve your problems and save you some of the pains I experienced.

(For the record I run a Windows 7 64 bit machine, I'm not sure how these xHCI problems carry over to other systems or hardware configs)"

How damn stupid is this? I am not trying to get a manned mission to Mars here but play a darn game. I have literally had every single one of these problems (and wasted the bulk of a day) trying to get this stick to work. If I didn't pay $130.00 for it (and the fact it worked great with WOFF and Win XP) I would throw it out the window right now. I am committed now. Or perhaps I should be committed - to the mental ward.
Went to my BIOS and didn't see xHCI - whatever it is.
Well back to trying to find a solution and thank you for listening to my rant.

DukeIronHand,

I understand your pain, I was looking at an x52 for my first HOTAS stick, but on doing research on the internet, I decided against it. I have now gone for the cheaper T-Flight HOTAS X.

I agree a joystick/flight controller should not cause a PC to become inoperable.

The main solution that I saw on the net was to ensure that the X52 was plugged into a USB2 socket. It kind of makes a mockery of USB3 being "backwards compatible".

I hope you find a satisfactory solution to the problems you have encountered.

Got everything all deleted even from the registry.
Got some older drivers from a Saitek FTP site.
Since everything is a big damn deal (as listed above literally!) I don't know if I m going to try the old drivers first or try to disable (somehow) USB 3.0 support on my system which many indicate is the (a) issue.
Might try the disable 3.0 thing first. Sounds kind of worthless anyway.
Guess having a brand new fancy a$$ system with all the bells and whistles isn't always a good thing!

EDIT: Oops! Disabling or uninstalling the obvious USB 3.0 stuff was not the way to go. Nothing worked. Thank goodness for Safe Mode and System Restore. Guess we will give the older drivers a try.

Well I have the problem figured out I just don't have a fix for that problem.

The problem is a file called "DirectOutput.msi"
It is part of the driver package and "locks up" in a permanent state of actively trying to install causing all of the issues noted previously. I will try a Google search on this .msi for an answer otherwise I might be licked!

I have a (older) Win 7 laptop. Is it possible to install the driver here and copy them to my WOFF machine?

Well looks like I am done for now. According to the "always correct" Google searches:
A hell of a lot of people are having this issue but a lot are are not. It all depends on your system.
It is a Win 7 64-bit issue...kinda. Looks Win 8's have it also.
It is not specifically related to the OS though - its just these OS's are on newer machines. And newer machines are the issue depending on your USB 3.0 Controller drivers/hardware set-up. Something about the Intel 3.0 system (which I have) conflicts with the Saitek software apparently.

1) I have no option to disable 3.0 support in my BIOS.
2) I tried to uninstall anything USB 3.0 in the Win 7 Device manager (Intel(R) USB 3.0 eXtensible Host Controller and Intel(R) USB 3.0 Root Hub) but my system became unresponsive (booted up but mouse and keyboard did not work) and I had to use System Restore to get it working again. I suspect USB 3.0 is integral to my new machine perhaps for the SSD drive that the system uses as a cache to improve performance? Or maybe I should try to uninstall one or the other but not both? Dunno if I want to play with System Restore again unless I have a definite answer. Any experts here?
3) Sent an email to Saitek customer support but according to others I shouldn't expect much from them. The problem has been around for years and they have done nothing about it.

If my 12 month old joystick is worthless this will be the last Saitek product I buy. Notice the price has has almost doubled since I bought it - or I got a hell of a deal.
So after about 8 hours (mainly with a locked up computer and forcing reboots and restores) I may try just plugging it in and see if the native Windows drivers give me adequate functionality or its back to the Logitech 3d Extreme - the "cheap" stick! Haha...

EDIT: Forgot to mention that, for some, buying a PCI 2.0 USB card has worked - if any of our dozens of lurkers is having the same issue. I may end up going that route after much timely research (again) to ensure the ports in the card will give me TRUE 2.0 function. With my MB, and the rest of my system, that may not be a sure thing.

Not to keep dragging this thread up but sorry Rugbyfan - I was so caught up in my longwinded tale of woe I forgot to get back to you.
Yes my system has six USB 3.0 ports and four USB 2.0 ports. Apparently the presence of 3.0 in my system does not make my 2.0 ports TRUE 2.0 ports. A couple of people had luck plugging and unplugging from various ports, and I tried that, but in a haphazard and not methodical fashion. The problem is the .msi file that causes the system lock-up. It's a hell of a PITA when it does that and discourages quick experiments to find a fix.

DukeIonHand,

Ouch, that must hurts, hopeuflly they haver fixerd the problem with ther X55, but I understand your relectance to buy another Saitek stick. Unfortunately that has destroyed any idea I may of had regardng getting an X52 as a HOTAS Stick in the futur, and like yo you said I will probaly look outside of Saitek for a HOTAS, assuming I can wok wih the T-Stick HOTAS X.

Tried the X52 again without any Saitek drivers present (I thought) and my system locked up again. After 45 minutes of getting my system back in order I d/'ed two registry cleaners and they found more Saitek registry crap not mentioned in previous articles. I had enough for one weekend though and shelved it and am back with my Logitech .
I might try one more time on some rainy weekend without the drivers (and ALL registry entries hopefully!) and if that doesn't work it will suffer the same fate as many pilots - I will smash and burn the damn thing.

I'll just add a stick recommendation here for all who like precise shooting:

THRUSTMASTER T.16000

The stick has extremely good precision, even on the throttle slider, which may be
a bit short; but it works with the slightes movements.
16 buttons are neither too few nor too much to handle and program.
And if you have no pedals - it's a twist stick.
Read more in the weblink above.