#wootility stop working on steam (rl)

1 messages · Page 1 of 1 (latest)

fervent zodiac
#

no controllers are detected on steam

atomic moat
#

is the wooting in controller mode and the profile with the controller enabled?

near nexus
near nexus
#

for some reason classic controller is detected by steam?

atomic moat
#

did steam change how they interact with xbox 360 controllers?

near nexus
#

i was thinking possibly that or a driver issue but i have no idea how to be sure

atomic moat
#

driver issue would be off that it happens twice but also easy to check since you just force remove the device from device manager as the driver is the windows default driver for xbox 360 controllers

glacial ember
near nexus
#

and standard controller setting is detected by steam as mentioned above

#

but xinput isn't

#

kinda bewildering as it's worked fine before

glacial ember
#

I haven't noticed any substantial change in the way Steam Input hooks any time recently, so maybe it could be your controller configuration cache got corrupted?

#

@near nexus Are you using the Beta steam client or normal steam client?

near nexus
#

might reformat as a last resort cause i def could have messed with something

glacial ember
#

Have you tried closing steam completely in task manager and deleting your config.vdf file in C:\Program Files (x86)\Steam\config?

#

That should clear controller configuration cache.

#

My guess is that your device mappings got corrupted overtime (usually from connecting and disconnecting frequently) and Steam is mislabeling the device reading.