|
|
Post by Pascal Mikula on May 8, 2020 11:20:52 GMT
Hi, so the title says it all basically.
Before the France F1 race, I had the issue occur for the first time. My wheel was in the list of connected devices, connected as JOY1, but no inputs were recognized at all. Somehow, through restarting and doing some things I can't remember, it worked just in time for the race.
Now we're coming close to the Indy 500 and I'm having the same problem again! AMS does recognize that a wheel is attached, even what wheel it is, but it doesn't recognize my inputs! (I had a similar problem back when I tried my luck at rFactor 2)
All the other controllers (Gamepad, TH8A Shifter, etc) are recognized and their inputs are recognized, so it might be a hardware problem - BUT every other game and sim I have always recognizes everything from my wheel, so it's gotta be on AMS's end.
So, is there anything I can do to definitely make it recognize my inputs?
Logitech G29 Windows 10 64bit
|
|
|
|
Post by Richard Wilks on May 8, 2020 11:23:54 GMT
Only time that happened with me i had to restart the whole computer, but i guess you already tried that, so i don't know. :\
|
|
|
|
Post by Alberto Ibanez on May 8, 2020 11:23:59 GMT
I assume Windows does recognize your wheel? And for example the old rFactor1 also does?
First thing, back up and remove all controllers ini files in your player setup file and then create a new one and save it. Sometimes AMS is loading a controller profile that is not what you have attached to the computer, so ensure it uses the only existing one and it has your wheel inputs in it.
|
|
|
|
Post by Pascal Mikula on May 8, 2020 12:56:27 GMT
Yep, rFactor does too. Every game except AMS does. Last time I got it to work by recalibrating the wheel through the Windows Controller Control Panel ... but it's still strange as hell.
But also reloading the controller file in AMS ... well actually I haven't tried that. Should try it.
|
|
|
|
Post by Pascal Mikula on May 8, 2020 13:49:02 GMT
So, the only thing I managed to do in order to get it working again is to reset the driver calibration in the control panel... still, incredibly strange but..I guess that works.
|
|
