<snip> >Is there any we can lock the FPS the server run at? You see, on 2.6.x kernels, if you put fps_max [number] the server will > run at that number so if you put fps_max 100 it'll run at 100 and you can change it on the fly. > Not, the server tries to run at fps_max, but if the CPU time isn't there then it can't.
>on 2.4.x kernels, setting -tickrate to 100, or any number, does not increase the fps. On 2.4.x kernels, setting -tickrate to >any number AND using fps_max to any number higher than 33, doesn't budge the server fps > Tickrate and FPS are independent. You need for FPS to above tickrate for it to run at tick rate however. >- How can we raise the server fps on 2.4.x kernels? I tried -tickrate 100 and fps_max 100, it says 100,but as soon as >someone joins it becomes 50, and even lower. This is a limitation of the timeslices provided by the 2.4.x scheduler (it only runs at 100Hz). Either use 2.6.x or run with 50fps for now (which is more than adequate). > >- I've found that I don't need to set -tickrate to raise the server fps on 2.6.x kernels, just fps_max - ? >Either way, alfred, how can we set it up so we can lock the fps? > No. Remember, fps max and tickrate are independent. >I tried running the startup file with +fps_max 100 or whatever, but they can always change it later. > >Could it be possible to make it so the fps_max AND -tickrate can ONLY be set with ./srcds_run and cannot be changed later >until the server restarts and ./srcds_run re-runs? > Tickrate is set at runtime, fps_max is dynamic (but only a max, not a fixed value). >-node >-- _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
