Healix
commented
5 months ago By default, ctrl+v is used when entering the login, since pasting allows GW2 to confirm to Gw2Launcher that something was entered. How long the key is held will depend on how quick GW2 is to respond. Worst case, the key is held for up to 5 seconds and retries every second for up to a minute, but normally it should only take 1 second total.
If you don't want to use the control key, Settings > Guild Wars 2 > Tweaks > Change how the email/password is entered - disable verification and use post for entry. If you're having Gw2Launcher enter authenticator codes, the control key will still be used for that.
Be sure to have the frame limiter set under the graphics options, otherwise GW2 is going to use as much CPU as it can.
GW2 has required more resources ever since DX11 was added, and has been increasing with the expansions. Expect it to get worse as they start using more demanding features of DX11.
This has been going on for a while, and I don't know if it's an issue with the launcher (probably not), Guild Wars 2 or my computer or whatever, but whenever I am launching multiple instances of Guild Wars 2, it often acts as though I have tapped or am holding the control key down. This usually occurs when the launcher is busy filling out the login information on the new instances. Sometimes if it gets "stuck," I have to tap the control key to get it to return to the off state. Additionally, if I am moving around in a different instance, it will kind of have a bit of lag. I can initiate movement like normal, except when I release w/a/s/d etc. it will keep moving for a while afterwards. (I end up overshooting my target.)
Perhaps it has to do with Guild Wars 2 starting to use way more of my computer's CPU. I used to be able to run many instances with relatively minimal impact on the processor. Now whenever I start new instances, each one often spikes the processor eating 20-25% and having more than a few instances open now often lags the computer. It didn't do this before.