-
Client(?) issues
Hello,
recently(~1month) I've been having issues with my game.
The game "freezes" as if I disconnected, but all the spells go through on the server side and people see me moving and casting normally.
My discord works normally while these spikes happen and I've tried pinging warmane login servers and it shows the normal 50ms ping.
I didn't download any model edits/addons when this started and have noticed no connection on what triggers it, it can happen anywhere and any time of the day. It can go for a week without a single lagspike and be almost unplayable for a whole day after.
What I've already tried:
--Disabling all addons
-Allowing wow windows firewall
-Forcing the game to run on 1 cpu core
-Running the game on lowest settings
-Using a different game client(warmane&excalibur)
-Running wow from an SSD or normal hard drive
-Using normal cable internet or wireless internet from my phone and they're from 2 different providers
Here's a quick video of it:
https://youtu.be/_Q2znAxro9Q
-
It's not a client issue. It looks more like a network issue. Since it's happening on 2 different connections, the problem is most likely either somewhere in the middle between you and Warmane servers, where both connections have to go through, or locally on your computer. The problem could be packet loss. If a packet is lost, WoW client is unable to process the packets after it until the lost packet is sent again by server and received by client.
You have to ping the realm not logon server. You can find the IP in Resource Monitor -> Network. For example, current IP of Icecrown is 79.137.41.100. Also you can add "-t" to the ping command so it does not stop after 4 times and you can see if any packets are lost over a longer time period.
Example:
Code:
ping 79.137.41.100 -t
In Resource Monitor you can also check if network activity of WoW.exe doesn't get higher while it happens. It could also happen if server starts sending you higher amount of data for some reason.
-
Cheers for the quick response, I had a feeling that login server wasn't the right address to ping but couldn't figure out how to get the server IP.
I'll keep an eye on resource monitor and ping the servers next time it happens.
-
Was stable for few days, but started happening today again
here's a screenshot of pinging the server and resource monitor
https://i.imgur.com/g80uAOR.jpg
-
Under TCP connections you should also be able to see packet loss. It's a column further to the right. Not visible in the screenshot. The rest seems pretty normal. Ping command has 2 small spikes but that alone should not cause such problems. But there could have been other problems at that time, which caused those spikes.