Lag....... Insane lag

[Alucard_Vampyre_Hunter]

Ever since the new update, i have been getting lag. No, not normal lag, but lag to the point where i'll hit between 490ms to 700ms. These lag times are throughout the entire game. However, if i go to any other MMO (ie, SWTOR, ESO,) I don't have any lag issues. Im at a loss. any Ideas or suggestions?

[Super_S1X]

There's nothing Wargaming can do about lag (Which also means updates do not cause your lag), or to influence the lag you are experiencing. Lag is a product of your distance from the server, and the route that your ISP uses to get your data from/to the server.

 

What do other MMOs have to do with anything? They have different servers, different locations, and different DNS protocols?

[Ace_04]

I've been having similar lag issues since the update. Tried a full uninstall and reinstall, so we'll see how that works out.

[Doutech]

Make sure the Game Center is not running in the background. This entire weekend I could not understand why I was having such severe lag until I saw a thread on the Game Center. After exiting out of it, there was no lag. So try that.

[AVR_Project]

I've detected a new generation of Lag Spike generators out.

I saw this first when an enemy ship, firing from concealment (distance), did NOT appear after firing.

The Shells came from nothing, as if in smoke, and the ship didn't show up for 2 full seconds after it fired.

I took note of the user name and kept an eye on this operator.  I ceased fire and went dark.

Every time this operator fired main guns, the ship motion would stop and the lag readout would jump to 150-200 usually, sometimes to 400.

What this creates is a position update illusion where this person seems to be standing still, when they are actually moving.

We would return fire with a wrong estimate of where they would be.

Furthermore, it also freezes our controls for that lag time -- for everybody in this match -- on both sides.  So your WASD won't work while shells are on the way.

...

It's a cheat.

It used to be manually breaking the RJ-45 connection with a push button, but cheat software was made to replicate this in the computer, on-command -- like after the LMB is pressed.

I believe the on-line WOWS server side should be able to detect this pattern and associate the error recovery with an operator firing using Left Mouse Button

If a person cheats - and gets away with it, they will never come back -- unless they are caught and punished.

[MrKilmister]

There's nothing Wargaming can do about lag (Which also means updates do not cause your lag), or to influence the lag you are experiencing. Lag is a product of your distance from the server, and the route that your ISP uses to get your data from/to the server.

 

What do other MMOs have to do with anything? They have different servers, different locations, and different DNS protocols?

 

There is a notable CC/players who has been streaming three times per week on Twitch for at least six months. I've watch regularly for more than 5 months. He has been dealing with wild moment to moment FPS and ping fluctuations that clearly began when 0.6.6 and Ultra went live. If it were in fact an ISP problem, his stream, which runs from a separate dedicated machine, would having correlating problems, too. 

[Crustay]

This has been happening to me as well.. All other games work fine. (ESO, PUBG, CSGO) Only when i come to WoWs does it start to lag like this. I just did a uninstall/reinstall and played my first game thinking that it would help, but ming ping was in the 9000 range. Absolutely insane. Before the patch i have never had this problem. 

[Super_S1X]

I've detected a new generation of Lag Spike generators out.

I saw this first when an enemy ship, firing from concealment (distance), did NOT appear after firing.

The Shells came from nothing, as if in smoke, and the ship didn't show up for 2 full seconds after it fired.

I took note of the user name and kept an eye on this operator.  I ceased fire and went dark.

Every time this operator fired main guns, the ship motion would stop and the lag readout would jump to 150-200 usually, sometimes to 400.

What this creates is a position update illusion where this person seems to be standing still, when they are actually moving.

We would return fire with a wrong estimate of where they would be.

Furthermore, it also freezes our controls for that lag time -- for everybody in this match -- on both sides.  So your WASD won't work while shells are on the way.

...

It's a cheat.

It used to be manually breaking the RJ-45 connection with a push button, but cheat software was made to replicate this in the computer, on-command -- like after the LMB is pressed.

I believe the on-line WOWS server side should be able to detect this pattern and associate the error recovery with an operator firing using Left Mouse Button

If a person cheats - and gets away with it, they will never come back -- unless they are caught and punished.

 

You have no idea what you're talking about. Don't open your mouth if you're this staggeringly ignorant about technology.

[MrKilmister]

 

Since he brought it up and describes the issue in latest video this morning...

 

[Super_S1X]

 

Since he brought it up and describes the issue in latest video this morning...

 

 

