The default is 300 on Orange Box. You can see this by typing "fps_max" in the server console.

On 8/7/2011 1:00 PM, Marco Padovan wrote:
What's currently the default fps_max value if not forced via command line?

66.67?

btw I was just reporting a problem that happens only when using specific
frame rates (333=bad, 300=ok, 500=ok) that COULD lead to similar
problems if the bug is ported also to the other "base" rate (66.66)...

I do not care if 66 is the best or of 300 is the worst... I'm just
reporting what I think could be something wrong...

Nobody confirm the problem?

It appear to be identical to the one that happened a few weeks ago with
the FPS limiter (in the case the problem was present on many more fps
values)...

Il 07/08/2011 18:06, Saul Rennison ha scritto:
I hope you understand that the world is only simulated every tick, and ticks
occur in suitable frames. A frame where a tick doesn't run is a waste of
power (at least server side).

In what way is he wrong?

On Sunday, 7 August 2011, Björn Rohlén<bjorn.roh...@gmail.com>  wrote:
This is server fps, which has to do with ticks and rates in worldstates,
and
you are also wrong, but that is another story.

-TheG

On Sun, Aug 7, 2011 at 3:13 PM, Michael Johansen<michs...@live.no>  wrote:

Just thought i'd share something. Running with high fps doesn't do
anything
positive. fps_max 66.67 is enough and it is the best (if it is stable)

Date: Sun, 7 Aug 2011 08:57:43 +0200
From: e...@evcz.tk
To: hlds_linux@list.valvesoftware.com
Subject: Re: [hlds_linux] fps_max 333 = high cpu usage

This is the Linux server list... my pc is powerful enough but don't
know
who cares about how fast is my PC as I do not play TF2...
I just run servers on servers boxes.

Il 07/08/2011 05:55, Bruno Garcia ha scritto:
I'd advice you if you don't know about the subject remove the fps_max
flag,
as it will play against you.
Also, 333 isn't a good number. Try using fps_max 100 instead, it's
better if
you have a slower PC.

On Sat, Aug 6, 2011 at 5:42 PM, Marco Padovan<e...@evcz.tk>  wrote:

Something is still broken into the fps limiter:

while having the fps_max set to 300 cpu load while the server is
empty
is
ok

with fps_max set to 333 cpu load stay high (same as when the server
is
full) even with empty servers

fps_max set to 0 (resulting costantly within the 497.30 ~ 497.70 fps
range) cpu usage is nearly zero when the server is empty.
_______________________________________________
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
_______________________________________________
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

_______________________________________________
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


_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds_linux

Reply via email to