Hey guys! Thanks for the reports - checked in with the team on this one and they have the issues logged (touch pad and ability menu binding blunders). We are taking a look at it. Apologies for the binding mess!
On 2020-05-13 at 10:28 AM, [DE]Danielle said:Hey guys! Thanks for the reports - checked in with the team on this one and they have the issues logged (touch pad and ability menu binding blunders). We are taking a look at it. Apologies for the binding mess!
Hey guys, we have investigated ‘Touch Screen’ related issues (with swiping to be specific) where custom bindings are not registering assigned commands and instead performing the default ability cast and unfortunately, as we looked into the bug we discovered that the fix touches on code that can only be changed via Cert. We understand this is a frustrating issue, as most are when out of Hotfix reach.
There is a temporary fix for the time being: If you chose to, reset your bindings to default and then reassign your ‘Touch Screen’ bindings. The newly assigned custom bindings should now work as intended until you close and re-open the game (rinse repeat after opening the game).
Apologies again, we will let you know when you can expect that fix.
3 hours ago, (PS4)FireGOD_2 said:Thank you for the update, Can live with that, any word on the L1 = ability Menu not working?
Yes! We actually fixed that in today's Hotfix 🙂
On 2020-06-01 at 7:10 PM, (PS4)BlightDragon89 said:In this very thread, Dani let us know that this is not hotfixable error. So unfortunately, we are going to have to wait till deadlock update for a fix.
Hey guys! Yes this is correct, the fix for the touch-pad issue will be coming with the Deadlock Protocol update on consoles. We are working on the build as we speak, we'll post the status thread once we are in Cert as usual 🙂
Thanks!
devtrackers.gg