reapex.8546 Posted January 10, 2018 Share Posted January 10, 2018 Hello, I've been using the letter V for my mount ability 2 skill, this letter is also assigned to my interact key. After the patch, it will no longer let me use mount ability 2 skill 'v' when gliding. It seems the latest build does not allow you to use a key that is already assigned to another button already for mount ability 2. Yeah, just tried using other keys that are already assigned and they don't work for mount ability 2. However, mount ability 1 works fine for the 'v' key.Has anyone else experience this? Link to comment Share on other sites More sharing options...
reapex.8546 Posted January 10, 2018 Author Share Posted January 10, 2018 Update: No keys assign to mount ability 2 for the Griffon are working, after the latest patch. Link to comment Share on other sites More sharing options...
Krypto.2069 Posted January 10, 2018 Share Posted January 10, 2018 Reapex, like you, I have my Mount Ability 2 key mapped to "V." My "V" key is also mapped for my Elite skill. With that said, when I press my "V" key when gliding after a dive, it does pull me back up into the sky. And when not mounted, "V" does execute my Elite skill. So it's working as it did before for me (aka - works correctly). Just wanted to provide you some feedback. Not sure what could be causing your issue. Perhaps try removing the "V" key mappings completely then reassign? EDIT: I guess you could also try running a -repair on your client. https://wiki.guildwars2.com/wiki/Command_line_arguments Link to comment Share on other sites More sharing options...
reapex.8546 Posted January 10, 2018 Author Share Posted January 10, 2018 @"Krypto.2069" said:Reapex, like you, I have my Mount Ability 2 key mapped to "V." My "V" key is also mapped for my Elite skill. With that said, when I press my "V" key when gliding after a dive, it does pull me back up into the sky. And when not mounted, "V" does execute my Elite skill. So it's working as it did before for me (aka - works correctly). Just wanted to provide you some feedback. Not sure what could be causing your issue. Perhaps try removing the "V" key mappings completely then reassign? EDIT: I guess you could also try running a -repair on your client. https://wiki.guildwars2.com/wiki/Command_line_argumentsOkay, so maybe I'm tired. But everything is working now with the letter 'v'. Its possible, I wasn't dashing but I thought I was. At any rate, thanks for you help things are alright now :D Link to comment Share on other sites More sharing options...
Krypto.2069 Posted January 10, 2018 Share Posted January 10, 2018 Cool beans! Glad to hear it! :+1: Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.