10 replies to this topic

[capnjosh]

I've been doing some reading, talking, and data-staring on the topic of server tick rates.  In our player base, more than have of our users get above 60 frames per second.  That means they could technically experience a slightly more fluid play experience with tick rates higher than the default 30 per second.  Realistically, most people will not notice any difference, especially new users.  It's only with high levels of skill and experience that these things will be detectable.  And, yes, I know this is great, endless debate fodder ;)

 

There is a pretty substantial load on servers when running at higher tick rates, so there is a very real additional cost overhead.  It's just something to consider.  As to going with very high server tick rates, e.g. 128 per second or even more, it's possible, but it would take some dev/hosting investment, since at the moment an entire host machine will run all game servers at the same tick rate.  I think I'll just make it an option we'll roll out for the Private Servers at some point.  I'm going to leave the game servers as they are for the time being, at least in terms of tick rate configs.

 

With the Pioneer Private Server event largely rolled out, a side benefit is that we have completed a very good pass on improving the hosting systems.  We've worked with nearly all the related code, databases, and deployment infrastructure.  We've got all code source-controlled and in a stable state, so most everything is very re-deployable.

 

Up next is a sprint aimed at tuning some Matchmaker configs.  I'll post about that very soon.

 

[hestoned]

I'm getting higher tick rate as soon as you make it available cap

[crockrocket]

Fairly certain my internet can't handle the high tick servers. 66t has been absolutely unplayable for me.

[CraftyDus]

offering higher tick (even ~60) for private servers will ensure they are an attractive purchase

[Loglino]

I can't wait to see what you'll do with matchmaking, because it obviously could use a few tweaks.

[MacTep_6oT]

fps in garage idling 122-149. ingame 47-89, depending on map, player population (highest fps ingame is DM), and moon phase.

[brackets]

If I get substantially less than 60 fps and I join a 66t server, will I be at a disadvantage compared to if I join a 30t server?

[comic_sans]

So are there plans of upgrading to 66 tick for all servers at some point at all?  Gotta admit, having a taste of all my shots existing has been glorious and I definitely prioritize the 66 tick servers heavily over others.

[Nept]

So I finally got on a 66 tickrate Ashburn server.  Difference was night and day: not only was my ping 80-88 (compared to my regular 100-110 East), but everything felt much more snappy and smooth.  Spent a game missing half my shots before realizing that I didn't have to lead a country mile.

[CraftyDus]

If I get substantially less than 60 fps and I join a 66t server, will I be at a disadvantage compared to if I join a 30t server?

 

None what-so-ever

It is always more desirable to have servers update the game enviroment as much and as quickly as is allowable

It is never a disadvantage, you are always better off

 

To say that a higher tickrate is "unplayable" over one with less than half the tickrate is absurd

It is better in any way that can be measured

 

Lemme know when 128 tick becomes available, I'll take a half dozen of those servers tyvm

Edited by Dustin, 06 May 2015 - 11:00 AM.

[IareDave]

So I finally got on a 66 tickrate Ashburn server. Difference was night and day: not only was my ping 80-88 (compared to my regular 100-110 East), but everything felt much more snappy and smooth. Spent a game missing half my shots before realizing that I didn't have to lead a country mile.

'Twas my first time in that USE 66t and the gameplay felt amazing. Hit reg was improved, and the gameplay just felt a notch faster - though that could of been a result of far too much caffeine.

Edited by IareDave, 06 May 2015 - 04:58 PM.