Games that don't like newer controllers.

[spharin]

Is there any way through steam/big picture that I could configure to make my Switch Pro controller work on a game that only likes to use xbox controllers without using 3rd party software?
I'm unsure if generic gamepads work for this game and I'm not sure if I have a way to test that either. I have an offbrand xbox controller that I don't enjoy using for PC so I'd like to use my Switch pro controller but it doesn't seem to work for a specific game.
The devs for said game have stated that they have no plans on fixing the game up to let more controllers work for it.

[tintingaroo]

You can enable Switch Pro Configuration Support and Steam will provide the emulation for all games in your Library, or you could enable things on a per-game basis.

Whole Library
Steam > Settings > Controller > General Controller Settings > enable Switch Pro Configuration Support

Per-game
Right-click the game in the Steam Library > Properties > Controller > select Enable Steam Input

[spharin]

this doesn't work, my controller still doesn't function in the game. it seems like the game doesn't like steam's controllers either.
i really don't want to use my cruddy off-brand xbox controller.

[crunchyfrog]

spharin님이 먼저 게시:

this doesn't work, my controller still doesn't function in the game. it seems like the game doesn't like steam's controllers either.
i really don't want to use my cruddy off-brand xbox controller.

Sadly you may be better off doing just that.

PS controllers and Switch controllers often have issues on PC because they're not truly supported as they have proprietary tech in there. You regularly see posts like yours on here, and it seems to randomly happen where you can have them working fine then one day not.

Get an Xbox One conotrller and they generally just work regardless as they're built for Windows.

[tintingaroo]

spharin님이 먼저 게시:

this doesn't work, my controller still doesn't function in the game. it seems like the game doesn't like steam's controllers either.
i really don't want to use my cruddy off-brand xbox controller.

What game is it? You have it on Steam? Also, which OS? I'm presuming Windows but would like to be sure.

[tintingaroo]

crunchyfrog님이 먼저 게시:

spharin님이 먼저 게시:

this doesn't work, my controller still doesn't function in the game. it seems like the game doesn't like steam's controllers either.
i really don't want to use my cruddy off-brand xbox controller.

Sadly you may be better off doing just that.

PS controllers and Switch controllers often have issues on PC because they're not truly supported as they have proprietary tech in there. You regularly see posts like yours on here, and it seems to randomly happen where you can have them working fine then one day not.

Get an Xbox One conotrller and they generally just work regardless as they're built for Windows.

Both those controllers are truly supported - that is what Valve & others have covered. What those controllers aren't is Xinput devices, so not natively supported in games by devs who only implement Xinput, or only target the Xbox controller. In those situations the controllers use the support of Steam/other input mappers.

Taking things from a Windows perspective:
Sony DS4/5 controllers and Nintendo Switch Pro controllers are truly supported between Windows and Steam/other input mapper. The DS4/5 over USB is natively supported by Windows. Games that use DirectInput and not just Xinput will natively work with them if the developers don't solely target the Xbox side. Over BT they can be operating in their PlayStation mode or in 'PC Friendly' mode. If they are operating in their PS mode, then Steam supports it (or other DS input mappers), if in 'PC friendly' mode then they are natively supported by Windows - things that utilise DirectInput will be fine with them.

The Switch Pro controller over USB is not natively supported by Windows, but is supported by Steam (or other NSP input mappers). Over BT the controller will natively work with Windows, and applications that make use of DirectInput will work natively if the devs don't solely target Xbox/Xinput. Over BT they can alternatively be operating in Switch Pro mode, this is not supported by Windows but it is supported by Steam.

Windows natively supports them in some situations, Steam/other input mappers support them in all.

Things can seem random to those who don't understand and don't try to understand how things are operating - Steam, the controllers, when they operate in simple/full modes, the games, other softwares, configurations/settings etc.

[crunchyfrog]

tintingaroo님이 먼저 게시:

crunchyfrog님이 먼저 게시:

Sadly you may be better off doing just that.

PS controllers and Switch controllers often have issues on PC because they're not truly supported as they have proprietary tech in there. You regularly see posts like yours on here, and it seems to randomly happen where you can have them working fine then one day not.

Get an Xbox One conotrller and they generally just work regardless as they're built for Windows.

