I'm having a few problems with my X52 Pro and I feel all these are somewhat related.
I'm using the X52 pro with a profile I created using the SD6 Beta version of SST (the one that support RShift). For the most part, the stick (axis and buttons) work flawlessly, but from time to time, things really go bad.
First symptom that I notice is that sometimes button get "stuck". For exemple, if I am panning the Shkval in one direction, when I release the hat switch, it keeps panning like it's pressed. If I immediately check the control panel, it shows that the button was indeed released, but the software thinks it's still pressed.
To "unstuck" the command, I usually have to press the button multiple times and/or the key(s) associated with the command on the keyboard multiple times. Eventually, the command is released.
Second symptom I have experience, and this is usually following the first symptom, the keys stop responding. Although the hardware still works correctly (observed with the control panel), the command simply do not work. The only way to resolve this is to remove and reconnect the X52. Sometimes, even that is not enough!
Third symptom I have observed are "flickering" commands. When I press a button, instead of triggering the command once, the command "flickers" - if it's a push button, it's going to go on and off very fast and randomly. This third symptom is usually a precursor of the first two.
Did anyone else experience these problems and if so, how did you work around them? For me, they occur about once every 2 hours of flight, which is a lot!
The last time these problems occurred, I tried to restart the SAI Direct Output service. Even though the process was still running, it was unresponsive. I have the feeling this is somewhat linked with the problems I've had. I will try running the game with the process disabled to see if it's more stable.
I'd also like to note that I have renamed the "lua-direct_output.dll" library from the <rootdir>\DCS\Ka-50\bin\stable\ directory to prevent DSC:BS from using the X52 MFD (which caused the game to CTD a lot).
All this, is for the game configured as a simulator. I've never tried the other game mode. I am running on XP Pro 32 SP3.
Any suggestion would be appreciated. If running without the Direct Output service started helps improving the X52 stability, I'll post my findings here.
:joystick:
