92 replies to this topic

[___ImUrHuckleberry]

Acrisis, hope you wouldn't mind confirming this with me? WG issue, not ISP as i had suspected?

 

 

EDIT: couple of minutes later 

 

Edited by YouHaveAbeeOnUrHatch, 13 August 2021 - 06:06 AM.

[acrisis]

Saw your message here [ http://forum.wotblit...king-my-device/ ] before seeing this.
Already responded there. 

Points of observation here:

74% loss at the handover from Frontier to Level3. When that happens, it will not get any better.

Often times a small or large loss there, will show identical all the way up the line. ( so it would show for instance 10% loss on all points 5 6 7 8 9 all the way down, as an example )

 

I am not seeing the blank lines from Gcore Labs ( the hosting provider ) before it gets to the server ... so something is amiss there between 14 and 15, as I just pinged both login0 and login1 ... both ping fine ... and I am getting the blank lines on pingplotter desktop and mobile. 
 

 

But, let's try to troubleshoot your issue in that other thread [ http://forum.wotblit...king-my-device/ ] 

 

[_Crusader6_]

Note the .36 address is offline -- that is no longer the login1 address.

   That s why Huck is having issues

[__V_O_P__]

Okay.. here's a question... ping plotter is tracking 34 ping on average to Login0...(I'm logged into server 0) but in game the ping indicator is all over the place. Last game it was up to 400 and rubber banding. So... how does ping plotter and WG get such different results?

[acrisis]

Simultaneously? Same device? Same connection method? 
 

My ping on pingplotter and wotb usually track closely, like within 5-10 ms … with a slight edge for my wired network over wifi.

[__V_O_P__]

acrisis, on 22 August 2021 - 04:52 PM, said:

Simultaneously? Same device? Same connection method? 
 

My ping on pingplotter and wotb usually track closely, like within 5-10 ms … with a slight edge for my wired network over wifi.

same device... same connection method. re simultaneous - well I saw the ping spikes in game (felt them as well) and checked ping plotter afterwards... nada.

[_Dtankshooter]

FPS been real bad since new update smth

[acrisis]

__V_O_P__, on 22 August 2021 - 05:26 PM, said:

same device... same connection method. re simultaneous - well I saw the ping spikes in game (felt them as well) and checked ping plotter afterwards... nada.

Interesting. When I am having issues, I run it on computer while playing on tablet. 

[acrisis]

_Dtankshooter, on 30 November 2021 - 02:17 AM, said:

FPS been real bad since new update smth

Graphics load keeps increasing with more and more visual features. 

Try turning down your graphics settings a bit. Several of the settings are not that important and can be put on medium or low. Or turned off.  

[_Crusader6_]

__V_O_P__, on 22 August 2021 - 05:26 PM, said:

same device... same connection method. re simultaneous - well I saw the ping spikes in game (felt them as well) and checked ping plotter afterwards... nada.

Sorry I wasn't tracking this thread routinely.

 

The In Game Ping indicator gives ping not just to your device - but to your screen - so any graphic issues (GPU throttling for instance) will be shown as ping spikes on screen -- this won't be shown in PingPlotter.

 

 After 7+ years of running Max settings - I bit the bullet and turned off camouflage for all but me - guess what - my ping issues disappeared.

     There seems to be an issue with the way WG has overwritten code for certain tanks and camouflage - so spotting created a huge graphic load and all of a sudden you spike and get clobbered.   Removing camo from the equation solves that (although legendary camo's are still seen those don't seem to have the same effects).

 

 

[__V_O_P__]

_Crusader6_, on 02 December 2021 - 04:55 PM, said:

Sorry I wasn't tracking this thread routinely.

 

The In Game Ping indicator gives ping not just to your device - but to your screen - so any graphic issues (GPU throttling for instance) will be shown as ping spikes on screen -- this won't be shown in PingPlotter.

 

 After 7+ years of running Max settings - I bit the bullet and turned off camouflage for all but me - guess what - my ping issues disappeared.

     There seems to be an issue with the way WG has overwritten code for certain tanks and camouflage - so spotting created a huge graphic load and all of a sudden you spike and get clobbered.   Removing camo from the equation solves that (although legendary camo's are still seen those don't seem to have the same effects).

 

 

philips hue lights. that was it for me. I just moved and everything was all good to start. I plugged in the hues and my ping went out the window. I now live in a hue free zone. ping is good. 

[acrisis]

Thanks for sharing!

 

It is amazing how much interference a simple plug-in device can cause.

 

Microwaves are notoriously evil, had my first fill of that way back when wifi first came on the market and the various gadgets on the same band for Audio Video streaming/relay, little cameras, etc. Could use one at a time pretty much.

