Forums » Bugs
Serious lag with server to the UK....
Allo folks. Since the last upgrade or 2, I've been having 2 major problems that might or might not be related to each other. Up 'til then, the game's been behaving perfectly.
1} - I've been getting some serious lag when I'm logging in to the game. All is well until I click the 'Accept' button on the EULA, then it can take up to 5 minutes to get into the station - It might be longer but I clicked the cancel button at 5 mins.
If I get in before 5 mins, the lag when jumping between sectors/systems is up to 2 mins, which really messes with my Escort missions.
2} - When targeting ships (Killing Spree), they'll suddenly either flick to another point in space (instantaneous) or slide extremely rapidly, if I shoot at them in their new spot, there's no damage at all until they suddenly zoom back to their original place.
If I'm escorting transport ships, they'll perform the same trait, suddenly appearing waaaaay of in front, then suddenly back again.
My apologies if this seems a bit wordy, I'm trying to give as many details as I can, to help diagnose a cure for this.
1} - I've been getting some serious lag when I'm logging in to the game. All is well until I click the 'Accept' button on the EULA, then it can take up to 5 minutes to get into the station - It might be longer but I clicked the cancel button at 5 mins.
If I get in before 5 mins, the lag when jumping between sectors/systems is up to 2 mins, which really messes with my Escort missions.
2} - When targeting ships (Killing Spree), they'll suddenly either flick to another point in space (instantaneous) or slide extremely rapidly, if I shoot at them in their new spot, there's no damage at all until they suddenly zoom back to their original place.
If I'm escorting transport ships, they'll perform the same trait, suddenly appearing waaaaay of in front, then suddenly back again.
My apologies if this seems a bit wordy, I'm trying to give as many details as I can, to help diagnose a cure for this.
When this happens, what does the ping and traceroute from your machine to our server look like (server.vendetta-online.com) ?
Do you have any nasty bandwidth-eating programs in the background? Some Bittorrent clients in particular can make network stacks sad and add this sort of delay...
Allo again :-)
Pinging the server 3 times gave 136ms, 142 and 143 ms - Tracert gives the following....
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
>tracert server.vendetta-online.com
Tracing route to server.vendetta-online.com [204.15.102.5]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 16 ms 15 ms 15 ms host82-14-174-21.not-set-yet.ntli.net [82.14.174.21]
3 16 ms 15 ms 15 ms host82-14-173-241.not-set-yet.ntli.net [82.14.173.241]
4 23 ms * * so-2-1-0.0.sqy-cor-001.bddsl.net [83.146.19.26]
5 * 24 ms * host82-14-174-97.not-set-yet.ntli.net [82.14.174.97]
6 16 ms 23 ms 16 ms popl-core-1b-ge-410-0.network.virginmedia.net [82.14.168.129]
7 23 ms 22 ms 15 ms pop-bb-b-as2-0.network.virginmedia.net [213.105.174.238]
8 23 ms 18 ms 17 ms nth-bb-a-as1-0.network.virginmedia.net [213.105.64.17]
9 40 ms 34 ms 40 ms fran-ic-1-as0-0.network.virginmedia.net [62.253.185.81]
10 41 ms 34 ms 41 ms te8-8.mpd03.fra03.atlas.cogentco.com [130.117.14.133]
11 33 ms 34 ms 39 ms te3-7.ccr01.fra03.atlas.cogentco.com [130.117.49.169]
12 114 ms 121 ms 121 ms te2-4.ccr02.ymq02.atlas.cogentco.com [38.20.46.205]
13 129 ms 135 ms 130 ms te9-8.ccr02.ord01.atlas.cogentco.com [66.28.4.137]
14 136 ms 141 ms 135 ms te3-1.ccr01.ord04.atlas.cogentco.com [154.54.24.178]
15 142 ms 142 ms 136 ms te4-1.ccr01.mke01.atlas.cogentco.com [154.54.3.58]
16 139 ms 132 ms 132 ms 38.101.0.20
17 143 ms 137 ms 143 ms majikthise.guildsoftware.com [204.15.102.5]
Trace complete.
I'm glad that lot means something to someone lol
My connection (through 'VirginMedia') is at 8Mb/s, of which I average about 7mb/s - Upload should be 512Kb/s but I've often measured it at 800+Kb/s.
Edit: I don't have any torrents running during Vendetta, I also shut down all the background gubbins that I can, apart from AVG (A/V).
Pinging the server 3 times gave 136ms, 142 and 143 ms - Tracert gives the following....
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
>tracert server.vendetta-online.com
Tracing route to server.vendetta-online.com [204.15.102.5]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 16 ms 15 ms 15 ms host82-14-174-21.not-set-yet.ntli.net [82.14.174.21]
3 16 ms 15 ms 15 ms host82-14-173-241.not-set-yet.ntli.net [82.14.173.241]
4 23 ms * * so-2-1-0.0.sqy-cor-001.bddsl.net [83.146.19.26]
5 * 24 ms * host82-14-174-97.not-set-yet.ntli.net [82.14.174.97]
6 16 ms 23 ms 16 ms popl-core-1b-ge-410-0.network.virginmedia.net [82.14.168.129]
7 23 ms 22 ms 15 ms pop-bb-b-as2-0.network.virginmedia.net [213.105.174.238]
8 23 ms 18 ms 17 ms nth-bb-a-as1-0.network.virginmedia.net [213.105.64.17]
9 40 ms 34 ms 40 ms fran-ic-1-as0-0.network.virginmedia.net [62.253.185.81]
10 41 ms 34 ms 41 ms te8-8.mpd03.fra03.atlas.cogentco.com [130.117.14.133]
11 33 ms 34 ms 39 ms te3-7.ccr01.fra03.atlas.cogentco.com [130.117.49.169]
12 114 ms 121 ms 121 ms te2-4.ccr02.ymq02.atlas.cogentco.com [38.20.46.205]
13 129 ms 135 ms 130 ms te9-8.ccr02.ord01.atlas.cogentco.com [66.28.4.137]
14 136 ms 141 ms 135 ms te3-1.ccr01.ord04.atlas.cogentco.com [154.54.24.178]
15 142 ms 142 ms 136 ms te4-1.ccr01.mke01.atlas.cogentco.com [154.54.3.58]
16 139 ms 132 ms 132 ms 38.101.0.20
17 143 ms 137 ms 143 ms majikthise.guildsoftware.com [204.15.102.5]
Trace complete.
I'm glad that lot means something to someone lol
My connection (through 'VirginMedia') is at 8Mb/s, of which I average about 7mb/s - Upload should be 512Kb/s but I've often measured it at 800+Kb/s.
Edit: I don't have any torrents running during Vendetta, I also shut down all the background gubbins that I can, apart from AVG (A/V).
a ping under 200 should not be a problem.... packet loss?
Hmm. Try running ping for a longer period of time: ping -t
and see if there are lost packets as PaKettle suggests.
and see if there are lost packets as PaKettle suggests.
>ping -t 204.15.102.5
Pinging 204.15.102.5 with 32 bytes of data:
Reply from 204.15.102.5: bytes=32 time=137ms TTL=47
Reply from 204.15.102.5: bytes=32 time=137ms TTL=47
Reply from 204.15.102.5: bytes=32 time=143ms TTL=47
Reply from 204.15.102.5: bytes=32 time=137ms TTL=47
Reply from 204.15.102.5: bytes=32 time=143ms TTL=47
Reply from 204.15.102.5: bytes=32 time=143ms TTL=47
Reply from 204.15.102.5: bytes=32 time=137ms TTL=47
Reply from 204.15.102.5: bytes=32 time=143ms TTL=47
Reply from 204.15.102.5: bytes=32 time=137ms TTL=47
Reply from 204.15.102.5: bytes=32 time=137ms TTL=47
Reply from 204.15.102.5: bytes=32 time=143ms TTL=47
Reply from 204.15.102.5: bytes=32 time=136ms TTL=47
Reply from 204.15.102.5: bytes=32 time=143ms TTL=47
Reply from 204.15.102.5: bytes=32 time=143ms TTL=47
Reply from 204.15.102.5: bytes=32 time=137ms TTL=47
Reply from 204.15.102.5: bytes=32 time=143ms TTL=47
Reply from 204.15.102.5: bytes=32 time=137ms TTL=47
Reply from 204.15.102.5: bytes=32 time=137ms TTL=47
Reply from 204.15.102.5: bytes=32 time=142ms TTL=47
Reply from 204.15.102.5: bytes=32 time=136ms TTL=47
Reply from 204.15.102.5: bytes=32 time=144ms TTL=47
Reply from 204.15.102.5: bytes=32 time=143ms TTL=47
Reply from 204.15.102.5: bytes=32 time=136ms TTL=47
Reply from 204.15.102.5: bytes=32 time=143ms TTL=47
Reply from 204.15.102.5: bytes=32 time=137ms TTL=47
Reply from 204.15.102.5: bytes=32 time=137ms TTL=47
Reply from 204.15.102.5: bytes=32 time=143ms TTL=47
Reply from 204.15.102.5: bytes=32 time=136ms TTL=47
Reply from 204.15.102.5: bytes=32 time=143ms TTL=47
Reply from 204.15.102.5: bytes=32 time=143ms TTL=47
Reply from 204.15.102.5: bytes=32 time=136ms TTL=47
Reply from 204.15.102.5: bytes=32 time=143ms TTL=47
Reply from 204.15.102.5: bytes=32 time=137ms TTL=47
Reply from 204.15.102.5: bytes=32 time=136ms TTL=47
Reply from 204.15.102.5: bytes=32 time=143ms TTL=47
Ping statistics for 204.15.102.5:
Packets: Sent = 35, Received = 35, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 136ms, Maximum = 144ms, Average = 139ms
The server connection seems to have improved a lot this evening, but I'm still getting the odd delay when sector-warping.
The other ships are still 'blipping' about space though, could it be a graphics-card setting that I've missed? I'm using an NVidia GEForce 9800GT with 1Gb RAM.
Pinging 204.15.102.5 with 32 bytes of data:
Reply from 204.15.102.5: bytes=32 time=137ms TTL=47
Reply from 204.15.102.5: bytes=32 time=137ms TTL=47
Reply from 204.15.102.5: bytes=32 time=143ms TTL=47
Reply from 204.15.102.5: bytes=32 time=137ms TTL=47
Reply from 204.15.102.5: bytes=32 time=143ms TTL=47
Reply from 204.15.102.5: bytes=32 time=143ms TTL=47
Reply from 204.15.102.5: bytes=32 time=137ms TTL=47
Reply from 204.15.102.5: bytes=32 time=143ms TTL=47
Reply from 204.15.102.5: bytes=32 time=137ms TTL=47
Reply from 204.15.102.5: bytes=32 time=137ms TTL=47
Reply from 204.15.102.5: bytes=32 time=143ms TTL=47
Reply from 204.15.102.5: bytes=32 time=136ms TTL=47
Reply from 204.15.102.5: bytes=32 time=143ms TTL=47
Reply from 204.15.102.5: bytes=32 time=143ms TTL=47
Reply from 204.15.102.5: bytes=32 time=137ms TTL=47
Reply from 204.15.102.5: bytes=32 time=143ms TTL=47
Reply from 204.15.102.5: bytes=32 time=137ms TTL=47
Reply from 204.15.102.5: bytes=32 time=137ms TTL=47
Reply from 204.15.102.5: bytes=32 time=142ms TTL=47
Reply from 204.15.102.5: bytes=32 time=136ms TTL=47
Reply from 204.15.102.5: bytes=32 time=144ms TTL=47
Reply from 204.15.102.5: bytes=32 time=143ms TTL=47
Reply from 204.15.102.5: bytes=32 time=136ms TTL=47
Reply from 204.15.102.5: bytes=32 time=143ms TTL=47
Reply from 204.15.102.5: bytes=32 time=137ms TTL=47
Reply from 204.15.102.5: bytes=32 time=137ms TTL=47
Reply from 204.15.102.5: bytes=32 time=143ms TTL=47
Reply from 204.15.102.5: bytes=32 time=136ms TTL=47
Reply from 204.15.102.5: bytes=32 time=143ms TTL=47
Reply from 204.15.102.5: bytes=32 time=143ms TTL=47
Reply from 204.15.102.5: bytes=32 time=136ms TTL=47
Reply from 204.15.102.5: bytes=32 time=143ms TTL=47
Reply from 204.15.102.5: bytes=32 time=137ms TTL=47
Reply from 204.15.102.5: bytes=32 time=136ms TTL=47
Reply from 204.15.102.5: bytes=32 time=143ms TTL=47
Ping statistics for 204.15.102.5:
Packets: Sent = 35, Received = 35, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 136ms, Maximum = 144ms, Average = 139ms
The server connection seems to have improved a lot this evening, but I'm still getting the odd delay when sector-warping.
The other ships are still 'blipping' about space though, could it be a graphics-card setting that I've missed? I'm using an NVidia GEForce 9800GT with 1Gb RAM.
Graphics settings would cause your whole framerate to change, not just bots jumpign around. Bots jumping around is indicative of either high network latency or a lagged sector.
It seems to be fairly general in all the sectors I've been pootling/hurtling through, regardless of the number of ships or other objects 'roids - space-stations - small children etc.
I've noticed that the loading times have improved a lot and although ships are still flicking around, there's less of 'em and they're 'sliding' very fast in their direction of travel, rather than instant-jumping back and forth, as they were.
Perhaps the recent change-overs and upgrades are 'settling' down and starting to play nicely with each other :lol:
I've noticed that the loading times have improved a lot and although ships are still flicking around, there's less of 'em and they're 'sliding' very fast in their direction of travel, rather than instant-jumping back and forth, as they were.
Perhaps the recent change-overs and upgrades are 'settling' down and starting to play nicely with each other :lol:
Same "jumping" problem here, I am in Switzerland.
- EDIT: Make it both problems, for the last half an hour I keep getting to the "Getting Characters" screen, than waiting indefinitely (until the server connection times out).
It's not my connection, I can ping you just fine. OK, a lil' slow, thanks to one of the cogentco lines or routers:
(edit: had wrong trace, replaced with the correct server now)
1 2 ms 2 ms 3 ms 192.168.1.1
2 20 ms 17 ms 16 ms 213.3.80.1
3 17 ms 14 ms 14 ms 193-255-3-213.bluewin.ch [213.3.255.193]
4 16 ms 15 ms 16 ms 189-247-3-213.bluewin.ch [213.3.247.189]
5 16 ms 15 ms 15 ms 254-0-186-195.bluewin.ch [195.186.0.254]
6 17 ms 16 ms 16 ms i79zhh-015-ten1-2.bb.ip-plus.net [138.187.129.100]
7 17 ms 16 ms 16 ms i79tix-015-ten1-1.bb.ip-plus.net [138.187.129.74]
8 * * * Request Timeout
9 27 ms 25 ms 24 ms te1-2.ccr01.str01.atlas.cogentco.com [130.117.3.13]
10 25 ms 24 ms 24 ms te1-2.ccr01.fra03.atlas.cogentco.com [130.117.0.73]
11 185 ms 206 ms 204 ms te2-4.ccr02.ymq02.atlas.cogentco.com [38.20.46.205]
12 227 ms 202 ms 204 ms te9-8.ccr02.ord01.atlas.cogentco.com [66.28.4.137]
13 217 ms 204 ms 204 ms te3-1.ccr01.ord04.atlas.cogentco.com [154.54.24.178]
14 227 ms 204 ms 204 ms te4-1.ccr01.mke01.atlas.cogentco.com [154.54.3.58]
15 227 ms 204 ms 205 ms 38.101.0.20
16 227 ms 204 ms 204 ms majikthise.guildsoftware.com [204.15.102.5]
- EDIT: Make it both problems, for the last half an hour I keep getting to the "Getting Characters" screen, than waiting indefinitely (until the server connection times out).
It's not my connection, I can ping you just fine. OK, a lil' slow, thanks to one of the cogentco lines or routers:
(edit: had wrong trace, replaced with the correct server now)
1 2 ms 2 ms 3 ms 192.168.1.1
2 20 ms 17 ms 16 ms 213.3.80.1
3 17 ms 14 ms 14 ms 193-255-3-213.bluewin.ch [213.3.255.193]
4 16 ms 15 ms 16 ms 189-247-3-213.bluewin.ch [213.3.247.189]
5 16 ms 15 ms 15 ms 254-0-186-195.bluewin.ch [195.186.0.254]
6 17 ms 16 ms 16 ms i79zhh-015-ten1-2.bb.ip-plus.net [138.187.129.100]
7 17 ms 16 ms 16 ms i79tix-015-ten1-1.bb.ip-plus.net [138.187.129.74]
8 * * * Request Timeout
9 27 ms 25 ms 24 ms te1-2.ccr01.str01.atlas.cogentco.com [130.117.3.13]
10 25 ms 24 ms 24 ms te1-2.ccr01.fra03.atlas.cogentco.com [130.117.0.73]
11 185 ms 206 ms 204 ms te2-4.ccr02.ymq02.atlas.cogentco.com [38.20.46.205]
12 227 ms 202 ms 204 ms te9-8.ccr02.ord01.atlas.cogentco.com [66.28.4.137]
13 217 ms 204 ms 204 ms te3-1.ccr01.ord04.atlas.cogentco.com [154.54.24.178]
14 227 ms 204 ms 204 ms te4-1.ccr01.mke01.atlas.cogentco.com [154.54.3.58]
15 227 ms 204 ms 205 ms 38.101.0.20
16 227 ms 204 ms 204 ms majikthise.guildsoftware.com [204.15.102.5]
Sorry fro the delay in getting back, I've been upgrading my PC to Win 7.
Whatever was causing the lag has now been cured, I assume that last game-upgrade - However, the other ships still leap about space like demented crickets.
There's also another 'hiccup' with escort mission scoring, but I'll start a new thread for that one.
Whatever was causing the lag has now been cured, I assume that last game-upgrade - However, the other ships still leap about space like demented crickets.
There's also another 'hiccup' with escort mission scoring, but I'll start a new thread for that one.