Hello! I’ve been having some controller input problem since the latest update launched. I mapped my controller in a way that I hold R1 or R2 and press the face buttons to use skills. I main Paladin and recently I’ve been accidentally activating my Judgement numerous times during gameplay. This is especially frustrating during a legion raid. Normally pressing Triangle (Y button) would activate Judgement, but I meant to do R1 + Triangle. I thought this was a controller issue so changed my controllers twice, another PS4 controller and a PS5 controller, but still getting the same problem. I even watched how I press the buttons closely and I was still activating it accidentally. Please help.
Sorry to hear you’re having this problem . I’ve moved this over to the support section so our support team can check into this problem with you.
my Controller didnt work anymore since the patch. some time he didnt get input. tryed ps5 and xbox elite, both with the same problems. friends have this problems too… pls bring our old gampad configuration back!!!.. thats why you should never change a runing system!!. btw if you will do a great controller support than change the aim assist to the target in front of you, atm we have aim assist to the enemy near you and this sucks! and maybe you can adjust the running animation for other players because we gamepad players only run smoothly for ourselves and for every other player we look like bots with lag!
Hello @JoshuaHotPapi and @chira.tschanun and thank you @Centeotl for moving this one over,
I am sorry to hear you are having issues with the mapping of your controllers ever since the last update. I have tried to locate possible solutions but am sorry to say I have fallen short in this scenario. I have reviewed all the data you have provided and thank you for the information. Due to the type of issue you mention and how it does not match the expected behavior, this thread would be better addressed in the Bug Reports section.
I have moved the thread back. Hope this helps and see you in Arkesia!
This is currently a known issue and is being looked into.
Thanks a bunch for moving this back .