Dualsense R2 problem.

[Lust1nTheDust]

So im having issues with R2 button on dualsense edge controller. Doesn't work propeply for first and sometimes 3rd time, on marking enemies and breaking doors. Shooting works just fine. Anyone else has it?

[NPC]

I'm having the same problem, glad I'm not alone. There seems to be some issues with the trigger range on the Dualsense on R2 / Right Trigger. Prying is really hard to do, I had to set it to toggle in the Accessibility menu. I'm still playing around with the Steam Controller layer options to see if I can find what is causing it.

[NPC]

The way they are using the Steam Controller layer is very interesting. All of the various possible in-game functions are assigned in a big stack to the triggers. R2 alone has ten different actions assigned, so figuring out where the conflict is coming from is frustrating.

[Gatsu]

Me too, can not pry open doors with controller (DS4).

[NPC]

Okay after some experimentation, here's what fixed it. Seems there is a conflict with certain commands when the Steam Input option is enabled. When I disable the Steam Input, it now all works fine: tagging and prying both now function as normal. When I enable it, however, it goes back to the same weird double-fire, not-working problem.

The problem here appears to be that the Steam Input layer meticulously replicates the default in-game mappings, which can _also_ be configured in-game. So for example, you go to the in-game mappings, you see that "Tag" and "Pry" are both assigned to the R2, and then you see them repeated if you go to the Steam Input mappings. I could be mistaken here, but this then makes it appear as if _all_ such mapping have a chance to be erroneously duplicated when using the Steam Input.

My "solution" was to go into the Steam Input, find R2, and remove both the "Tag" and the "Pry" actions from the assigned action stack. After returning to the game, those actions still work, because they are assigned as such in-game as well. Which... is really really dumb.

For others, the obvious solution might be to disable Steam Input entirely. In my case, that's not an option: I'm using a Dualsense Edge, and Steam Input is the _only_ way to remap the back paddles and function buttons to custom actions.

[I_come_in_peace]

i think you have to disable Steam Input because the game supports the Dual Sense natively (over USB).

[NPC]

I'm gonna see if it's possible to just forcefully re-map all of the Steam Input buttons to just function as that: default buttons. But might be a chore to do...

[NPC]

Yeah, upon further experimentation it seems that some of the specific actions are bugged when using Steam Input. The two I've confirmed so far are "Focus Tag" and "Pry" - they double-up, whereas most others I've tried so far don't. I wish there was a bug report forum, seems like something they should be able to fix pretty easily.

[Razor]

Originally posted by I_come_in_peace:

i think you have to disable Steam Input because the game supports the Dual Sense natively (over USB).

save my day, thx

[NPC]

For those wishing to still use the Steam Input layer for whatever reason (say, you want to enable gyro aiming on L2 pull, for example), I was able to completely reset the profile, and after that, the issue stopped as well. So if that is something you need, consider just resetting the profile before disabling it entirely.