> I assume you disable the GameInput service and rebooted as well? (Without deinstalling GameInput, to test.)
I just tested, and even though GameInput service gets restarted every reboot, just disabling the service, rebooting, and disabling it again did allow me to play.
I may experiment a bit, but I know that just disabling it and running the game didn't work the first few times I tried it.
> I also think there must be more to it.
> Microsoft GameInput is an API that is present on every Windows 10 and 11 systems except for N versions who are fairly rare.
> While Origins overlay interferes with Andromeda on my system, in the short spots I can play the game on Origin the steering works fine as it does on EA app, that don't has the problem with the overly.
> So I assume there is a third component that is interfering here.
I'm not saying your wrong. It is very odd that the issue
1) appeared suddenly after months of playing the game with no issues
2) is apparently specific to this one game of all the games I've tried
As far as I can tell, GameInput itself was updated at the time it stopped working. The last update was installed 5 days earlier. I'm not certain I rebooted the PC in the next 5 days (I usually just sleep the PC) and it seems possible that I rebooted just before the problems occurred. So that's one possibility. The fact that the issue crosses all input devices and is somehow related to the game acquiring exclusive input access (taking over the mouse and hiding the cursor) does seem related to GameInput's functions.
Of all the other app installs that occurred around the time it stopped working, most seem highly unlikely: iTunes, McAfee Security Scan, Microsoft Store, Movie Maker, and Phone Link all say they installed (or updated, I suppose) on that day and Firefox the night before. The second possible culprit would be the Steam game Stray that I installed the day before. I wonder if it's possible if some Steam common file update related to installing Stray could have caused the issue?
One last possible culprit was an attempt I made to install a better driver for my mouse which didn't work out because it turned out not to be for the exact mouse I own (it was for a Cyberpower Elite M-131 Pro mouse, but I only have the Elite M-131). It just told me it wasn't compatible and I uninstalled it. That was at least 3 or 4 days before.
In any of these cases, why would any damage be specific to one game's interactions with input devices, and not affect every game that interacts with GameInput? And I'm not sure, assuming there is some damage to some Windows input related system files, how I'd go about detecting and repairing it. Clearly reinstalling GameInput doesn't fix it, so the damage isn't to GameInput itself.
It's messy, but as long as it's confined to one game only and I have a workaround, I'm not sure it's worth a huge amount of effort to unravel all the details.
