I have found a bug - whilst most keys remap if you assign them to another function, some appear to but in actuality dont.
For example - I like to have strafe left and right on Q and E so they are next to W for moving forward, and when you change E to strafe right, it appears to remap use to D for USE, which works for MOST but NOT all things:
When you want to take a book, the option for taking it is ALWAYS "E" no matter what you bind E to, and if E is bound to strafe, rather than taking the book, it actually just turns the page - the only way to take the book if this happens is to exit book menu, and change it back to D being strafe temporarily, take the book by pressing E, then change it all back, which is a major pain
ALSO
again, if E is bound to strafe right you cant use the enchant table properly - it insists on you using E, but if E is bound to strafe, it wont work.
Can we get a fix please? Simply get it to check the keymaps for use, rather than just always asking for E, and then not working when E is bound to strafe?
Thanks
This issue has been mentioned, but I think it isn't well understood by most people. The problem stems from the UI using derived keybindings. For example, if you remap your Sheathe/Ready Weapon key from R to something else, other actions that share the same key (e.g. Drop, Store, Craft, etc.) will use that key, despite the fact that the UI will display the default key "R" as the button to press (these are static images and don't change if you rebind keys). The "R" key doesn't seem to be plagued with as many problems as some other derived actions, however. The "E" key, which is used for enchanting, and some other keys simply won't work as derived commands if you rebind their "parent" keystroke (meaning the basic keybindings that are listed in the manual). Other keys allow you to change the "parent" keystroke, but their derived commands will not change. An example of this is the Run/Sprint key, which is ALT by default. If you change this key to LEFT SHIFT, it seems to work fine, but if you are running and want to walk briefly, say when you're sneaking, SHIFT does nothing - you must use ALT, provided you haven't mapped ALT to something else, in which case, that functionality is LOST to you. What we are left with is essentially a mandatory use of the default keymappings. Once keys get rebound, certain actions become impossible. You got that, Bethesda? I M P O S S I B L E.
It's unclear exactly why the button art doesn't change. socrates200X indicated that it was a conscious decision based on the performance hit it would take to provide images for all possible keystrokes, but the fact that some derived keystrokes are
not changed when you remap the parent command suggests that perhaps there is something else going on. It almost seems like the UI was designed by two individuals who didn't coordinate their efforts.