05-02-2010, 09:39 PM
ehm, the concept of server fps has been "invented" in the QuakeWorld engine. And if you call it HZ step or frame does not change anything. As far as I know there is no better concept than doing all calculations in regular time intervals and sleep in between to give other processes, drivers, etc. cpu time.
If I could change the engine I would change something else: currently the engine estimates the latency and puts the client commands into the command queue shifted by that amount of time into the past, to correct for the latency. much better would be to use a global tick number and let the clients tag their commands with the tick number to which they belong. That way the precise latency would no longer play any role, the server could put the commands into the queue at the right point in time without any uncertainties from latency estimation. Maybe this would open some additional doors for cheaters, but there are so many ways to cheat that this simply would not matter (at least if some cross checks are done with the estimated latency). the concept of fps would remain but it would no longer be important to have high fps. fps equal the tickrate would be perfectly fine. (at the moment it's not, because it introduces an additional uncertainty of 10ms for the ping - even if you, Monk, still neglect this, it's there!)
If I could change the engine I would change something else: currently the engine estimates the latency and puts the client commands into the command queue shifted by that amount of time into the past, to correct for the latency. much better would be to use a global tick number and let the clients tag their commands with the tick number to which they belong. That way the precise latency would no longer play any role, the server could put the commands into the queue at the right point in time without any uncertainties from latency estimation. Maybe this would open some additional doors for cheaters, but there are so many ways to cheat that this simply would not matter (at least if some cross checks are done with the estimated latency). the concept of fps would remain but it would no longer be important to have high fps. fps equal the tickrate would be perfectly fine. (at the moment it's not, because it introduces an additional uncertainty of 10ms for the ping - even if you, Monk, still neglect this, it's there!)
http://www.fpsmeter.org
http://wiki.fragaholics.de/index.php/EN:Linux_Optimization_Guide (Linux Kernel HOWTO!)
Do not ask technical questions via PM!
http://wiki.fragaholics.de/index.php/EN:Linux_Optimization_Guide (Linux Kernel HOWTO!)
Do not ask technical questions via PM!