It's been about 24 hours since we identified and corrected an issue affecting server network range and client render distance. Since the fix, we've seen a substantial increase in both server and client performance. Please leave some feedback and let us know if Monday (for Connery/Emerald) or Tuesday (for Miller/Cobalt/Briggs) night's play session felt better than previous sessions. I also wanted to provide a few network status updates as well. Miller/Cobalt: We are in the initial stages of a peering agreement with Deutsche Telekom that will allow us to exchange traffic directly with each other, avoiding our ISPs altogether. Briggs: We are exploring a peering agreement with Telstra as well, based on network performance feedback from Australian players Thanks, -PC
Was the fix to do with spotting targets beyond your render range, sometimes seemingly on the other side of the map? Didn't notice any of that tonight. Server performance on Miller during tonights (Tuesdays) peaktime Indar Alert felt a lot more responsive compared to previous days. No vehicle warping or unresponsive terminals. Real test will be next Sunday as thats been by far the worst day for server performance in recent weeks. Thanks for the update!
I just jumped off after playing for a bit on Emerald. Server performance for me was way down marked by bad hit detection (bullets would stop doing damage at random after each shot with no hitmarker) and unusually high ping (@127 up from 70-90). Players were also not rendering at the correct distance when I was at Xeno Tech Labs. Also I'm not sure if the floating infiltrator head bug is back but there were an awful lot of people shooting at me from a very far off distance while I was cloaked. A few snipers nailed me with head shots a couple of times as well.
Please look at peering with PIPE networks for Briggs as most Australia ISP's currently peer with them. http://www.pipenetworks.com/pipeix-who.php#NewSouthWales
I know you can't share details but aren't those peering agreements quite expensive? And If so, do this mean we encounter another round of "how-to-make-more-money" from DBG? I mean don't get me wrong, I don't mind DBG making more revenue but my screen can only shake that much.
Could you explain why it is that I've been seeing an improvement from the UK, without a hop via DT, when the focus is on DT? Also will removal of ISPs (or whatever that means ) for Germans give them an advantage over the rest of us? i.e. in before Germans OP...
Had some weird ones tonight. Most notable one was everyone disappearing when I flew in close to ground targets.
It was like I was playing on my 5yo computer again. I did not hack any turrets, so the problem of invisible people popping out I could not test. I did not see any invisible people popping of flashes, so that is good. I'm becoming more convinced that the FPS number I have in the bottom left corner is a lie. I've played this game on 15FPS on my old computer and I am well aware of what that is like. I've played this game on my brand new i7, GTX750 and it seriously feels more and more like my old computer. In no way do I believe that 50FPS because it honestly feels like the 15 I got on my old computer. The hackers that are plaguing this game... I know you guys are probably doing everything you can to patch this latest hack, but yeah, it is completely oppressive. Priority number 1 should be making this game clean again. Overall: this last play session was pretty awful.
I haven't noticed any latency improvements, and since Monday I have had really bad lag spikes that I have never encountered on this PC before. They are almost like mini-freezes, and generally only last less then a second, every 10-20 mins or so. Although I do not know for sure what is causing these spikes, I doubt it is because of my PC, as I haven't had this problem before and there have been no hardware changes to my PC. Not game breaking, but annoying.
For AU/Briggs, peering at Pipe wont gain you much. NSW-IX and Equinix are the two I'd suggest, but your already getting your routes propagated via Equinix peering last I looked. I'm on a Telstra Cable connection at home - looks pretty good to me (and is consistently good): C:\Users\thermal>tracert 69.174.220.23 tracing route to 69.174.220.23 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 192.168.1.254 2 14 ms 8 ms 7 ms 10.251.0.1 3 8 ms 13 ms 9 ms 58.160.24.73 4 8 ms 9 ms 9 ms te6-3.agg2.fli.bigpond.net.au [58.160.27.250] 5 13 ms 11 ms 8 ms bundle-ether4.way-edge902.adelaide.telstra.net [203.50.116.102] 6 10 ms 11 ms 11 ms bundle-ether8.way-core4.adelaide.telstra.net [203.50.11.152] 7 24 ms 28 ms 24 ms bundle-ether9.exi-core10.melbourne.telstra.net [203.50.11.93] 8 38 ms 43 ms 39 ms bundle-ether12.chw-core10.sydney.telstra.net [203.50.11.124] 9 37 ms 34 ms 35 ms 10gigabitethernet7-1.chw45.sydney.telstra.net [203.50.20.183] 10 34 ms 35 ms 35 ms equini3.lnk.telstra.net [139.130.117.214] 11 34 ms 35 ms 33 ms xe-1-0-1.gw102.sy3.ap.equinix.com [27.111.240.147] 12 33 ms 33 ms 33 ms xe-0-0-0.gw101.sy3.ap.equinix.com [27.111.240.136] 13 35 ms 35 ms 35 ms 27.111.243.178 14 33 ms 33 ms 33 ms 69.174.220.23 Inbound traceroute to you is good - its not going to get any better than that. My IP is 58.160.169.xxx, not sure what the return path to me is, but based on the RTT its about as good as it gets. If you want some more info about this happy to have a chat - large ISP networking (in Australia) is my day job.
Well... I started off with bad connection - hits were registering, but displaying hitmarkers and actually doing damage happened somewhere between 0.5 and 1.5 seconds later. Same thing for any interaction(terminals, entering leaving vehicles) or ability activation - which makes sniping kinda hard. The connection was SO bad that PS2 didn't even bother to display my ping btw . I hopped in the game again a couple hours later, this time good connection and 90ms ping (most of the time). Issues I noticed: Grenades exploding next to me and then rendering - yes in that order. It is very hard to prove it, but I think people sometimes didn't render or didn't render fast enough. I was shot several times from corners of a room I just checked. What I definitely know did not render was a Vanguard that shot at the A point at Regent Rock. I was simply turning around looking for wtf hit me, and after getting killed and revived 6 times in a row he finally did render - or at least his tracks did. Neither his turret nor his shells rendered when he finished me off the 7th time and I had enough of this BS.
This is my trace route/netinfo. Emerald is still crap jumping from poor - bad connection from 200ms - 1000+ms Windows IP Configuration Host Name . . . . . . . . . . . . : ...-PC Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Intel(R) Ethernet Connection (2) I218-V Physical Address. . . . . . . . . : 78-24-AF-8C-F4-4A DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::49b:bf5a:b7a4:ebb0%11(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.0.3(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : 27 February 2015 20:07:16 Lease Expires . . . . . . . . . . : 01 March 2015 12:49:13 Default Gateway . . . . . . . . . : 192.168.0.1 DHCP Server . . . . . . . . . . . : 192.168.0.1 DHCPv6 IAID . . . . . . . . . . . : 242754735 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1C-5C-BF-DA-78-24-AF-8C-F4-4A DNS Servers . . . . . . . . . . . : 192.168.0.1 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter isatap.{BCA4AF9B-12F6-4003-AEFF-887DA35F70E3}: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Teredo Tunneling Pseudo-Interface: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2001:0:9d38:6abd:201c:118a:a151:1d08(Preferred) Link-local IPv6 Address . . . . . : fe80::201c:118a:a151:1d08%12(Preferred) Default Gateway . . . . . . . . . : :: NetBIOS over Tcpip. . . . . . . . : Disabled Tracing route to lp.soe.com [64.37.171.213] over a maximum of 30 hops: 1 <1 ms 2 ms <1 ms routerlogin.net [192.168.0.1] 2 10 ms 8 ms 7 ms 10.13.196.1 3 8 ms 12 ms 12 ms basl-core-2a-xe-210-0.network.virginmedia.net [62.252.175.1] 4 12 ms 35 ms 11 ms brnt-bb-1a-ae10-0.network.virginmedia.net [81.96.0.145] 5 * * * Request timed out. 6 24 ms 12 ms 14 ms brnt-bb-1c-ae0-0.network.virginmedia.net [62.254.42.198] 7 11 ms 11 ms 10 ms ae10-xcr1.lnd.cw.net [195.2.9.149] 8 19 ms 13 ms 40 ms ae6-xcr1.lsw.cw.net [195.2.25.29] 9 * 18 ms 20 ms lag-20.ear1.London15.Level3.net [212.187.195.177] 10 228 ms * 226 ms ae-0-11.bar1.LasVegas1.Level3.net [4.69.148.125] 11 177 ms 172 ms 172 ms SWITCH-COMM.bar1.LasVegas1.Level3.net [205.129.16.50] 12 170 ms 172 ms 179 ms 64.37.171.213 Trace complete. Tracing route to lp.soe.com [64.37.171.213] over a maximum of 30 hops: 0 ...-PC [192.168.0.3] 1 routerlogin.net [192.168.0.1] 2 10.13.196.1 3 basl-core-2a-xe-210-0.network.virginmedia.net [62.252.175.1] 4 brnt-bb-1a-ae10-0.network.virginmedia.net [81.96.0.145] 5 * * * Computing statistics for 100 seconds... Source to Here This Node/Link Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address 0 ...-PC [192.168.0.3] 0/ 100 = 0% | 1 1ms 0/ 100 = 0% 0/ 100 = 0% routerlogin.net [192.168.0.1] 0/ 100 = 0% | 2 --- 100/ 100 =100% 100/ 100 =100% 10.13.196.1 0/ 100 = 0% | 3 11ms 0/ 100 = 0% 0/ 100 = 0% basl-core-2a-xe-210-0.network.virginmedia.net [62.252.175.1] 100/ 100 =100% | 4 --- 100/ 100 =100% 0/ 100 = 0% brnt-bb-1a-ae10-0.network.virginmedia.net [81.96.0.145] Trace complete.
I have to say, that I was yesterday playing on cobalt (indar). And I had i really nice 32 ping. Before it was 90-120. So yeah it was a really a nice night.
Most of the outfit played last night on hossin on Miller. Maybe the first outfit night in months where it hasn't been **** due to server lag. Cheers.
No. IIRC, there was a court case a few years back with DT regarding throttling/premium lanes and that stuff was ruled out. Afaik, its still illegal, so that shouldn't be an issue (#NetNeutrality). Your ISP however, is still the last mile and could be a chokepoint if they dont have their s#lt together. But in theory, that would mean great news for everybody as DT owns that whole infrastructure and ISP's just rent it from them essentially.
DT is also a Tier 1 provider with numerous hubs outside Germany, so with some luck you'll get a better connection through their Tier 1 network than you get now through someone like level3
Yesterday evening was pretty laggy on Cobalt even on the lower pop continent. Much killexchanges. Then again im from germany (Not DTAG).
Cool. It's nice to hear about the developments. Lag on Miller has been bad, but it's way worse when you have no idea whether or not it is being worked on.
Got a lot better for me. Also on prime so please keep improving. My average ping was around 120ms. 90ms Is normal for me.
