You don't want to go over 100 FPS in these games because the movement changes somehow, jumping becomes floaty and it plays worse, especially in CS. What should be changed IMO is the default fps_max to 100 from 72, that seems to provide the best experience on the engine.
Also up the default rates. Players warping/lagging around with 20/30 update and cmdrates set for 1998 internet connections is just silly.
Depends. You actually shoot faster at 111 FPS, and you can actually surf faster at 130 FPS on surf_ maps.
If you set something like 400-500 FPS though, yes, your movement will be totally fucked up.
Changing the default rates might be a good idea as well though.
The default "rate" is quite low, it could be set to its maximum, "20000".
cl_updaterate, cl_cmdrate and fps_max could be set to 100.
Might change ex_interp as well to follow cl_updaterate value change.
I've already increased the default rate to 20k, but this only applies if you have not set it previously. cl_updaterate has also been increased to 40 by default (same deal on not already seeing it). I'll update fps_max to 100, that seems reasonable, these other changes seem best left to the individual user to optimize for their network setup.
Also note the new gl_vsync cvar, which is set to 1 by default, so for most users these tweaks will not be interesting. But for hardcore players they have all the flexibility they need.
Nice, thanks. Are you removing the need of developer 1 to have more than than 100 FPS and fps_modem as well?
yup, didn't make it for today's release though.
Thanks.
Does cl_rate default to 20000 as well? That command seem a bit buggy:
] cl_rate
Usage: cl_rate
Client to server transmission rate (bytes/sec)
Current: 0.00000
and if I try to set a value over 20000, it says:
cl_rate: Maximum 0.000000, Minimum 0.000000
After setting it to 20000 it tells me the current is 20000 though.
Nothing extracted yet.
This is a feature request.
It would be nice to not need to have developer set to 1 to get over 100 FPS. I guess some people have screens that are over 100 Hz.
BTW, could remove fps_modem as well (seem to be at the same place as the developer FPS cap), it's pointless to have 2 different cvars to limit the FPS.