Both those controllers are truly supported - that is what Valve & others have covered. What those controllers aren't is Xinput devices, so not natively supported in games by devs who only implement Xinput, or only target the Xbox controller. In those situations the controllers use the support of Steam/other input mappers.

Taking things from a Windows perspective:
Sony DS4/5 controllers and Nintendo Switch Pro controllers are truly supported between Windows and Steam/other input mapper. The DS4/5 over USB is natively supported by Windows. Games that use DirectInput and not just Xinput will natively work with them if the developers don't solely target the Xbox side. Over BT they can be operating in their PlayStation mode or in 'PC Friendly' mode. If they are operating in their PS mode, then Steam supports it (or other DS input mappers), if in 'PC friendly' mode then they are natively supported by Windows - things that utilise DirectInput will be fine with them.

The Switch Pro controller over USB is not natively supported by Windows, but is supported by Steam (or other NSP input mappers). Over BT the controller will natively work with Windows, and applications that make use of DirectInput will work natively if the devs don't solely target Xbox/Xinput. Over BT they can alternatively be operating in Switch Pro mode, this is not supported by Windows but it is supported by Steam.

Windows natively supports them in some situations, Steam/other input mappers support them in all.

Things can seem random to those who don't understand and don't try to understand how things are operating - Steam, the controllers, when they operate in simple/full modes, the games, other softwares, configurations/settings etc.

Yes that's what I mean. the GAMES are those that use them. Steam is just the UI. So they are not supported by the games. The bit you need to use them for.


None of this changes the fact of evidence on here.

We get loads of posts - which you can freely check - of people with Switch controllers, some third party controllers, PS controllers that all of a sudden work errativally, or stop working and this is why. Because they're not supported weirdness happens.

So all I can do is advise based on this evidence - and that is to use an Xbox One controller for the best experience as even if you fix the issue today there's no guaranteeing tomorrow it won't happen again.


It depends on what you want out of it.

[Kargor]

crunchyfrog님이 먼저 게시:

PS controllers and Switch controllers often have issues on PC because they're not truly supported as they have proprietary tech in there. You regularly see posts like yours on here, and it seems to randomly happen where you can have them working fine then one day not.

The core problem is a quality issue, though. With Steam.

At the end of the day, we're talking software. If you want to provide an emulation that looks like an authentic XBox controller, then be serious about it, and make it look like an authentic XBox controller -- not just something that's good enough for the 3 games you've tested it on.

Likewise, if you had to reverse-engineer how the controller you're trying to support sends its stuff over the USB, and it doesn't always work reliably, put some effort into it to find out where you went wrong in your initial analysis.

If you can't do these things, be honest about it.

We all know that Valve in general is "lazy"; they probably added both of these things at some point, called it a day, and never touched it again to address issues.

From my perspective, Steams controller support has yet another issue -- I actually have an XBox controller, but controller support feels obscure, undocumented, and more likely to get in the way than to help with anything. Thus, I'm primarily trying to shut it up... but then again, I've never even read anything factual about what this obscure "enable Steam input" actually does.

I know I have one game that actually needs it for the controller to work... which is not communicated or even enforced by the game, you have to learn it from the forums -- might not be Valve's fault to be honest, but it plays into the "Steam controller support obscurity mist"; at the end of the day I want games that work, and I don't really care who's at fault if it doesn't. I just know that 99% of the games work just fine (concerning controller support), and then there's one that requires me to play with Steam's obscure settings... and it doesn't even tell me.

[tintingaroo]

crunchyfrog님이 먼저 게시:

tintingaroo님이 먼저 게시:

Both those controllers are truly supported - that is what Valve & others have covered. What those controllers aren't is Xinput devices, so not natively supported in games by devs who only implement Xinput, or only target the Xbox controller. In those situations the controllers use the support of Steam/other input mappers.

Taking things from a Windows perspective:
Sony DS4/5 controllers and Nintendo Switch Pro controllers are truly supported between Windows and Steam/other input mapper. The DS4/5 over USB is natively supported by Windows. Games that use DirectInput and not just Xinput will natively work with them if the developers don't solely target the Xbox side. Over BT they can be operating in their PlayStation mode or in 'PC Friendly' mode. If they are operating in their PS mode, then Steam supports it (or other DS input mappers), if in 'PC friendly' mode then they are natively supported by Windows - things that utilise DirectInput will be fine with them.

