Hi Blue and every1 else.

I am having an issue with lags again same as a year ago ( old post in here http://uthgard.net/en/forum/viewtopic.php?f=15&t=25048). But this time nothing helps.

It started about month ago. Lags usually starts prime time after 6GMT. And it lags like permanently begining from yellow tringle (2 sec lag) ending up on double red square(10 sec lag/LD).

Did some lag records today to make it easier to find out what actually makes it please see below :

Was playing my rm(Rjannrm) with login: gaco1


6.01.39 PM GMT (real time) , 7.35AM ( in game time) - double red square 10 sec lag

6.02.53 PM GMT(real time) , 8.07 AM (in game time) - double red square 10 sec lag

6.04.20 PM GMT (real time) , same perma lag starting from 2secs up to 10sec

6.06.25 PM GMT (real time) , double red again


This is my CMD when double reds appeared:

C:\Users\Kuba>ping 88.198.56.21 -t

Badanie 88.198.56.21 z 32 bajtami danych:
Odpowiedź z 88.198.56.21: bajtów=32 czas=46ms TTL=116
Odpowiedź z 88.198.56.21: bajtów=32 czas=48ms TTL=116
Odpowiedź z 88.198.56.21: bajtów=32 czas=51ms TTL=116
Odpowiedź z 88.198.56.21: bajtów=32 czas=50ms TTL=116
Odpowiedź z 88.198.56.21: bajtów=32 czas=49ms TTL=116
Odpowiedź z 88.198.56.21: bajtów=32 czas=55ms TTL=116
Odpowiedź z 88.198.56.21: bajtów=32 czas=62ms TTL=116
Odpowiedź z 88.198.56.21: bajtów=32 czas=52ms TTL=116
Odpowiedź z 88.198.56.21: bajtów=32 czas=56ms TTL=116
Odpowiedź z 88.198.56.21: bajtów=32 czas=47ms TTL=116
Odpowiedź z 88.198.56.21: bajtów=32 czas=50ms TTL=116
Odpowiedź z 88.198.56.21: bajtów=32 czas=63ms TTL=116
Odpowiedź z 88.198.56.21: bajtów=32 czas=47ms TTL=116
Odpowiedź z 88.198.56.21: bajtów=32 czas=50ms TTL=116
Odpowiedź z 88.198.56.21: bajtów=32 czas=51ms TTL=116
Odpowiedź z 88.198.56.21: bajtów=32 czas=48ms TTL=116
Odpowiedź z 88.198.56.21: bajtów=32 czas=51ms TTL=116
Odpowiedź z 88.198.56.21: bajtów=32 czas=46ms TTL=116

And this is tracerout to the server since lags have started today with more then 3,5k tracerouts :


Host Name IP Address Hop Ping Time Ping Avg % Loss Pkts r/s Ping best/worst
winn-core-2b-ae7-1322.network.vir 2 9ms 13ms 0% 3577 / 3590 6ms / 83ms
brhm-bb-1c-ae2-0.network.virginme 3 16ms 19ms 0% 3581 / 3590 13ms / 115ms
nrth-bb-1c-et-400-0.network.virgi 62.253.174.226 4 15ms 19ms 0% 3585 / 3590 11ms / 117ms
nrth-tmr-1-ae1-0.network.virginme 213.105.159.30 5 16ms 21ms 0% 3577 / 3590 13ms / 205ms
fran-ic-1-as0-0.network.virginmed 62.253.185.81 6 31ms 34ms 0% 3570 / 3590 28ms / 128ms
decix-gw.hetzner.de 80.81.192.164 7 70ms 66ms 0% 3581 / 3590 41ms / 170ms
hos-bb1.juniper1.rz13.hetzner.de 213.239.240.240 8 50ms 48ms 0% 3570 / 3590 40ms / 142ms
hos-tr1.ex3k11.rz13.hetzner.de 213.239.224.12 9 90ms 67ms 0% 3569 / 3589 41ms / 168ms
uthgard.game-server.cc 88.198.56.21 10 49ms 62ms 0% 3576 / 3589 43ms / 162ms


As you can see nothing is wrong with my connection/provider , no losses and ping less then 200.

Blue as you were dealing mostly with my previous lags problem , could you check my acc logs and see whats going on? What makes the lags?

If i missed some more informations let me know and ill uptade it asap.

Thanks for your help.

More info;

Teamspeak works perfrctly during the lags, lags are not happening on any other servers.

I have very bad lag/LD problems anytime during prime time as well. Anytime there are more than around 500 players logged on the game becomes nearly unplayable for me. Any ideas how to fix it?

TheSkiesAsunder wrote:I have very bad lag/LD problems anytime during prime time as well. Anytime there are more than around 500 players logged on the game becomes nearly unplayable for me. Any ideas how to fix it?

No. Its usually unrelated to player count. We can host 1000+ players with ease.

Blue wrote:

TheSkiesAsunder wrote:I have very bad lag/LD problems anytime during prime time as well. Anytime there are more than around 500 players logged on the game becomes nearly unplayable for me. Any ideas how to fix it?

No. Its usually unrelated to player count. We can host 1000+ players with ease.

Any ideas whats going on then? Because i have had the same feeling that lags were depending on number of players ( when 800+ on server).

Are my account logs says anything?

Don't mean to intrude, however - last night I was playing perfectly fine when there was a few hundred people (I think it maxxed out at 300), however this morning - I started playing with around 780 people - a bit of latency, but nothing horrible. Once it hit 800 (or around that time) I went LD. When I re-entered the game, it said there was 816 on, played about 10 minutes, and went LD. Now there is 840, and I can only stay on for 2 or so minutes before going LD.

I hate to overstep my limits, but it would seem that there is an issue here - and after looking through other posts, most are having this issue around that amount of players - I'd also mention that the only response from moderation is that it's client side issue relating to "maintenance" from either ISP or NODES. This is unlikely.

If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a duck.

I'm sure that the server can handle upwards of 1,000+ connections (as Blue has stated elsewhere), but I have a feeling that somewhere there is a hang-up, and more than likely, with the amount of posts regarding the issue, that it has something to do with the server console dropping those connections.

Edit:
I'd also say that it obviously doesn't affect everybody, but it is affecting some, such as myself. I only add that because as I was typing this, the population continues to rise.

Same thing today. Played for a good 3 hours, then started going LD, and lo and behold, above 800 players.

Starting to record tracert/ping logs. Already have some interesting finds.

Played yesterday from 16 gmt to 19gmt and no lag at all ( around 700 players on), then had a break back on again 21gmt with 860 players on lags/ and like 5 lds between 21-22gmt. As soon as players droped below 800 after 22gmt lags were gone again.

The server has been above 1k users many times without any issue.

The likely culprit is the servers ISP and your route to it.
Unfortunately, there's not much you can do to resolve the problem. Most routing issues sort themselves out within a matter of hours. If they don't, you might be better off switching the ISP.

In my case last year, Uthgard was unreachable every hour for 10-15 minutes almost every night from 8pm-11pm CET.
It lasted for several months.
(I have Comcast in the western US)

Eh, was playing all morning, and in the last hour (when server reached 900 this time), started going LD, and now I can't even log in because of an inability connect to authentication server now.

pythion wrote:The server has been above 1k users many times without any issue.

The likely culprit is the servers ISP and your route to it.
Unfortunately, there's not much you can do to resolve the problem. Most routing issues sort themselves out within a matter of hours. If they don't, you might be better off switching the ISP.

In my case last year, Uthgard was unreachable every hour for 10-15 minutes almost every night from 8pm-11pm CET.
It lasted for several months.
(I have Comcast in the western US)

I dont think that changing internet provider will change anything as i have proved(by posting my cmd + tracerout) that during the lags in game there is nothing wrong with ping or losses.

you did the traceroute while experiencing connection issues with uthgard?

pythion wrote:you did the traceroute while experiencing connection issues with uthgard?

Check my first post in this topic maybe?:o

I am still having the same problem every time there are anywhere close to 800 players online. I can stay on for about 10-15 minutes (With terrible delay), then I go LD. After that I can load the game to character select and then onto the load screen, however, it never advances into the game again until the player count goes down. It's a shame if there is nothing can be done to change that. Don't have any of these problems on other games/servers.

There are things that can be done about it, but the staff has to acknowledge it, which they won't. So in other words, here's a shaft, shove it appropriately.

Nothing can be done. As long as not all players are affected its not server engine related.