The difference between us SEA players and the chinese players are quite significant... If they play in US or AUS servers, they will experience a lot of lag and the players fighting them will see them as a bunch of nightcrawlers... we SEA players dont experience that kind of thing from the very beginning and the aussies didnt complain about us playing with them.. but as time goes by, it only gets worse.. And it just doesnt make any sense that i could get so many packet losses from a server much closer to me than any other servers... it just angers me so much due to the fact that a month ago, i have none of these issues... the question is why is this happening now?? they reassured us with constant optimisation and yet the game gets worse and worse.. does it make any sense??
Briggs has its share of login issues, particularly at prime time but I don't think the issue you're having with packet loss is happening at the server end. C:\Users\Rod>ping 69.174.220.23 -t Pinging 69.174.220.23 with 32 bytes of data: Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=18ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=18ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=16ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=16ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=16ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=18ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Reply from 69.174.220.23: bytes=32 time=17ms TTL=118 Ping statistics for 69.174.220.23: Packets: Sent = 49, Received = 49, Lost = 0 (0% loss) Approximate round trip times in milli-seconds: Minimum = 16ms, Maximum = 18ms, Average = 17ms Pretty stable my end, always has been. Don't think I've dropped a single packet while testing as I used to run them when having huge delays in logging in.
Okay, let's just say it's on my end and not the server's end.. Can SOE explain why I'm not getting any packet losses from a server much much further away from me?? I can guarantee you I have no such issues with every other servers... How do you explain that?? This is a very inconsistent with the server Briggs.. I should be having the same problem with the other servers if it were on my end, right??
Yeah, I mean like why now, why it never happen before, I feel bad those people having same problem and they spent on this game. I think its not from the players end since alot of us(from Malaysia probably) having this kind of problem. This must be something not right on the server or our country itself.
I'm old so I know this isn't a new problem. There is a lot of info online that will explain it better than I could here,. Do a little research on how the internet works and you will see why it may not be your ISP or the server. You should also find out about some other tools you could use to find out where the issue may be. The trace below shows that I shouldn't play more than a couple of hops into New Zealand with my old reflexes' And that it has nothing to do with the SOE server in Australia, it is that it has to go through NZ first. Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\Player2>tracert 69.174.220.23 Tracing route to 69.174.220.23 over a maximum of 30 hops 7 26 ms 27 ms 23 ms ae-5-0.cr0.nyc30.tbone.rr.com [66.109.6.74] 8 93 ms 95 ms 91 ms 107.14.19.34 9 93 ms 91 ms 92 ms ae-6-0.cr0.sjc30.tbone.rr.com [66.109.6.14] 10 120 ms 95 ms 91 ms ae-0-0.pr0.sjc20.tbone.rr.com [66.109.6.139] 11 101 ms 92 ms 93 ms f0-0.pabr1.netgate.net.nz [198.32.176.97] 12 93 ms 92 ms 92 ms ae0.sjbr2.global-gateway.net.nz [203.96.120.73] 13 243 ms 247 ms 245 ms xe7-0-0.tkbr9.global-gateway.net.nz [202.50.232. 17] 14 246 ms 245 ms 245 ms xe6-1-0.sebr1.global-gateway.net.nz [202.50.232. 234] 15 249 ms 243 ms 243 ms ae1-10.sebr2.global-gateway.net.nz [202.50.232.2 42] 16 246 ms 245 ms 243 ms aapt-int.sebr2.global-gateway.net.nz [202.50.238 .214] 17 255 ms 244 ms 246 ms lag40.sglebinte01.aapt.net.au [202.10.14.193] 18 251 ms 252 ms 252 ms 203-174-189-250.syd.static-ipl.aapt.com.au [203. 174.189.250] 19 275 ms 250 ms 248 ms xe-0-0-0.gw101.sy3.ap.equinix.com [27.111.240.13 6] 20 249 ms 249 ms 249 ms 27.111.243.178 21 250 ms 252 ms 249 ms 69.174.220.23 Trace complete. C:\Users\Player2>
Okay, assuming it's not on my end and not on SOE's end either.. I don't really care where it goes first, be it South Africa or Mars... The question remains, why is the so called server or terminal or whatever in NZ misbehaving NOW?? Because I used to have a good time, so the thing in NZ must be doing something right at the time... And now it suddenly hates SEA players?? Not an excuse any gamer can accept.. I get what you're trying to say.. This is just to show what goes where and where.. It still does not answer the question as to what is wrong with the connection between SEA and AUS?? And why it is far worse than US or EU?? And to be real honest, why does it have to go through NZ anyway?? (Edit : Thinking about it, there may be something wrong with the NZ connection for the time being and it may be out of SOE's hands.. Oh well, sucks to be me)
And if SOE is really serious about providing an epic scale warfare to players, then they have to think big and think of ways to connect to the rest of Asia.. Asia is just being brushed aside with nowhere to go.. Can't play EU, US and now AUS.. We are literally stuck in the middle of nowhere? After all, Sony is from an Asian country.. If they do nothing, then this game is a freaking gimmick, at least to Asians... I may be wrong to say this, but Briggs would be a whole lot emptier without SEA players.. or at least, less farming to do for the Aussies
Quite easy to explain, you're not taking the same route. I take it you're in Malaysia? Can be any hop between you and the Briggs server that could be dropping packets. Just because you're losing packets doesn't mean the destination server is the cause, can be any hop between you and the destination server that's dropping packets. Do a tracert to 69.174.220.23. You'll see the route your packets take to get to Briggs. I'll guarantee that if you did a tracert to one of the US servers, it'll route through a different path pretty quickly. C:\Users\Rod>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 home.gateway.home.gateway [192.168.1.254] 2 16 ms 17 ms 17 ms nexthop.nsw.iinet.net.au [203.215.17.248] 3 17 ms 16 ms 16 ms te1-1.syd-ult-bdr1.iinet.net.au [203.215.16.22] 4 20 ms 16 ms 16 ms ae6.cr1.syd7.on.ii.net [150.101.33.114] 5 17 ms 17 ms 17 ms ae5.br1.syd7.on.ii.net [150.101.33.50] 6 35 ms 19 ms 17 ms ae0.br1.syd4.on.ii.net [150.101.33.14] 7 25 ms 17 ms 17 ms p17819.syd.equinix.com [202.167.228.120] 8 80 ms 17 ms 17 ms xe-1-0-1.gw101.sy3.ap.equinix.com [27.111.240.145] 9 18 ms 17 ms 17 ms 27.111.243.178 10 17 ms 17 ms 18 ms 69.174.220.23 Trace complete.
More than may well, it's absolutely out of SOE's hands. What happens between your client and the network SOE utilises at the destination is at the mercy of the Internet. Either hope the problem on that hop is corrected or taken down so you'll route through a different path. What do you propose they do? Don't they have servers in China(?)
I'm not sure if the9 server is available for non-chinese players.. There are no servers I can join to get there... It's pretty much exclusive to China.. They never said anything about opening doors to other Asian countries...
trace route using icmp/udp won't work if u're from malaysia since TM (telekom malaysia) has block trace route.... probably dont want use to know how crappy their service is try this instead , it uses tcp http://www.visualroute.com/
https://dl.dropboxusercontent.com/u/2346385/site/VisualRoute.htm i uploaded my visualroute traceroute on my dropbox as html, as you can see it is having problem with telstra internet hop. Can some higher-ups mind explaining what's the problem here?
Wow, thanks.. I guess this is a more reliable method of tracing out the problem.. However, due to the apparent lack of interest from SOE to even respond to this thread shows that they do mind... They could at least tell us that that they acknowledge the issue rather than just giving us all a cold shoulder.. We're basically talking to a wall...
If the traceroute shows several of the hops to be high ping (especially if they are routing from say an origin in Malaysia, routing through HK> New Zealand then finally through Australia), surely the fault lies with your isp rather than SOE. I can understand those complaining of slow logins but warping due to lag lies at both yours and your isp's feet. In the past when I've had such issues, I've contacted my isp with the appropriate evidence and asked for them to help resolve the issue. In all cases they have been very helpful.
I am no tech geek, so this is very likely very wrong, but what the heck: Some providers (in Europe f.e.) do deep packet inspection which might result in packet-los, mebbe? Also it might help to upgrade your connection with "fast path" - Some providers offering that for a very small fee (in germany it costs 1 Euro/month to upgrade)