The Switch Pro controller over USB is not natively supported by Windows, but is supported by Steam (or other NSP input mappers). Over BT the controller will natively work with Windows, and applications that make use of DirectInput will work natively if the devs don't solely target Xbox/Xinput. Over BT they can alternatively be operating in Switch Pro mode, this is not supported by Windows but it is supported by Steam.

Windows natively supports them in some situations, Steam/other input mappers support them in all.

Things can seem random to those who don't understand and don't try to understand how things are operating - Steam, the controllers, when they operate in simple/full modes, the games, other softwares, configurations/settings etc.

Yes that's what I mean. the GAMES are those that use them. Steam is just the UI. So they are not supported by the games. The bit you need to use them for.


None of this changes the fact of evidence on here.

We get loads of posts - which you can freely check - of people with Switch controllers, some third party controllers, PS controllers that all of a sudden work errativally, or stop working and this is why. Because they're not supported weirdness happens.

So all I can do is advise based on this evidence - and that is to use an Xbox One controller for the best experience as even if you fix the issue today there's no guaranteeing tomorrow it won't happen again.


It depends on what you want out of it.

Steam is not just an UI - are you aware of Steam Input? https://partner.steamgames.com/doc/features/steam_controller/concepts
Steam handles and understands the input from the controllers. Steam translates the controller input and sends it to the games. The games, if they are looking for Xinput, receive Xinput from Steam. That is the support Steam (and other input mappers) provide so the controllers work with the games.

When you see a post by a user saying they have an issue doing something and they are using a Switch Pro controller or PS controller, do you discern where the issue is or do you just conclude it's because of the controller? e.g. Someone has trouble connecting their PS controller via BT to their PC - is that a BT issue (BT adapter not capable, or the drivers they have installed for it, interference etc), the process they are using to connect, a problem stemming from their OS/other software, low battery in their controller, stuff like that, or is it 'because they are using a PS controller'? Do you ask these sort of questions? Do you trouble-shoot? Or does it just get added to the post count of 'there's another issue caused by the PS/Switch controller'?

As I wrote before:
Things can seem random to those who don't understand and don't try to understand how things are operating - Steam, the controllers, when they operate in simple/full modes, the games, other softwares, configurations/settings etc.

[crunchyfrog]

Kargor님이 먼저 게시:

crunchyfrog님이 먼저 게시:

PS controllers and Switch controllers often have issues on PC because they're not truly supported as they have proprietary tech in there. You regularly see posts like yours on here, and it seems to randomly happen where you can have them working fine then one day not.

The core problem is a quality issue, though. With Steam.

At the end of the day, we're talking software. If you want to provide an emulation that looks like an authentic XBox controller, then be serious about it, and make it look like an authentic XBox controller -- not just something that's good enough for the 3 games you've tested it on.

Likewise, if you had to reverse-engineer how the controller you're trying to support sends its stuff over the USB, and it doesn't always work reliably, put some effort into it to find out where you went wrong in your initial analysis.

If you can't do these things, be honest about it.

We all know that Valve in general is "lazy"; they probably added both of these things at some point, called it a day, and never touched it again to address issues.

From my perspective, Steams controller support has yet another issue -- I actually have an XBox controller, but controller support feels obscure, undocumented, and more likely to get in the way than to help with anything. Thus, I'm primarily trying to shut it up... but then again, I've never even read anything factual about what this obscure "enable Steam input" actually does.

I know I have one game that actually needs it for the controller to work... which is not communicated or even enforced by the game, you have to learn it from the forums -- might not be Valve's fault to be honest, but it plays into the "Steam controller support obscurity mist"; at the end of the day I want games that work, and I don't really care who's at fault if it doesn't. I just know that 99% of the games work just fine (concerning controller support), and then there's one that requires me to play with Steam's obscure settings... and it doesn't even tell me.

That might be true, but frankly at this point I don't care.

All I can do is advise according to things now.

[spharin]

this looks like a lot of replies i'm too lazy to read

i'll take a peek later