bfeld

VRS really sucks ;)

Hello, unfortunately, it's not the cable. So I will search the Saitek forums, re-install Windows (in case it's a driver issue) or send it back (might be a loose connection somewhere). Thanks, bfeld

Yes, first I just re-installed (with previous deinstallation) everything. Then I tried a backup point. Then I manually cleaned everything I could find off the registry. And so on, but with windows, you never know if there's anything left. Perhaps I should reinstall windows... but first, I hope for a broken cable ;) Thanks, bfeld

Hi Boulund, I already checked the pins and swapped the cable around as suggested by Shadow.D.. However, I didn't "really" check it with a multimeter yet. Thanks, I will try that tonight. Bye, bfeld

Hi bettymoo, hi all, anything new to this? Did you get a new controller, does it work? I still fight the same problem and I think it's something weird with the drivers. It seems as if a new driver is instanciated when the X52 is plugged to the USB port, causing interferences and thus lags. I plugged it to another port and it worked until it was reset when starting a new mission. I also used an externally powered USB hub. The problem was similar, but this time, using the new USB port, the LEDs on the throttle wouldn't work. This was reproducible. I can't think of a hardware problem, because it's somewhat reproducible (axes always work, toggle buttons and throttle, too. LEDs and the other joystick keys do not always, sometimes depending on USB port) but then there are times where it just works. Any help is appreciated, currently I'm trying to register for the saitek forums like bettymoo did. Cheers, bfeld

Hey bettymoo, unfortunately I don't know what to do, but fortunately for you there's at least another one -- me -- who got the same problem. I observed, that it is mostly the buttons on the stick, not on the thrust control. I played around a lot with different drivers, but I soon got the feeling, that it became worse. I manually cleaned the whole registry, it became better, but not perfect. Sometimes it works from the beginning and then, after a couple of minutes, the effect appears. Sometimes it was much more than 5 or 10 seconds. I guess, it's something with the drivers. Since we got the same problem, the hardware should be okay. So long, Torsten edit: I can confirm, that the axes are always working. If I remember correctly (I'm on holiday, so no way to check this), the toggle buttons at the bottom of the stick as well.

... you are permanently looking at the clock in your car to ensure you are in fast forward mode when automatically starting the engines :)