#wootility stop working on steam (rl)
1 messages · Page 1 of 1 (latest)
is the wooting in controller mode and the profile with the controller enabled?
also having this issue, have to turn off steam input for my wooting (gamepad config) to be able to used
but this is only a work around if the game has native controller support, some don't or it's wonky
was detected before so not sure what has changed with steam
did steam change how they interact with xbox 360 controllers?
i was thinking possibly that or a driver issue but i have no idea how to be sure
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
It sounds like Steam doesn't see it as a gamepad - does Windows? You can check by hitting the windows button, typing "run", then entering "joy.cpl". If Windows detects it, it should read like in this picture:
windows does for some reason
and standard controller setting is detected by steam as mentioned above
but xinput isn't
kinda bewildering as it's worked fine before
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?
I've tried both no dice
might reformat as a last resort cause i def could have messed with something
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.