Update 9.20 Bugs, Issues and Feedback
Дата: 01.09.2017 23:09:04
Blackstone, on Aug 31 2017 - 03:20, said: Updated drivers. No more crashes. BUT THE GODDAMN
RUBBER-BANDING FROM THE SERVER IS STILL HAPPENING.Saffr0n: Please post traceroute
Blackstone, on Aug 31 2017 - 11:57, said: Noticed another small bug: While viewing tanks in the
garage, I noticed the flags and other tank art wasn't on any of my
tanks. Went to the side art screen and you can't view any of them
at all. Not on the tank or the selections below. The weird thing is
all of my tanks do have whatever side art I applied to them. You
just can't "see" it. Stealth side art?Saffr0n: Please post a screenshot
GHR1227, on Aug 31 2017 - 17:57, said: Getting lots of packet loss and rubber banding plus loading into
battle up to a minute late. I ran in safe mode and
still happens so it's not mods. Ping is health 40-50
which is good considering I'm in Houston and one of the nodes (bear
creek) the data goes through is located right in the addicks flood
plain. Ping plotter shows lots of spikes, but
they are only to 90ms which should be insignificant. The
last server before hitting Wargaming, IP 4.53.98.230 shows latency
is 327ms, but no packet loss there and average is still
<40ms. SO what is wrong? This
much packet loss never happened even on test server the other day
with 300ms ping. Target Name:
wotna3.login.wargaming.netIP: 92.223.56.16
Date/Time: 8/31/2017 12:45:19 PM - 8/31/2017 12:55:19 PM Hop Sent PL% Min Max Avg Host Name / [IP]
1 61 0 1.39 12.01 2.61 10.0.0.1 [10.0.0.1]
2 61 0 9.41 181.43 22.22 96.120.17.177 [96.120.17.177]
3 61 0 9.29 195.21 27.33 xe-10-1-1-sur03.tidwell.tx.houston.comcast.net [69.139.208.5]
4 61 0 10.67 206.65 29.39 ae-60-ar01.bearcreek.tx.houston.comcast.net [68.85.245.201]
5 61 100 0 0 0 [-]
6 61 0 34.18 112.43 43.75 ae-14-3604.edge4.Chicago3.Level3.net [4.69.204.166]
7 61 0 33.84 327.02 55.00 4.53.98.230 [4.53.98.230]
8 61 0 34.19 58.06 39.26 wotna3.login.wargaming.net [92.223.56.16] My PC is I3-4130, 8GB RAM, Win10, GTX nVidia750Ti 2GB, 250GB SSD.
Saffr0n: Look at the traceroute as a whole rather than separating the
trace into individual hops. The fluctuations you see at
68.85.245.201 are the same as the fluctuations in hops 2
and 3 ( all of which are within your ISP's network). Any affect
resulting from your ISP will go down the trace and be
problematic. The Level 3 hops are configured to mitigate
unnecessary packets and prioritize the necessary ones, which is why
many people may notice PL on Level 3/Telia/Cogent hops -- and
attribute this observation to server lag or major packet loss that
causes rubberbanding, which is incorrect. In this trace, you should
also notice that at the last hop, which is the server, the latency
stabilizes. This would confirm that this isn't a server issue, but
there's a fault somewhere within Comcast's routing. Unfortunately,
we have no control over how your ISP chooses the pathway to the
server, we can only control routing from Level 3/Telia/Cogent
intermediary hops.
Update 9.20 Bugs, Issues and Feedback