Hello.
I noticed a conflict when configuring the keys. I tried swapping the “Utility” and “toggle Runes” keys, but they can both be the same key. In this case, the rune indicator doesn’t appear. Shouldn’t it give a warning when we assign the same button to two different features? In this case, this shouldn’t be possible.
Hello,
Since i am a fan of Dodging on R2 i was trying to find a working remap but encountered some inconsistencies. Hope this counts as “bug” ^^.
Remapping parry to one of the normal buttons (YXAB) removes it from the Toggle section of the Runes. But since the Runes only activate while holding this should work.
Remapping Offhand item use to L2 makes Block work with a shield but wont let me use a bow.
Remapping parry AND toggle runes to R1 works though. Im sure there are other combinations that are bugged. I gave up at some point 
This is highy irritating….
Hi Inkognico,
I do not own a controller but is something out of this thread useful to your issue?
If not, could you clarify a little bit more what you are trying to accomplish? I have read your topic multiple times but I cannot grasp it (yet!).
Please and thank you!
Silas
I am trying to accomplish a working controller remap that suits my playstyle.
I have read the other post and the reason it is behaving like that might be in there but that would be a bit lazy programming. I cannot really imagine the devs doing that.
Lets take one example:
I put parry on “X” (XBox controller). The game then removes “X” from the Toggle Runes set.
Happens with YBA the same way. Yet the rune on X should trigger on LB+X so why would it be unbound in combination with the parry on X? It works with other buttons like the interact Y or the attack A.
So A attacks and LB+A is the rune in the runeslot. But A parry and LB+A does not work because the game unbinds A in the rune section when assigning parry to A.
But i can put both toggle rune AND parry on LB…(Which was a nice workaround but a bit awkward).
Is that a bug or has it a reason i am unaware of?
The other example would be having “use offhand”. I have it on LT so i can aim a bow. So my thought would be holding LT to aim and firing with A. Not happening. Charater does not activate the bow.
When i equip a Shield though it does Block…which is a bit strange. (Having bows as offhand is already strange though. Xbows like the NPCs have would be better. Bows can only be fired 2 handed, always )
These are my 2 main examples. There are more of those combinations i do not understand. Maybe ill take my time to list them.
Hope this helped.
1 Like
First: I customized my controller layout and changed, among other things, the interact button from Y to LB. This also updated the interaction tooltips. However, after leaving the game and returning the next day, the change to the control itself persisted, but the tooltips reverted to the default, now incorrectly showing Y as my interact button instead of LB.
Second: When using utility runes, I need to press RB together with one of X/Y/B/A. But when I’m out of focus for a specific rune, even though I’m holding RB, the game executes the actions assigned to the X/Y/B/A buttons as if I never pressed RB. For example, since I assigned my food to Y, when I try to execute the RB+Y action while out of focus, I unintentionally end up eating food.
On a side note I’ve always been a mouse and keyboard PC player, and this is literally the first game I’m trying to play with a controller (since the Pegasus in the 90s). I’m honestly disappointed by the lack of deeper customization I can’t even remap all actions the way I want.
I’m using a Steam Controller.
1 Like
Text in the image: Ok so. I have xbox controller. B does nothing by default so as suxh i have rebinded it to switch main hand weapon. If you have a rune ( both utility and weapon rune) i. The third slot thay would go to B. That will be activated only when you oress the other button to activate runes ( rb, rt). Issue is that with switch weapon bound to B, when you activate the third rune it also switches weapon. For some reason unlike dodge (a) attack (x) and interact (y) which gets deactivated once the rune selection is open it is
By Jeancly on Discord
1 Like
This topic has been merged into and will act as Main for the foreseeable future for any bugs related to “controller keybinds, key mapping not working properly”.
I’ve done some more testing, any button configuration keeps the issue. Even in the customization menu for the controls if you put something that is also used in the runes menu it stops you even though it’s tecnically not a conflict ( since you need to press the extra button to access said submenu )
1 Like