Qanba arcade stick no longer detectable in any game, but works in Big Picture

[freefall]

Hi guys, I have a recurring problem where my arcade stick is not recognizable in any game, but it's usable in Big Picture Mode or when configuring the controller setup.

The problem really started when Steam changed its implementation so you had to register a controller into the Steam interface and configure it from there. Before this when the controller was tied to DirectInput, I had no such problems. Even when I got the stick working after a lot of trial and error previously, it would then come back every few months.

Previously I could solve this by unplugging my stick plugging it back in and reconfiguring it. Bbut now that my stick is working fine in Big Picture or when configuring my controller, I really don't know what to do anymore, and I really need help.

Thank you in advance

[shoopy]

I don't know if it'll help but I've never had to register anything. I have a Qanba Carbon and I just let Steam auto detect it, it recognizes it as a 360 controller. I think I did once have an issue a long time ago that I solved by not selecting any controller support at all but I can't remember exactly.

Basically I don't set up anything, stuff just works.

[freefall]

Originally posted by ardiel:

I don't know if it'll help but I've never had to register anything. I have a Qanba Carbon and I just let Steam auto detect it, it recognizes it as a 360 controller. I think I did once have an issue a long time ago that I solved by not selecting any controller support at all but I can't remember exactly.

Basically I don't set up anything, stuff just works.

I use a Carbon as well. I managed to rectify the problem this time with some help by hiding the controller, and letting it auto detect itself again. But this is not the first time it's happened, and I suspect it won't be the last. And every time it happens, it just wipes out my control bindings across all the games, so I'd need to reconfigure them again.

[shoopy]

Originally posted by freefall:

Originally posted by ardiel:

I don't know if it'll help but I've never had to register anything. I have a Qanba Carbon and I just let Steam auto detect it, it recognizes it as a 360 controller. I think I did once have an issue a long time ago that I solved by not selecting any controller support at all but I can't remember exactly.

Basically I don't set up anything, stuff just works.

I use a Carbon as well. I managed to rectify the problem this time with some help by hiding the controller, and letting it auto detect itself again. But this is not the first time it's happened, and I suspect it won't be the last. And every time it happens, it just wipes out my control bindings across all the games, so I'd need to reconfigure them again.

I let games handle their own bindings without using the Steam setup at all. Those should be saved with each game's individual settings data.