Even wireline. Getting some networking and/or smart home stuff to work over the electrical grid in your home. Fluorescent lights and their ballasts, appliances with motors, ...  

 

Speaking of light bulbs. Here's a fun one: plain old LED light bulbs.  Some of the early LED to replace some CFLs ( slow to warm up dingy light ) interfered on electricity and cable signal. That was a fun one to chase down ... I can't imagine how many hours and days I wasted, trying to sort it out ... until one time it accidentally was crystal clear. 100% signal fine. 6 canned lights on in the bathroom. Signal gone. 6 canned lights off. 100% signal fine. Unscrewed the LED bulbs and grabbed a more recent set. Solved.  But imagine putting some new led light bulbs in spring or summer throughout your house, to replace your CFL bulbs; you are not aware of any issue rightaway, then maybe a glitch here or there, but you barely use lights in the summer time, ... then months later, why would you suspect light bulbs instead of faulty gear, bad weather, bad antenna, bad aiming, ... 

 

I have not used any of those smart bulbs. They can be handy and plug and play, but again, it is a simple thing made " smart " that suddenly becomes something that sends and receives data ... and if it runs anywhere near the wifi bands to create its own little mesh network. 

Our stuff runs both wireline and 915 MHz MESH ... kind of akin the old cordless phone stuff. 

Anyway. Smart bulbs, certainly something to keep in mind. 

[change_my_mind]

Lots of information. I just upgraded my router, and this lag happens.  Ghost shots, view changes at critical moments, tanks appearing and changing positions from one second to the next.

 

It sounds like it is easy to blame the player. This game is becoming trash. The implementation, player base, and on and on.

[acrisis]

change_my_mind, on 14 January 2022 - 11:22 PM, said:

Lots of information. I just upgraded my router, and this lag happens.  Ghost shots, view changes at critical moments, tanks appearing and changing positions from one second to the next.

 

It sounds like it is easy to blame the player. This game is becoming trash. The implementation, player base, and on and on.

So, you changed routers (or upgraded the firmware of an existing one) ... resulting in networking issues that include ping and/or packet loss when you play online games ... and so you draw the conclusion of WG blaming the player? 

Please tell me how WG is to blame for the networking issue in your own home? 
 

[Padre_ShadowRider]

Somebody help me.    I have put in a ticket and they tell me it is my initial ISP,  BUT  the traceroute shows a complete drop out near chicago.   The game is unplayable for the past 3 days.    Can anyone interpret this to see if it is my ISP or something wonky in the Net: 

traceroute: Warning: login0.wotblitz.com has multiple addresses; using 92.223.57.35

traceroute to login0.wotblitz.com (92.223.57.35), 64 hops max, 52 byte packets

 1  192.168.1.1 (192.168.1.1)  126.343 ms  18.818 ms  21.098 ms

 2  192.168.10.1 (192.168.10.1)  54.454 ms  41.944 ms  6.457 ms

 3  10.101.0.1 (10.101.0.1)  33.277 ms  114.372 ms  80.653 ms

 4  10.100.100.1 (10.100.100.1)  109.469 ms  305.369 ms  56.765 ms

 5  rrcs-***.sw.biz.rr.com (****)  54.028 ms  7.387 ms  68.418 ms

 6  ae15.wmbrtx0602h.chtrse.com (97.77.0.224)  73.732 ms  97.980 ms  32.808 ms

 7  agg41.ausxtxir02r.texas.rr.com (24.175.42.200)  52.787 ms  16.036 ms  32.695 ms

 8  agg22.hstqtxl301r.texas.rr.com (24.175.41.48)  54.769 ms  111.883 ms  41.303 ms

 9  ae-1-0.p0.atl90.tbone.rr.com (66.109.1.218)  77.008 ms

    66.109.9.88 (66.109.9.88)  238.778 ms

    bu-ether16.hstqtx0209w-bcr00.tbone.rr.com (66.109.6.108)  88.371 ms

10  107.14.19.49 (107.14.19.49)  84.311 ms *  49.348 ms

11  107.14.19.192 (107.14.19.192)  33.855 ms  169.047 ms  135.301 ms

12  107.14.19.197 (107.14.19.197)  95.640 ms  78.477 ms  85.094 ms

13  209-18-43-61.dfw10.tbone.rr.com (209.18.43.61)  390.363 ms *

    66.109.5.225 (66.109.5.225)  187.426 ms

14  eqix-ch1.gcore.lu (208.115.136.42)  45.585 ms  44.678 ms

    as199524.xe0-0-11.chix2.ch1.unitedix.net (206.41.110.77)  204.783 ms

