"Marusia" - feedback please

I average a ping of 60-80 on the new server which is truly annoying. (Had half of that on the old one)

I average a ping of 60-80 on the new server which is truly annoying. (Had half of that on the old one)

But do you experience a lot of lag?

I average a ping of 60-80 on the new server which is truly annoying. (Had half of that on the old one)

But do you experience a lot of lag?

I do experience a lot of lag. However they aren't huge lagspikes, I constantly experience packet loss resulting in models skipping from one position to another or simply disappearing completely for a split second. It's like playing on an australian server. What makes it even worse is that I'm mainly a sniper

I average a ping of 60-80 on the new server which is truly annoying. (Had half of that on the old one)

But do you experience a lot of lag?

I do experience a lot of lag. However they aren't huge lagspikes, I constantly experience packet loss resulting in models skipping from one position to another or simply disappearing completely for a split second. It's like playing on an australian server. What makes it even worse is that I'm mainly a sniper

Can you do this:
start -> run -> cmd

type in tracert marusia.aprilon.net then copy/paste the result here.

And if you can, also a picture of your network graph while playing on the server? net_graph 4 in console.

Dont ask me why there seem to be two command prompts. "Zeitüberschreitung der Anforderung." basically means I didnt receive any packets I think.

http://rapidshare.com/files/406895600/tf2.zip <- screenshots of netgraph

Sadly I dont know how to change the capturing from .tga to .jpg :/ Basically the actual graph spiked heavily when engaging in combat (Note that it was the last checkpoint so pretty much everyone was there. Ping averaged between 70 and 85.

Ironically I didnt experience any major lag though. I think it has to do with the amount of players on the server (24 that session; gets really bad if its 28 upwards). The map was pl_upward

That's a really odd traceroute.
Also, yeah, 32-slot servers are known to be a little laggy, they won't be 100% stable (it's probably impossible), since Valve tested and optimized this game for 24 players.

Karl could you please config back hlstatsx that when you die, it says how many points you lost
I hate doing /2 math every time i die, TY.

The only time I experienced latency lag or warping was on pl_upwards, not bad though, only happend once for a couple of seconds and vanished as quickly as it came.

Karl could you please config back hlstatsx that when you die, it says how many points you lost
I hate doing /2 math every time i die, TY.

Doesn't it do this already?

Ok thanks for the reports, it makes sense now.

No it only shows how much points the killer got

No it only shows how much points the killer got

well I haven't changed anything, there's nothing to "configure back".

No it only shows how much points the killer got

well I haven't changed anything, there's nothing to "configure back".

Configure forward then lol

Like i said it only shows points that killer got without -%number% so i have to do the math every time i die

I wish I could try this stuff

This is our whole machine, and it's not a fast decision, we've used this company before.
I can't believe you imply this server sucks and we need to get another one that's better?

"]

Please note that I am happy with the new server, I'm just not convinced yet.


I do not think the server sucks. I only said that it would require more testing, which is not a crazy thing to say when I've only played 1 or 2 days at the server.

New one seemed good to me for the session i had today

There is a possibility that we'll move again to a server in the Netherlands. We got a good offer. We'll be able to host more servers.

I'd like you all to ping and traceroute the IP 87.238.173.154 and post the results here

If you don't know how (for Windows):
Start -> Run: cmd -> type in 'ping 87.238.173.154'
Start -> Run: cmd -> type in 'tracert 87.238.173.154'

Thanks

Pinging 87.238.173.154 with 32 bytes of data:
Reply from 87.238.173.154: bytes=32 time=142ms TTL=54
Reply from 87.238.173.154: bytes=32 time=140ms TTL=54
Reply from 87.238.173.154: bytes=32 time=141ms TTL=54
Reply from 87.238.173.154: bytes=32 time=141ms TTL=54

Ping statistics for 87.238.173.154:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 140ms, Maximum = 142ms, Average = 141ms






Tracing route to colo.hosting-ict.net
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 17 ms 15 ms 17 ms
3 16 ms 15 ms 15 ms 85.114.32.41
4 15 ms 15 ms 35 ms 85.114.32.41
5 23 ms 23 ms 23 ms gi9-15.ccr01.vie01.atlas.cogentco.com
6 31 ms 30 ms 31 ms te0-0-0-6.ccr22.muc01.atlas.cogentco.com
7 35 ms 36 ms 36 ms te0-2-0-2.ccr22.fra03.atlas.cogentco.com
8 45 ms 45 ms 46 ms te0-2-0-2.ccr22.par01.atlas.cogentco.com
9 127 ms 126 ms 128 ms te0-3-0-2.ccr22.jfk02.atlas.cogentco.com
10 132 ms 131 ms 131 ms te7-1.ccr01.jfk07.atlas.cogentco.com
11 126 ms 125 ms 126 ms gblx.jfk07.atlas.cogentco.com
12 140 ms 140 ms 140 ms DUOCAST.gigabitethernet3-1.ar4.AMS2.gblx.net
13 142 ms 141 ms 140 ms colo.hosting-ict.net

Pinging 87.238.173.15 with 32 bytes of data:
Reply from 87.238.173.15: bytes=32 time=124ms TTL=52
Reply from 87.238.173.15: bytes=32 time=122ms TTL=52
Reply from 87.238.173.15: bytes=32 time=122ms TTL=52
Reply from 87.238.173.15: bytes=32 time=119ms TTL=52

Ping statistics for 87.238.173.15:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 119ms, Maximum = 124ms, Average = 121ms

Tracing route to 87.238.173.154 over a maximum of 30 hops

1 1 ms 1 ms <1 ms 192.168.1.1
2 14 ms 11 ms 9 ms 10.60.96.1
3 13 ms 26 ms 16 ms 172.30.28.145
4 23 ms 24 ms 23 ms 12-215-0-26.client.mchsi.com
5 20 ms 20 ms 20 ms cr83.attga.ip.att.net
6 23 ms 20 ms 24 ms cr1.attga.ip.att.net
7 23 ms 20 ms 19 ms attga01jt.ip.att.net
8 21 ms 24 ms 21 ms 192.205.37.82
9 131 ms 123 ms 121 ms DUOCAST.gigabitethernet3-1.ar4.AMS2.gblx.net
10 187 ms 196 ms 203 ms 87.238.173.154

Trace complete.

Pinging 87.238.173.154 with 32 bytes of data:

Reply from 87.238.173.154: bytes=32 time=18ms TTL=59
Reply from 87.238.173.154: bytes=32 time=18ms TTL=59
Reply from 87.238.173.154: bytes=32 time=18ms TTL=59
Reply from 87.238.173.154: bytes=32 time=19ms TTL=59

Ping statistics for 87.238.173.154:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 19ms, Average = 18ms


Tracing route to 87.238.173.154 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 32 ms 26 ms 19 ms 195.190.242.4
3 19 ms 18 ms 19 ms 42.ge-2-1-0.xr4.1d12.xs4all.net

4 18 ms 18 ms 134 ms 42.ge-2-1-0.xr4.1d12.xs4all.net

5 18 ms 26 ms 116 ms 0.so-6-0-0.xr1.tc2.xs4all.net
6 18 ms 18 ms 22 ms ams-ix.gs.ams.duocast.net
7 18 ms 19 ms 19 ms 87.238.173.154

Trace complete.