[coolzie]

Hello,

Setting sv_competitive_minspec 1 on my CSS server actually forces fps_max to 59 rather than forcing a minimum of 59. When I join my server with fps_max 0 or fps_max 300 (etc), I end up with fps being locked at 59. Is sv_competitive_minspec broken? Or is there possibly another command on my server interfering?

"sv_competitive_minspec" = "1"
game notify replicated
- Enable to force certain client convars to minimum/maximum values to help prevent competitive advantages:
r_drawdetailprops = 1
r_staticprop_lod = minimum -1 maximum 3
fps_max minimum 59 (0 works too)
cl_detailfade minimum 400
cl_detaildist minimum 1200
cl_interp_ratio = minimum 1 maximum 2
cl_interp = minimum 0 maximum 0.031

Thank you.

[DarkDeviL]

Since you found out it is an issue with your computer, please follow the AlliedModders Rules and share the solution for future readers.

[coolzie]

<sarcasm>Receiving a warning is a real motivator to come and post again.</sarcasm>

Anyways, the issue happens when you have fps_max 0 in your autoexec.cfg file. You need to set an actual limit, and oddly enough, leaving the server to set a limit doesn't work. The game needs to be relaunched with the value changed in your autoexec.cfg file. So Valve's "0 works too" is not true.

This is in regards to CSS, I have not tested it in CSGO (it's probably fixed).