Junior Member
Was excited to finally play the game again with all the good changes it looks like they've been making, but when I got into the game and launched a bot duel to practice, that old bug of the right and left triggers canceling each other out is still there (holding LT and trying to heavy just drops guard stance and does nothing as if they cancel each-other out). I tried some custom bindings like setting RT to right mouse button, or LT to ctrl, but the game didn't like swapping between xinput (controller) and mouse=keyboard on the fly and was doing weird stuff like dropping in and out of guard stance and occasionally losing input. I tried setting the triggers to digital rather than analog as well as changing physical buttons on the controller, but unfortunately all of these send xinput "left trigger" signals into the game, so they'll always have this bug and cancel each other.
Setting guard mode to toggle ended up being the best workaround, but I'd really love to be able to solve this if at all possible and it's kind of mind-boggling that this bug has existed for over a year.
Tested many configs in other games just to sanity check that my controller was working fine, no issues at all in anything except for honor. My friend with an Xbox One controller actually has the same trigger issue too, so it seems to be an actual bug in the way PC For Honor is handling the input.
Anyway, if anyone here is using a Steam controller and NOT the Steam copy of the game, what is your method for working around this bug?
P.S. It appears that even moving the left thumbstick causes guard stance to drop on default controls. Unfortunately I also remembered why having guard toggle wasn't ideal either. The ideal way to set up a steam controller was to use regular right pad as a mouse-like joystick for aiming things like feats, ballista, etc and having a modeswap on LT hold that converts right pad into a crossgate dpad for perfect digital stance changing, which is what my controller profile was set up as. I was sitting there confused as to why I had it set up like that since it clearly wasn't working, but then I remember that about a year ago when they did a patch to natively support steam controller (steam copies only of course) they did something that broke their input and it was since then that these issues started popping up.
Ubisoft Support Staff
Hey,
Can you please create a case on the support website and submit your DxDiag and MsInfo files for further investigation?
Thanks.
