6.5.0-b7 https://github.com/mastercoms/mastercomfig/releases/tag/6.5.0-b7
pancake_stacksIs there a reason why cl_cmdrate and cl_updaterate are set to 66? I know vast majority of servers are 66 tick, but is there any downside to setting them higher than what the servers tick rate is? I've seen some 128 tick servers, so wouldn't it just be best to set cl_cmdrate and updaterate to 128 and let the server enforce/lock you to their max? Or does it mess with the hitreg having different update/cmdrate higher than the tickrate?
It's really hard to grasp all these networking commands, as I'm no networking engineer. I wish Valve would put out detailed information on this stuff, as there are just too many people with varying opinions on what does what, and what's best for hit reg. There's almost no way to test this stuff because it's all subjective due to no proper way to test, outside of cl_interp, which is very easy to see the difference using hitbox outlines.
I've seen 133 tick servers, not 128. If those commands are set too high, client side, lerp is shown inaccurately and may confuse people.
bassroytJust out of curiosity, is there no more progress left to be done for the Max Quality preset? Or does the
comfig help improve the Max Quality to be more stable each time you update it?
Like all presets, max quality builds off of comfig so any updates to comfig will affect max quality.