Tick Rate...

[pooty]

So with the move to 64-bit it seems we can up the tick rate.... old server was at 30, we are now at 70.

https://wiki.unrealadmin.org/Netspeed_Tutorial_(UT)

But per Snarf:

Unrelated, I noticed at 70 tick last night we were pushing 95kbs from the server. Thank god for bandwidth fix, but also setting MaxClientRate=100000 might not be enough. We might need 200000 if we increase tick rate further.

Without our bandwidth removal mod, we can increase the netspeed. (100 is 100 KB/s, so for 32 players = 3.2 MB/s (Bytes, not bits) Not exactly burning up the network pipe. Even at 200K is 6.4 MB/s (51 Mbits/s) (which back in the day would have been unthinkable, but now with most servers on 10+ Gigabit networks not a big deal). For each person, 200 Kb/s is only 1.6 Mb so those of you still on AOL or Compuserve need to upgrade...and/or stop your continuous OnlyFans streaming....

All that being said, do we need more than 70 ticks?

[Anonymous.]

The cap should definitely be raised, 100k isn't enough anymore. It looks like the default is 80k which should also be raised.

I think 70 tick is good enough, but I'm not opposed to more if the CPU can handle it.

[pooty]

Current tick rate is now at 50, up a bit from 40.

Lets see how it goes, its probably a bit too high with 24+ players, but we only get a full server once in a while.

[Super Sanka]

I didn't see any performance issues or lag events with 50 ticks.

[pooty]

Harbor lagged a bit, but that might be the map vs. server.

[Enyo]

Harbor lagged a bit, but that might be the map vs. server.

Only map that lagged all night for me. FPS drop to less than half.

[Anonymous.]

It's the map, the tick rate doesn't have that kind of impact on client FPS.

[pooty]

It can though depending... I've seen it drop with vehicles, especially if they have heavy Tick() function and certain emitters/ dynamic light.

Based on the other thread its too many triangles in the meshes on that map.