Guild Wars 2

I play on a laptop and whenever I run GW2, it keeps switching between charged and battery mode, as if I was constantly plugging and unplugging the A/C, or if the plug itself wasn’t well plugged. I know it’s not a problem from outside GW2 as when I exit the game, the problem stops…

Anyone could help me? A little bit at loss here… Never heard of something like this.

Never had this problem before & just now started doing it. Could be related to the new update as I hadn’t updated my client in a few days.

Thanx
Thoth

So additional info: the problem only occurs when I am in-game: character select & loading screen are fine…

Might wanna post this in Tech Support instead. I’m pretty suspicious of laptop gaming…esp. if the laptop is dated.

Do you have a key bind on the PC that swaps it out and you are hitting it when you do a combo with your character?

I will try posting in tech support. However, no, there is no keybind and I have never had this problem in the past on any other game nor Guild Wars 2.

Yep, this should really go into the tech support forum.

To your problem:
I have the same issue, but only if the battery is below appr. 50%

In my opionion it is an issue with the software/electronics which detects if the battery is being charged.
On a heavy load situation it might get wrong results for the batterys state.

I’ve not tested this further as GW2 is currently the only game I’m playing which needs a bit of power.

Might help if you could tell us your laptops brand/model.

Mine is an:
Acer Aspire V3
Core i5-3210M
NVIDIA GeForce GT 650M
8GB RAM

Yeah, the problem seems to be linked with how low the battery is. Now that the battery is full charged the problem has disappeared…

Just an update/bump in order to hopefully get some sort of answer: if the battery is at 100%, no problem. But if it’s any lower (even 99%) it will bug out. Basically, it keeps switching between battery and a/c power constantly (every half a second or so). If that can help, I am on an Asus ROG.

Fix found… it seems that putting the energy mode on “Battery Saving” even if it’s charged fixes the issue… If anyone else has this problem.

As this issue has been resolved, the thread is now closed.