Swapping Confirm/Cancel face button to nintendo style without swapping the in-game action (steam input).

[Tatsuja Ogawa]

We all know that you can swap (in steam input) the confirm/cancel face button to a Nintendo style. But the in-game (the game self or keybinding (for non-siapi games)) action (layer) configuration also swaps the face button. It does mean that I have to reconfigure the action in the configuration. It's a small complaint but the question remains: Is it possible to swap the confirm/cancel face button without swapping them in
in-game action (layer) configuration? So you can keep consistence controller scheme.

[EDƎN]

But why would you even use Nintendo layout though? You would probably hate that B in Steam and B in a game do different things.
Think about this like playing US games on japanese PS3. It would be confusing as hell because you would use O to confirm in XMB and X in games.
The option would still be nice though

[Balderick]

Originally posted by EDƎN:

But why would you even use Nintendo layout though?

maybe newbigpicture ui is showing wrong button prompts and/or giving bad controller mapping? where enabling nintendo button layout fixes for newbigpicture ui

Steam Input should just use last game config for controller type last used with that controller but is always worth checking game config before launching game after chnaging general controller settings to make sure an appropriate config is used for your preferred controller type in game.

Steam INput always needed configured for controller and configured for game where "Define Layout" allowed easy saving layout as different controller type.

[Tatsuja Ogawa]

Originally posted by EDƎN:

But why would you even use Nintendo layout though? You would probably hate that B in Steam and B in a game do different things.
Think about this like playing US games on japanese PS3. It would be confusing as hell because you would use O to confirm in XMB and X in games.
The option would still be nice though

It's not the best argument I would say but I have a Dualsense controller, and my preference is to use O as confirm because some Eastern country: O is correct, and X is wrong. That's the reason why I want to take the challenge to use this method. And I'm not confused or I'm getting used to train this way, but your mileage may vary. Xbox is a different story that I'm not going to touch too quickly.

[LAN021]

Originally posted by TatsuyaGuen:

We all know that you can swap (in steam input) the confirm/cancel face button to a Nintendo style. But the in-game (the game self or keybinding (for non-siapi games)) action (layer) configuration also swaps the face button. It does mean that I have to reconfigure the action in the configuration. It's a small complaint but the question remains: Is it possible to swap the confirm/cancel face button without swapping them in
in-game action (layer) configuration? So you can keep consistence controller scheme.

This isn't possible except for in Steam Input API, where you have different action sets for in-game controls and menu controls. Remember that Steam Input is an XInput emulator at its core--it just sends the XInput buttons to the game (and KB/M keys, if you use those). This is entirely a game-dependent setting and nothing that Steam Input can alter.

I play with the Japanese/Nintendo type of Confirm/Cancel myself--it is simply my preference, we don't need to discuss it further--and I just swap A and B in Steam Input and then remap those buttons in the game, if possible. I can live with the prompts being wrong--I'm quite used to reading cross as the right face button and circle as the bottom face button by now (I use a PS4 controller).

Originally posted by EDƎN:

But why would you even use Nintendo layout though? You would probably hate that B in Steam and B in a game do different things.
Think about this like playing US games on japanese PS3. It would be confusing as hell because you would use O to confirm in XMB and X in games.
The option would still be nice though

You can change the Steam BPM configuration separately in BPM, which I have done. Not that I use BPM much.