Controller issue

[Zag]

I've recently bought a Speedlink Competition Pro Extra joystick (for those who don't know, a re-creation of the old micro-switched joystick of the 1990s) which plugs into the PC (Windows 10, 64-bit) via a modern USB connection. When connected the computer recognises it as "Competition Pro Extra", sets it up okay and it works fine with games etc.

The only problem is when I start Steam. As soon as I do this I get the "disconnect" sound and the "Competition Pro Extra" is replaced as controller with "Game Controller For Android" which it remains even if Steam is closed. The only way to get the Competition Pro recognition back is to unplug and re-connect. Whilst in this "Game Controller for Android" mode it doesn't work properly and the buttons are all wrong.

I've tried different USB ports but they make no difference - the problem is clearly with Steam which doesn't seem to like the controller as it is and changes it to something else. I've no real interest in using this controller with Steam games but it's screwing up my using it with anything else.

Ideas?

[Bad 💀 Motha]

Buy something that is known to work well with Win10 and Steam.

Controllers from Logitech, Razer, Sony (DS4), Microsoft (360/XBO), Nintendo (Switch) for example.

The cheaper XBO controllers from PDP and PowerA also work fine.

[Zag]

Thanks for the responses but just to clarify: I don't need it to work with Steam, I've a Xbox controller which does fine for all that and which Steam, obviously, recognises. What I need it to do is stop "unplugging" it as what it is - a Comp Pro Extra - and then change it to this "Android Controller" nonsense whenever Steam starts. It stops me using it with the other (non Steam) games I bought it for.

[Bad 💀 Motha]

Then I would suggest, since that is never going to happen unless Valve fixes it, is to reconfigure that controller for the game in question.

Also, uncheck the ps4 and Xbox boxes in Steam bpm and enable the Generic box only. Then restart steam client

[Zag]

Thanks, will see what I can do.

Only other solution I can think of is: if I unplug and then reconnect the joystick (once Steam is closed) it recognises it properly again. It's hardly ideal, but is there any way to "force" this without physically unplugging and re-connecting the stick?

[Bad 💀 Motha]

By right clicking the device in device manager, uninstall, refresh scan in device manager to redetect the hardware again

[Zag]

This looked like it was fixed, thanks to a Steam update but since the latest Win update it seems to have started happening again... (Y)