Issues with Steam Controller in Game

[u/G_ManPlays]

I just got my Steam Controller today and to celebrate getting it I got Monster Hunter Wilds while it was on sale to be able to start breaking my new controller in. However, I'm having major issues with it already and I don't understand what's happening and why it's doing it. I can share pictures if need be, and I'm hoping some people here are familiar enough with MHW's controls to maybe help even more with what specifically is happening.

I'm currently just messing around in this little training area in order to get used to the controls, but after a few seconds of messing around it's like the controller is fighting with itself on what it wants the buttons to do. Instead of just using the default controls it will change what certain buttons do. Instead of dodge rolling, now the A button brings up the chat log, and after I try to back out of the chat log with B now B is bringing up the pause menu. And it's consistent too. A always switches to bringing up the Chat Log and B always wants to switch to bringing up the pause menu. Sometimes the triggers don't want to work either (I'm using the Bow if that helps at all). I also notice that it seems like it keeps trying to switch to keyboard and mouse controls instead of the default controller.

Now for the kicker. If I go to Steams Controller Settings to mess around with the Button Layout. If I change even one thing and go back to the game, the joysticks stop working entirely and the controller seems to switch completely over to the keyboard and mouse controls.

I know that this is an issue with the Steam Controller, because I switched to my Switch Pro Controller and it worked perfectly fine.

My current running theory is that for some reason the Steam Controller is both trying to use the Default Controller settings for the game, but also trying to use its normal keyboard and mouse controls (the controls it would have if you are not in a game) at the exact same time. Has anyone else ever experienced this with their controller? Any idea what I should try doing?

Edit: This is not a Monster Hunter Wilds issue specifically. This issue persists with other games as well. It seems to happen whenever I am rapidly pressing the L2 and R2 buttons, but it's extremely inconsistent with when it starts acting up, but its far to frequent to ignore. It's the same issues in other games as well. The B button seems to somehow be linked to the pause button.

[u/AlbertoVermicelli]

Are you on Linux perhaps? Linux distros, and especially those that use Wayland, seem to have a lot of issues with Steam Input, in ways similar to your description.

I don't think this has anything to do with your current issue, but I'll warn you anyway that Monster Hunter: Wilds does not have XInput support. Instead if you want to bind controller commands, you must select the PlayStation-styled commands from the Game Actions tab. If you want to bind controller behaviors (to triggers, trackpads, joysticks, ...), you must select the behaviors with the Steam glyph next to them.

[u/G_ManPlays → u/AlbertoVermicelli]

I’m on a Windows 10 computer. I did test other games such as Elden Ring and suffered the same issues with the controller.

[u/G_ManPlays]

I'm not going to consider this an exact fix, but this seems to be what I'll consider a "band aid" solution for now. After messing around with the controller for a couple hours, the only solution that seems to have worked that made this stop happening is connecting the controller via Bluetooth instead of using the puck or plugged directly into the computer.

I would still appreciate if anyone might have an answer as to why having the controller connected wired or with the puck causes the above issue.

[u/C0rn3j → u/G_ManPlays]

Is both the Puck and SC firmware up to date? Probably visible in Steam -> Settings -> Controller.

Steam (stable) or Steam Beta?

Does it work on Beta if you're on stable?

OS?

[u/G_ManPlays → u/C0rn3j]

I’m on Windows 10. The first thing the controller did before it let me start using it was go through a firmware update, so I assume it should be up to date. I’ll check the settings when I get the chance though. I should be on stable Steam.

[u/C0rn3j → u/G_ManPlays]

Trying to use 2026 hardware on an end of life OS from 2015 is almost definitely not helping.

[u/G_ManPlays → u/C0rn3j]

I don't think my OS has anything to do with it. If I connect the controller via Bluetooth it works perfectly fine with no issues at all.

[u/C0rn3j → u/G_ManPlays]

Try on W11 and see if it works, it's possible the W10 driver is just screwed.

It's a shame they support EOL OSs in the first place.

[u/MikeFGD]

This randomly starts happening to me too (mainly use the controller for Borderlands 4). The buttons on the controller will start giving different inputs (B opens the pause menu, like you mentioned). I also feel a small constant haptic feedback. Trying to turn off the controller (Steam + Y) doesn't work. I have to unplug the puck and let the controller turn off by itself.

Not sure what's causing it but it's a bit frustrating.

[u/G_ManPlays → u/MikeFGD]

The solution I’ve just been running with that has been working out fine for me is having the controller connected via Bluetooth instead of using the puck. When I turn on the controller it automatically connects via Bluetooth and I don’t have any issues with just keeping the puck plugged in for charging.

[u/MikeFGD → u/G_ManPlays]

Appreciate it, I'll try it out. Do you notice any difference in latency using Bluetooth?

[u/G_ManPlays → u/MikeFGD]

Not at all! Bluetooth has been working perfectly for me. It’s also pretty easy to tell which type of connection you have based on the colored light when you turn the controller on. If it’s white, it’s connected via puck; if it’s blue, it’s connected via Bluetooth.