Thank you very much for the tip. It stabilized framerates nicely on both hlds and srcds, and significantly reduced cpu load on hlds. I'm quite pleased.
(And I have now figured out why I couldn't post to the mailing list, so I won't be hijacking anymore threads... ;) Drek Erik Southworth wrote: > On Sun, Sep 21, 2008 at 1:26 PM, Crazy Canucks <[EMAIL PROTECTED]>wrote: > > >> Ok, here is what I've figured out: >> >> 1. The command line option "-tickrate x" for srcds does not correlate >> to server fps, "+fps_max x" regulates that. I'm still not sure what the >> difference is between tickrate and server fps is for srcds. >> >> 2. The server.cfg cvar, "sys_ticrate x" for hlds does roughly correlate >> to server fps. There is no fps_max option or cvar for hlds. There is >> however, an unrelated client cvar "fps_max x". >> >> I am however trying something different. I've decided to make the >> tickrate, sys_ticrate and fps_max all multiples of sv_maxupdaterate. I >> will see if that affects performance in any way. (I have funky rate >> settings due to the fact that I run a bandwidth challenged server on a >> business cable connection.) >> >> Drek >> >> Gary Stanley wrote: >> >>> At 11:18 AM 9/21/2008, Crazy Canucks wrote: >>> >>> >>>> I am running a 1000hz, low latency kernel. I have my -ticrate (command >>>> line option) set to 66 on my DOD: Source server. I thought that ticrate >>>> basically governed server fps, but when I run the "stats" command in the >>>> console, I see that my server is running at around 200 fps. >>>> >>>> >>> Server FPS is measured by doing 2 gettimeofday() calls and doing some >>> math.. (subtracting both values for the nsec field?) >>> Anyways, most of the time what the server's FPS shows is how much >>> granularity HZ on the system is, or how accurate gettimeofday() is >>> going to be.. >>> If you only want the server to run at 66hz, just, well, lower HZ to >>> about 100 :) >>> >>> >>> >>>> This doesn't appear to be a problem, I haven't noticed any excessive cpu >>>> load issues, however, I like to know what is going on and how things >>>> work, in case I do need to make adjustments. Why is my server running >>>> at 200 and not 66 fps? >>>> >>>> >>> +fps_max 66? >>> >>> >>> >>> _______________________________________________ >>> To unsubscribe, edit your list preferences, or view the list archives, >>> >> please visit: >> >>> http://list.valvesoftware.com/mailman/listinfo/hlds_linux >>> >>> >>> >> _______________________________________________ >> To unsubscribe, edit your list preferences, or view the list archives, >> please visit: >> http://list.valvesoftware.com/mailman/listinfo/hlds_linux >> >> > > You should read: > http://developer.valvesoftware.com/wiki/Source_Multiplayer_Networking > The relationships are complex and easy to confuse. > > In general tickrate does not equate with fps. > > I recommend for your box set tickrate at 66 and unlock framerate 'fps_max > 0'. > Then tweak your rates accordingly. > > If you want experiment the effects of a single framerate try i.e. > 'host_framerate 100'. //Set to lock per-frame time elapse. Must not to > exceed servers ability to render frames. > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, please > visit: > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > > _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
