Nintendo pro controller is not detected by steam using bluetooth, and using cable is even worse

[Enmi]

Up and untill 2 days ago I had no issues connecting my nintendo pro controller to my PC via bluetooth, steam detected the controller, and after a bit of calibratrion everything was working smoothly. When I connect via bluetooth now steam simply doesn't detect it, and when I plug it in with a cable, the sticks have no deadzone and it spams every single button by itself. Picture of it spamming buttons https://imgur.com/a/CeS2P1J

[Benson]

Same here. It was working perfectly. Now I can't even run Big Picture mode with it wirelessly.

I looked into the Controller Settings and it looks like there's new support for Pro Controllers and this is what's breaking everything. Worked fine as a generic controller. But now the new native support for it makes it so it can't be generic.

Looks like we're ♥♥♥♥♥♥ until they fix the Nintendo Controller support.

[Forcen]

Post logs and do it in this forum: https://steamcommunity.com/app/353370/discussions/0/1696046342855251976/?ctp=2#c2828702373012601352

[Benson]

Where do I find the log file?

Also, I'm using the Official Nintendo Switch Pro controller. Not this offbrand thing that they're using in that thread.

[Forcen]

In the log folder in the Steam folder. Should be lots of them, check which ones look interesting based on when they were updated, filenames and contents of the log. Controller something is probably it.

Search for threads about that issue and make a new one if you can't find one.
I linked that post because valve mentioned that they made the logs better for issues like this.

[Benson]

My Official Nintendo Switch Pro controller worked until today's patch. Still works perfectly in any other program.

controller.txt log:

[2018-05-17 11:44:52] Local Device Found
type: 057e 2009
path: \\?\hid#{00001124-0000-1000-8000-00805f9b34fb}_vid&0002057e_pid&2009#9&12c08f55&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
serial_number: 0403d6443e41 - 0

[2018-05-17 11:44:52] Manufacturer: Nintendo

[2018-05-17 11:44:52] Product: Wireless Gamepad

[2018-05-17 11:44:52] Release: 0

[2018-05-17 11:44:52] Interface: -1


[2018-05-17 11:44:52] Switch: Bluetooth

[2018-05-17 11:44:52] Switch: failed RequestDeviceInfo

[2018-05-17 11:46:05] No cached sticky mapping in GetActionSetHandle. Native Steam Controller support won't work.

[Forcen]

Originally posted by Benson:

Still works perfectly in any other program.

Other programs? Which ones? I didn't know that controller worked with anything that well except steam.

And I confused you with that link, sorry. Still, make a new thread in that forum and post the whole log or more of it. You can use websites like https://paste.sh/
EDIT: link the thread here.

[Forcen]

In this forum: https://steamcommunity.com/app/353370/discussions/1/

[Benson]

Sure. I'll make another thread. But the issue looks identical to Enmi's

The whole log is the same[pastebin.com]. It just repeates itself over and over.

Pro controller works in pretty much anything that supports generic controllers and button mapping. Like Emulators.

[Forcen]

Yeah, this thread is fine. It's the forum it's located in and some lacking information that's the issue. No need to make a new one about the same issue in the same forum, You should delete that other one if you can
You two seem to have the same issue so one of you should post a bug to the bug forum:
This one: https://steamcommunity.com/app/353370/discussions/1/
And read this guide how to post a bug: https://steamcommunity.com/app/353370/discussions/1/1319962329028051258/

[Benson]

That thread is for the Stream Controller.

[Forcen]

Ah, there's where you are misunderstanding. That's the thing, Steam turns other controllers into Steam controllers basically. Everything Steam does between games and and your controller is covered in that forum.
You can see in that bug report example that they want to know what type of controller the bug is related to. (Steam Controller, DS4, Xbox) That covers the switch controller also.

[Benson]

Well I made the thread .

Strangely enough, Wired Mode works for me. Which is odd because it never did anything before. It's just wireless that remains undetected.

[Forcen]

Great bug report! I don't have any issues myself but I'm on windows 10 and might have another adapter or something. Hope it gets solved.

[Benson]

Enmi I found a workaround for you!

I noticed when connected via USB, my controller also shows the buttons going ♥♥♥♥♥♥♥♥ when steam is running. But it works fine in big picture mode at the exact same time that the Properties window shows the buttons lighting up like some sort of possessed christmas tree.

I tried it in-game and sure enough the buttons were being pressed constantly. After some fidding, I found a way for it to work.

You have to Enable Steam Overlay.

So to recreate what I did:
1. be connected via USB wire
2. go into Big Picture Mode
3. register your controller
4. checkmark required on "Switch Pro Configuration Support"
5. enable Steam Overlay
6. run game through Big Picture Mode library (may not be necessary)

Once I did this, the controller worked in game. The crazy inputs still constantly light up in the Properties window. But in game it works. It seems that the crazy inputs is a result of Steam working as intended?!

Unfortunately, this forces the controller to function as a keyboard and mouse in Windows. If you want to use the controller for non-steam programs, you have to either close Steam entirely or disable Steam's Configuration Support (undo step 4).

Which is incredibly obnoxious.

[Enmi]

Yo thread!
Sorry I haven't been back since I posted this. I see Benson found a solution, I'm happy you got it to work! I found another solution as well, a program that makes the nintendo pro controller register as an xbox controller instead, it is called ProConXinput (can be googled, its a github project, swap the top bar to releases and find the one that fits your OS) and it is pretty easy to set up, there is youtube guides as well.

Hope we help some other people along the way with these issues

regards Enmi