X55

[Soulstain]

Hello all,
I posted this question on the steam forums but I thought I would get more response here. SeeJay tried to help me out but to no avail. Everything was great until I did a recent upgrade of my system. Since this time I can no longer get my X55 stick to be recognized in EM. The throttle is, but the stick isn't. Yes, I know you have to cycle through from device 1-3 because the throttle and stick are mapped separately. It doesn't matter if I cycle 1-3 there is no axis recognized on the stick. I have updated to the Saitek beta Win 10 drivers. Help, I miss EM and don't want to play with a controller..... Both controllers are being recognized in all my other games.

Windows 10 64bit clean install from licensed full version, not upgrade.
MSI GTX 980 ti
ASUS Maximus VIII Hero
Skylake I7 6700k
16 gig DDR4 ram
Two WD Black 1 TB's
Saitek X55
TrackIr5

[Edited on 11-6-2015 by Soulstain]

[Vice]

Not really sure what could be wrong, other than drivers that still need to be updated/corrected for Windows 10. The game is merely reactionary to what Windows/DInput/DirectX sends to it. So if Windows doesn't think a device is available on a particular ID channel, neither will the game. Why it might work elsewhere could be dependent on what type of input system a particular program/game uses.

What else shows up on the three channels the game does detect, other than the throttle? If you have other USB devices plugged in, have you tried unplugging them to test for changes in behavior?

I earlier posted instructions that Madcatz provided to properly set up and (re)install drivers for their device when it has detection problems in games here (scroll to the bottom): http://www.starwraith.com/forum/viewtopic.php?t=11713

Also, install the joystick config program in the game's save data folder and see what it provides in raw data feedback from your system (particularly the list of detected devices): http://www.starwraith.com/evochronmerce ... Config.zip

Then please post the results of what that program displays.

Edit: Although I don't have a X55 to test with, I do have a X52. So I plugged that into one of my Windows 10 machines and let Windows install the preferred driver for it. It worked fine that way. You might also want to test removing the beta driver and try the Windows driver install route to see if the behavior changes at all. You'd likely need to clear out the old driver and its INF setup to avoid it being installed again by default for such a test.

[Edited on 11-9-2015 by Vice]