yahooSetsulYou're a pyro main, I'm not sure if you feel anything.
Interpolation exists for a reason and you shouldn't try to disable it completely.
Anything below 15ms, which is the tickrate, can by definition not have any packet to interpolate with.
why do you so hardly believe in theory when it comes to this. in theory you should not be able to go under 15, however this game is full of bugs and broken mechanics. just test it out yourself and you can see that client side will have cl_interp value set to 0 on 0 lerp settings. cl_interp wont be set to 0 on 15 lerp settings. tickrate cant go above 66, however tickrates higher than 66 still affect cl_interp value, since cl_interp is determinated by interp_ratio/updaterate or cl_interp itself, whichever is higher.
also sick burn bro. really made u look smart.
No one ever said you can't set cl_interp to 0?
Can't do it != shouldn't do it.
You shouldn't cut off your arm but that doesn't mean you can't. It is just strongly advised against.
Tickrate is server side. You can't affect it.
You can set cl_updaterate to 10000000 which affects interp, but that still doesn't mean the server will start sending you you the 10000000 per second you need for interpolation to work. You just broke interpolation.
Why the fuck do you think cl_interp_ratio was introduced and supposed to replace cl_interp? They never bothered to implemented the last two steps.
1. remove cl_interp.
2. use the actual updaterate to calculate interp, not cl_updaterate.
That would prevent idiots from doing stupid shit they have no idea about if the server tells them they're not allowed to.