15  * * *

16  * * *

17  * * *

18  * * *

19  * * *

20  * * *

21  * * *

22  * * *

23  * * *

24  * * *

25  * * *

26  * * *

27  * * *

28  * * *

 

Attached Files

•   Ping.jpg   106.42K

Edited by Padre_ShadowRider, 20 January 2022 - 05:19 AM.

[acrisis]

Well, that's a rather messy signal situation that you have found yourself in. 

When you have such bad ping and packet loss all long the way, then the game server is certainly not to blame. 
The 100% loss lines have to be ignored, it is network equipment that cannot be pinged. There is no loss there. (discussed this with pingplotter folks) 

 

The primary thing to keep in mind is that at the top there's you and your device, home internet, isp, and then a route to the game server at the very bottom.

 

From the start (top), we can see that your connection is simply not stable. When you lose 5% of packets before the signal leaves the house and your average ping is already 100 ( between 6 and 400 ) and you lose packets so close; everything further out is always going to suffer. 

That's why there is just a consistent series of red lines (packet loss) all the way down, at each stop. 

The setup looks unusual with 4 counts before the actual router ... you need to start by sorting that out and drastically simplifying.

 

[Hugzy_]

Acrisis,

Thanks for the info yet in my case totally irrelevant.  Am running off my company's 100G backbone and we keep it clean 24/7/365.   

 

Lag spikes are typically caused on the server side e.g. hard drive failing, system compromised, etc. etc. unless it is on the client side, which in this case it is not.

 

Great rant trying to sell a product.  -_-  

[Hugzy_]

acrisis, on 21 January 2022 - 02:09 PM, said:

Well, that's a rather messy signal situation that you have found yourself in. 

When you have such bad ping and packet loss all long the way, then the game server is certainly not to blame. 
The 100% loss lines have to be ignored, it is network equipment that cannot be pinged. There is no loss there. (discussed this with pingplotter folks) 

 

The primary thing to keep in mind is that at the top there's you and your device, home internet, isp, and then a route to the game server at the very bottom.

 

From the start (top), we can see that your connection is simply not stable. When you lose 5% of packets before the signal leaves the house and your average ping is already 100 ( between 6 and 400 ) and you lose packets so close; everything further out is always going to suffer. 

That's why there is just a consistent series of red lines (packet loss) all the way down, at each stop. 

The setup looks unusual with 4 counts before the actual router ... you need to start by sorting that out and drastically simplifying.

 

Obviously you are unaware of the realities of everyday life on the Internet.  Companies are being compromised daily by hackers and are being submitted to Malware infections, DDOS, etc.  Stating that it 'cannot be on the server side'  is very ignorant.  If you are a network engineer, please by all means contribute.  Do not come and state 'facts' which you received from a 3rd party.  Thank you!

[j_rod]

Hugzy_, on 12 April 2022 - 09:17 AM, said:

Obviously you are unaware of the realities of everyday life on the Internet.  Companies are being compromised daily by hackers and are being submitted to Malware infections, DDOS, etc.  Stating that it 'cannot be on the server side'  is very ignorant.  If you are a network engineer, please by all means contribute.  Do not come and state 'facts' which you received from a 3rd party.  Thank you!

If the issue was at a macro level on the server side then there would be a mass of complaints on here and on Discord. When the server has had issues (and it has), these complaints are addressed and the problem is fixed, although communication isn't always stellar. The rest of the time, the issue is either on the player side, somewhere in between, or is sometimes found to be latency within the game itself (bad programming after an update). 

 

Telling an IT guy and long time forumer that he is unaware of the realities of the internet when he's trying to help you is about as dumb as it gets. 

[acrisis]

Hugzy_, on 12 April 2022 - 10:14 AM, said:

Acrisis,

Thanks for the info yet in my case totally irrelevant.  Am running off my company's 100G backbone and we keep it clean 24/7/365.   

 

Lag spikes are typically caused on the server side e.g. hard drive failing, system compromised, etc. etc. unless it is on the client side, which in this case it is not.

 

Great rant trying to sell a product.  -_-  

 

Hugzy_, on 12 April 2022 - 10:17 AM, said:

Obviously you are unaware of the realities of everyday life on the Internet.  Companies are being compromised daily by hackers and are being submitted to Malware infections, DDOS, etc.  Stating that it 'cannot be on the server side'  is very ignorant.  If you are a network engineer, please by all means contribute.  Do not come and state 'facts' which you received from a 3rd party.  Thank you!

I am far from unaware of the realities on the internet.
 

When there is 5% of packet loss within the user's own network ... then that simply is not a server issue.