When people say "lag" I assume they are referring to ping. What you're describing might be that the new ultra sounds are poorly optimized, and the extra work mobo sound cards are having to do is hogging resources from the CPU/GPUs. Virtually no one has dedicated sound cards these days, because high quality sound is provided by onboard sound cards, and badly coded "high def" sound like what WOWS implemented is likely at fault.

 

It might cause FPS drops, but not ping lag.

 

It's possible that the update caused various ISPs to reroute traffic to WG servers along a less efficient DNS route, but unlikely.

[Bril01]

No issues here but I know some people have mentioned they are having lag issues since the patch.

[JervisBay]

I've definitely experienced FPS issues since the latest update.

This isn't imagination.....something in the update has caused a problem which never occurred prior to that download and what Notser described is exactly the same.

 

[MrKilmister]

I'm just glad I'm not having any sort of FPS, ping, or lag issues myself.  The extra delay on the kill/ship sunk klaxon is annoying but that's a whole other matter. 

[eVa_Refuel]

Make sure the Game Center is not running in the background. This entire weekend I could not understand why I was having such severe lag until I saw a thread on the Game Center. After exiting out of it, there was no lag. So try that.

 

Quoted for truth

[ArcDeath]

Where is war game center?

 

[vonshaunus]

I've definitely experienced FPS issues since the latest update.

This isn't imagination.....something in the update has caused a problem which never occurred prior to that download and what Notser described is exactly the same.

 

 

This is absolutely real and I experience it. Prior to the last patch game performance was very good. It is now very poor. night and day from one day to the next

[ArcDeath]

Where is war game center and how do I turn it off pls!

 

[Krautjaeger]

Make sure the Game Center is not running in the background. This entire weekend I could not understand why I was having such severe lag until I saw a thread on the Game Center. After exiting out of it, there was no lag. So try that.

 

^^ That.

 

Also, the installer for the old and simple launcher can still be found here: http://dl-wows-ec.wargaming.net/na/files/MDcyICBcdT/WoWS_internet_install_na.exe If one wants to get rid of the WGC, and go classic.

[Battleship_Constitution]

I've detected a new generation of Lag Spike generators out.

I saw this first when an enemy ship, firing from concealment (distance), did NOT appear after firing.

The Shells came from nothing, as if in smoke, and the ship didn't show up for 2 full seconds after it fired.

I took note of the user name and kept an eye on this operator.  I ceased fire and went dark.

Every time this operator fired main guns, the ship motion would stop and the lag readout would jump to 150-200 usually, sometimes to 400.

What this creates is a position update illusion where this person seems to be standing still, when they are actually moving.

We would return fire with a wrong estimate of where they would be.

Furthermore, it also freezes our controls for that lag time -- for everybody in this match -- on both sides.  So your WASD won't work while shells are on the way.

...

It's a cheat.

It used to be manually breaking the RJ-45 connection with a push button, but cheat software was made to replicate this in the computer, on-command -- like after the LMB is pressed.

I believe the on-line WOWS server side should be able to detect this pattern and associate the error recovery with an operator firing using Left Mouse Button

If a person cheats - and gets away with it, they will never come back -- unless they are caught and punished.

 

you do understand anything hack wise with a WG server would instantly reset the server to the last saved information. This was done WAY back when with tanks when WG decided during beta that the server would handle anything that would have to do with game mechanics. NOTHING in your client handles anything with game mechs. all of the client side DL's are cosmetic to the game and information to read the server nothing more.

[AVR_Project]

 

You have no idea what you're talking about. Don't open your mouth if you're this staggeringly ignorant about technology.

 

I troubleshoot electronics and programming for a living.  It's my day job.

[AVR_Project]

 

you do understand anything hack wise with a WG server would instantly reset the server to the last saved information. This was done WAY back when with tanks when WG decided during beta that the server would handle anything that would have to do with game mechanics. NOTHING in your client handles anything with game mechs. all of the client side DL's are cosmetic to the game and information to read the server nothing more.

 

Each game is a running program.  It has inputs and outputs.

The intent is to pass the information (fire weapons), then after a few milliseconds delay, send a packet with an intentional protocol error, affecting the server at the hardware level.

There is a resend request and the loop continues, tying up the bandwidth for the duration of the spike.  The error count cannot exceed a certain limit - would take experimentation to see what that limit is.

Think of it like an error on your CD player.  The music stops, or skips.

In this case, all client updates are suspended until the error is resolved.  If each user had a dedicated patch line into the game server,, this would be ineffective...  but there isn't.

I have the ability to create such a device, but I will not - and I won't tolerate those who do.

..

Another way is to jam the system full of 'good' dummy packets, rather than creating errors.  This would need to be done outside the client.