Switch Pro Controller works perfectly in Steam Big Picture, but not anywhere else.

[zweistein]

I have been trying to play games with my switch pro controller that are not on steam, but for some reason, it feels like hundreds of buttons are pressed every second. If I launch Steam Big Picture mode though, my controller works fine. I have it connected via an USB-C Wire because my Computer does not support Bluetooth and I could not be bothered buying a bluetooth adapter.
This is what it looks like
https://gfycat.com/dizzycoolhake

[tintingaroo]

This is how I understand things:

joy.cpl is reading the controller via DirectInput and from what I read somewhere, the wired Switch Pro Controller output is, at its base, DirectInput, but has additional Nintendo stuff on top meaning its not compliant with DirectInput.

I was going to write I'm not aware of any games that natively support the wired Switch Pro Controller output, but thinking about it, games that use SDL to support controllers should be OK (its what Steam uses to support controllers).

So apart from games using SDL, I'm not aware of any having native support for the wired Pro Controller output. As you are experiencing, you need to run it via an input mapper (Steam in your case). It supports the wired Pro Controller protocol and can translate it into Xinput, the protocol most of the games will be using.
Over Bluetooth things are different, the BT Pro Controller output is compliant with DirectInput and so is more supported.

What you can do is add the non-Steam games to Steam and you'll get the same support as the Steam games do. Alternatively, check out other input mappers such as DS4Windows. Sometimes there can be issues with the way Steam interacts with a game to provide it's emulation (it's via the overlay) but the other input mappers do things a different way, they present a virtual Xbox controller, as if it were a device connected to your system.

[zweistein]

Publicado originalmente por tintingaroo:

This is how I understand things:

joy.cpl is reading the controller via DirectInput and from what I read somewhere, the wired Switch Pro Controller output is, at its base, DirectInput, but has additional Nintendo stuff on top meaning its not compliant with DirectInput.

I was going to write I'm not aware of any games that natively support the wired Switch Pro Controller output, but thinking about it, games that use SDL to support controllers should be OK (its what Steam uses to support controllers).

So apart from games using SDL, I'm not aware of any having native support for the wired Pro Controller output. As you are experiencing, you need to run it via an input mapper (Steam in your case). It supports the wired Pro Controller protocol and can translate it into Xinput, the protocol most of the games will be using.
Over Bluetooth things are different, the BT Pro Controller output is compliant with DirectInput and so is more supported.

What you can do is add the non-Steam games to Steam and you'll get the same support as the Steam games do. Alternatively, check out other input mappers such as DS4Windows. Sometimes there can be issues with the way Steam interacts with a game to provide it's emulation (it's via the overlay) but the other input mappers do things a different way, they present a virtual Xbox controller, as if it were a device connected to your system.

Thank you very much. Adding non steam gasmesto steam is what I did for most of my games, but FIFA games are not working because the fifa.exe file starts a launcher and not the game. I will try to see what happens

[tintingaroo]

Yeah, launchers can prove troublesome for the Steam way, it's one of the areas where things are smoother with other input mappers. For Steam's support the aim is to get the overlay to work with the game/launcher.

Is the launcher Origin? If so you could try this:
1. disable Origin's overlay (Origin > Application Settings > Origin In-game > turn off 'Enable Origin In-Game'). Quit Origin.
2. add Origin as a non-Steam game
3. Start Origin from Steam
4. Start FIFA from Origin

That works for me and Star Wars: Jedi Fallen Order (but I can also add the game's exe to Steam and things work as well).

Perhaps it'll be a similar thing for the EA App if that's the launcher you get.

[zweistein]

Publicado originalmente por tintingaroo:

Yeah, launchers can prove troublesome for the Steam way, it's one of the areas where things are smoother with other input mappers. For Steam's support the aim is to get the overlay to work with the game/launcher.

Is the launcher Origin? If so you could try this:
1. disable Origin's overlay (Origin > Application Settings > Origin In-game > turn off 'Enable Origin In-Game'). Quit Origin.
2. add Origin as a non-Steam game
3. Start Origin from Steam
4. Start FIFA from Origin

That works for me and Star Wars: Jedi Fallen Order (but I can also add the game's exe to Steam and things work as well).

Perhaps it'll be a similar thing for the EA App if that's the launcher you get.

Thank you. Theres an EA App Launcher and when you press FIFA 21 it starts a launcher which looks like this. https://prnt.sc/n0Dk6zocOaku . If this wasnt a thing, I think launching the game from steam would work. I appreciate your help and I will look for solutions

[ZesplaroLAMM]

GRACIAS TINTINGARO, para los que tengan el problema de la que solo los juegos fuera de steam no reconoce su mando el programa DS4Windows solo con estar en inalambrico solucionara los problemas ejecutas e inicias y si quieren mas detalles esta en el comentario de la persona que mencione al inicio gracias gracias gracias