Definitely the trans-Pacific part of the path where we're seeing the jump in ping. #6 PAIX is the NA point of entry, Palo Alto (California) Exchange. I see a slightly different trace from my end but with same results 52 ms (from western Canada) to PAIX then 190 ms for the next hop in Sydney, Australia. Telstra claims 138 ms from Sydney to Los Angeles on their newest link so what he's seeing is within spec. http://www.telstrawholesale.com.au/download/document/13123-telstra-endeavour-wbroch-asedit.pdf FWIW, we see mid-200 pings all the time with Aussie racers on our server. Generally there is no problem but I've always wondered if that accumulates over time then forces the game to re-sync everyone.
From near Daytona Beach. Tracing route to nrtservers.com [75.127.1.74] over a maximum of 30 hops: Tracing route to nrtservers.com [75.127.1.74] over a maximum of 30 hops: 1 * * * Request timed out. 2 9 ms 8 ms 8 ms ten0-0-0-7.orld50-ser1.bhn.net [71.44.61.242] 3 22 ms 11 ms 11 ms ten0-7-0-11.orld11-car1.bhn.net [71.44.61.250] 4 15 ms 22 ms 16 ms ten0-7-0-11.orld71-car1.bhn.net [72.31.10.12] 5 13 ms 15 ms 16 ms 72-31-193-133.net.bhntampa.com [72.31.193.133] 6 14 ms 16 ms 15 ms 4.68.70.153 7 51 ms 48 ms 62 ms ae-8-8.ebr1.Atlanta2.Level3.net [4.69.137.150] 8 47 ms 45 ms 45 ms ae-6-6.ebr1.Washington12.Level3.net [4.69.148.10 6] 9 47 ms 45 ms 46 ms ae-1-100.ebr2.Washington12.Level3.net [4.69.143. 214] 10 47 ms 47 ms 45 ms 4.69.148.49 11 48 ms 48 ms 49 ms ae-91-91.csw4.NewYork1.Level3.net [4.69.134.78] 12 47 ms 47 ms 46 ms ae-92-92.ebr2.NewYork1.Level3.net [4.69.148.45] 13 49 ms 45 ms 45 ms ae-4-4.car2.Buffalo1.Level3.net [4.69.140.241] 14 49 ms 56 ms 60 ms GIGLINX-INC.car2.Buffalo1.Level3.net [4.59.214.3 4] 15 54 ms 56 ms 59 ms host.colocrossing.com [198.23.150.78] 16 61 ms 60 ms 61 ms nrtservers.com [75.127.1.74] Trace complete.
A few little burps on it's way up from FL. but 60ms is about what I get also. Thanks for the post Dave NRT
Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\SkeleTele>tracert nrtservers.com Tracing route to nrtservers.com [75.126.240.52] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 * * * Request timed out. 3 9 ms 7 ms 9 ms 67.59.234.193 4 10 ms 11 ms 9 ms rtr4-ge1-10.mhe.hcvlny.cv.net [167.206.39.137] 5 25 ms 9 ms 10 ms 451be0cd.cst.lightpath.net [65.19.99.205] 6 12 ms 12 ms 11 ms 451be0e6.cst.lightpath.net [65.19.120.230] 7 27 ms 25 ms 40 ms rtr3-tg10-2.in.nycmnyzr.cv.net [64.15.0.33] 8 23 ms 22 ms 23 ms te3-5.bbr01.eq01.wdc01.networklayer.com [206.126 .236.185] 9 * * 34 ms ae0.bbr01.tl01.atl01.networklayer.com [173.192.1 8.153] 10 58 ms 68 ms 70 ms ae13.bbr02.eq01.dal03.networklayer.com [173.192. 18.134] 11 * * * Request timed out. 12 66 ms 87 ms 59 ms po1.fcr02.sr04.dal01.networklayer.com [66.228.11 8.178] 13 65 ms 55 ms 59 ms nrtservers.com [75.126.240.52] Trace complete. I have no idea what this stuff means but I was getting heavy lag on the GT server with 20 people just a moment ago
lag is still present on the servers without the plugin running (granted the room has to be half full) so is the plugin the problem? I know nothing about what makes a server lag but it seems the more the room fills up the more lag is present. This is true for the historics, touring and the worst for me in the current GT server with LD running. Could tracks cause issue with lag?
Sure, but it would depend on your system. This is why people get banned from servers a lot without knowing why. You can see when someone has their PC struggling and a low frame rate in their ping. Sent using Tapatalk - excuse the short post, etc
Obviously not. I think the ISI servers should work fine, with no crashes or lag for the vast majority of the time providing a solid and reliable service to a very patient user base whilst working very well, for the vast majority of the time, with the Liveracers plugin. I just really liked it Tim, thats all, thought it was a really good feature and I know you're disappointed too. Is there any way forward to get this, or a similar feature, working? Incidentally, I also think if a user enters a server and is found to be bringing problems to the server (don't know much about this stuff, here in the UK my ping in ISI servers is 115, fps around 30-80) then that user should be informed, excluded and advised. That problem should be eliminated.
Argo0: I spent close to an hour on our TS server with Stevo, the developer of Live Racers. We discussed the issues that we have seen, and he is going to look over his settings. We came to the conclusion on changing a setting and he will send it to me when he has it ready. At that time, and if Tim want's to try it, I will put it back on 1 or 2 servers and try it and see how it fairs out. Then go from there on the other servers. Dave NRT
From London,UK... Tracing route to nrtservers.com [75.127.1.74] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 192.168.1.1 2 126 ms 133 ms 163 ms host-83-146-18-122.dslgb.com [83.146.18.122] 3 151 ms 81 ms 105 ms ge-0-0-0.30.cht-cor-001.dslgb.net [83.146.22.30] 4 140 ms 117 ms 78 ms so-2-1-0.0.cht-cor-002.dslgb.net [83.146.19.82] 5 * * * Request timed out. 6 * 148 ms 90 ms ae-25-25.edge4.London2.Level3.net [4.69.200.89] 7 214 ms 237 ms 226 ms ae-3-3.ebr1.London1.Level3.net [4.69.141.189] 8 * 205 ms 199 ms ae-42-42.ebr1.London1.Level3.net [4.69.167.22] 9 256 ms * * vlan103.ebr2.London1.Level3.net [4.69.143.94] 10 * * * Request timed out. 11 * * 141 ms ae-81-81.csw3.NewYork1.Level3.net [4.69.134.74] 12 150 ms * * ae-82-82.ebr2.NewYork1.Level3.net [4.69.148.41] 13 * 222 ms 162 ms ae-4-4.car2.Buffalo1.Level3.net [4.69.140.241] 14 193 ms 190 ms 159 ms GIGLINX-INC.car2.Buffalo1.Level3.net [4.59.214.3 4] 15 268 ms 165 ms 200 ms host.colocrossing.com [198.23.150.78] 16 147 ms 173 ms 206 ms nrtservers.com [75.127.1.74] Trace complete.
From Peterborough, UK Tracing route to nrtservers.com [75.127.1.74] over a maximum of 30 hops: 1 9 ms 8 ms 7 ms 10.167.160.1 2 6 ms 8 ms 10 ms pete-core-2a-xe-021-0.network.virginmedia.net [8 0.3.130.65] 3 10 ms 11 ms 11 ms nrth-bb-1b-ae15-0.network.virginmedia.net [62.25 3.175.138] 4 13 ms 12 ms 14 ms brhm-bb-1b-et-000-0.network.virginmedia.net [62. 253.175.13] 5 16 ms 13 ms 15 ms manc-bb-1c-et-000-0.network.virginmedia.net [62. 253.175.70] 6 15 ms 18 ms 14 ms manc-bb-1d-ae2-0.network.virginmedia.net [62.253 .174.93] 7 31 ms 32 ms 32 ms 213.242.120.97 8 118 ms 127 ms 117 ms vlan80.csw3.Paris1.Level3.net [4.69.168.190] 9 117 ms 116 ms 117 ms ae-82-82.ebr2.Paris1.Level3.net [4.69.161.101] 10 117 ms 118 ms 115 ms ae-41-41.ebr2.Washington1.Level3.net [4.69.137.5 0] 11 117 ms 116 ms 116 ms ae-3-3.ebr1.NewYork2.Level3.net [4.69.132.90] 12 116 ms 117 ms 115 ms ae-1-100.ebr2.NewYork2.Level3.net [4.69.135.254] 13 116 ms 117 ms 115 ms ae-47-47.ebr2.NewYork1.Level3.net [4.69.201.33] 14 116 ms 115 ms 117 ms ae-4-4.car2.Buffalo1.Level3.net [4.69.140.241] 15 119 ms 129 ms 115 ms GIGLINX-INC.car2.Buffalo1.Level3.net [4.59.214.3 4] 16 118 ms 119 ms 119 ms host.colocrossing.com [198.23.150.78] 17 128 ms 128 ms 143 ms nrtservers.com [75.127.1.74] Trace complete.
How about just asking about it in your first post like you did in this one, rather than immediately sinking down as badly as you can feel? This reply was great. Yes, we are working with LR to hopefully solve this by reducing the updates rate. You can't really say it's their plugin, but probably is our usage of that plugin (5 servers). Reducing the updates rate should solve it I believe, the dev I asked believes and Dave at NRT believes. Though there will still be lag with users who join with a 1000 ping that goes between 100-1000 because of either their connection or their system being worked too hard. Not much we can do about those guys.
The lag is there with our without the plugin. It's most notable at the start of races when there's an incident. As soon as cars start to spin, slow or change directions quickly all goes to hell. P.S.
Well, I only said I was very disappointed. On the other hand, sorry mate. Sent from my GT-I9000 using Tapatalk 2
Thanks folks for the trace routes, As you can see from "some", they struggle sometimes getting to the server, but if they do another it is likley to be issue free. I could gather the ping results, put them in a nice support ticket, and send it to the bandwidth carrier(s), they would come back with a Thank-you but, the average together is within net quality. Not that I am not going to try, But expect the above reply. Dave NRT
That will not be a problem, I would think we are all working to a resolve. It will likely be released from Live Racers when resolved. Thanks Dave NRT
