X 52 pro stops

[chardly38]

In the middle of playing my x 52 pro will just stop working. Also i have the trimmer set no the left mouse button on the X52. While trimming in flight the x 52 will stop working for a second. But now its getting worse. Now its stopping and not working until restarting the game. In the control panel it shows the x 52 working great.

[Sense]

if yout using it in combination with rudderpanels, you might want to check if you still have programmed the joystick twist axis. double programming the rudder, gives this failure.

[Isegrim]

Or Center Position Trim mode.

[chardly38]

no rudder rudderpanels yet. What is Center Position Trim mode.

[EtherealN]

Center Position Trim mode is the alternate mode for trim handling, accessed through the options pages. Essentially, with this mode, instead of giving you half a second to center inputs after releasing trim button, the game will wait until everything is centered. This can look as if it just stopped accepting input. If the stick is in any way "spiky" (inexact poitentiometers etcetera) the game may however never get the "center" from all, and would thus never give you control back. In this case the solution is to either add some deadzone in axis tune, or use the standard mode.

[PigOnTheWing]

Hi.

 

I'm having the same problem with my X-52 Pro. During my flights the joy stops working with no advise, and the only way to make it working again is disconnect it from the USB port and reconnect. I have installed the 6.2.2.4 version of the driver and the 7.0.2.7 version of SST, i think the last version, and my OS is Win 7 64 bit.

 

Have you any idea? I have already tried changing the USB port and reinstalling drivers and SST but the issues remains there.:(

[IonicRipper]

Guys, make sure the MFD is not trying to display more then 16 characters. For example, Saitek's SST originally writes Left Mouse Button to designate that button but that's 17 characters (Left Mouse Button.) You have to go in SST and rename the controls so they're not more then 16 characters (Left Mouse for example.) When the MFD tries to display any more then that, it makes the joystick (and SST) crash.

[PigOnTheWing]

Thanks for the suggestion. But in my case the MFD displays wrong words also when, for example, the command name is just "Fire". Anyway I'll check my profiles as soon as possible to ensure they are ok.

 

Thanks again.

[Erforce]

Also, more than 16 characters crashed my system (BSOD) just after plugging the joy in sometimes.

 

For corrupted displays, just switch to mode 2, and back to 1 should be good.

Also beware, the stock PS-2 cable is a true junk (even if it looks brand new).

you should get a better cable if you plan to use it more than often. I've got some serious issues because of it. Fortunately, thanks to internet i was not alone.

[Rammit]

The connection between the actual stick and quadrant can become loose, if this disconnects slightly you will have to re-start the game to get it to register again

[Teapot]

The other thing to watch out for with the X52 Pro is that you don't double up button assignment between your Saitek profile and the default joystick button assignments in DCS (C:\Program Files\Eagle Dynamics\DCS World\Mods\aircrafts\A-10C (*substitute module of choice)\Input\give-it-a-name-or-default-but-make-a-copy-first.lua).

 

I've learned to keep it all very neat and to be scrupulous in the separation between programming native Saitek and key/button assignments from within DCS. If you're uncertain don't mix the two. If you work it out, mixing the two can provide for some interesting possibilities/combinations.

 

Lastly, watch out for slider assignment if you assign the extremes of the slider to two different key presses. I reckon people sometimes forget leaving the slider pushed to one end of the extreme and cause a keyboard buffer overflow.

Edited February 13, 2013 by Teapot

[PigOnTheWing]

Thanks for your replys.

 

I checked the names of the commands and no one is long more than 15 characters, but problem is still there.

I use only the external profiler and I've cleared the whole category for the X-52 in DCS, to avoid any interference. I also checked the connection with the PS2 cable and it seems good.

Now I will try to change the cable an see what happens.

:joystick:

[PigOnTheWing]

After a long search I found a cable and I changed it, but no results:cry:: my joy still lose connection during normal use, and every time I have to disconnect and reconnect it. Some times, with this operation, Win gives me a blue screen.

 

I don't know what else to do. In your opinion, reinstall older drivers can work? Do you know a place where to find them? I found a link to a Saitek FTP site but I can't understand what is the right one.:(

[Erforce]

you may try to go somewhere in your control panel => pads and check if Windows didn't put the joystick in auto-power save mode.

Moreover, can i ask you, the average FPS you are experiencing when this bug occurs?

Before my upgrade, i had some issue with my X52P when passing by a heavy dynamic weather, or more generally at about 14FPS and below.

It can be almost anything, from usb plug to a random driver. :-s

[PigOnTheWing]

Thanks for your answer.

I found an option called USB selective suspend setting in the power options on the Control panel. It was on Enable, now I put it on Disable, Let's see if it works.:joystick:

 

For the fps I had the problem in several conditions, from the heaviest grafic load (15/20 fps on DCS) to the lightest (60 fps on FC 2).

 

If the problem will remain after this test, I will probably change the joy.:cry:

[PigOnTheWing]

No way, my joy dosen't want to work.:no_sad:

 

At this point my only option is to change it. What do you think about the X-65F also from Saitek? I heard different opinions on it and its force sensing system.