Hi
I used to use cl_interp 0 on hitscan weapons
but after the recent updates, if i try to use cl_interp 0, it shows me this message
] cl_Interp
"cl_interp" = "0.010000" ( def. "0.1" ) min. 0.000000 max. 0.500000
** NOTE: The real value is 0.000 but the server has temporarily restricted it to 0.010 **
client archive notconnected
- Sets the interpolation amount (bounded on low side by server interp ratio settings).
{
It always restricts it to 0.01 no matter what i set the ratio to
I've searched around a lot for a solution but no-one seems to be having this problem
here are my current settings
sv_client_min_interp_ratio 0
sv_client_max_interp_ratio 2
cl_interp_ratio 1
cl_cmdrate 100 (restricted to 66 by client)
cl_updaterate 100 (restricted to 66 by client)
cl_interp 0
Hi
I used to use cl_interp 0 on hitscan weapons
but after the recent updates, if i try to use cl_interp 0, it shows me this message
] cl_Interp
"cl_interp" = "0.010000" ( def. "0.1" ) min. 0.000000 max. 0.500000
** NOTE: The real value is 0.000 but the server has temporarily restricted it to 0.010 **
client archive notconnected
- Sets the interpolation amount (bounded on low side by server interp ratio settings).
{
It always restricts it to 0.01 no matter what i set the ratio to
I've searched around a lot for a solution but no-one seems to be having this problem
here are my current settings
sv_client_min_interp_ratio 0
sv_client_max_interp_ratio 2
cl_interp_ratio 1
cl_cmdrate 100 (restricted to 66 by client)
cl_updaterate 100 (restricted to 66 by client)
cl_interp 0
Hasn't it always been like this?
Hasn't it always been like this?
shorasHasn't it always been like this?
no, before the updates I could use cl_interp 0 fine
[quote=shoras]Hasn't it always been like this?[/quote]
no, before the updates I could use cl_interp 0 fine
It has always been like this. If anything, it should be restricted to 0.015-ish, but it's not because you set your cmd and updaterate to impossible values. Either way, the engine will use the 0.015 value because of cl_interp_ratio 1.
>sv_client_min_interp_ratio 0
>sv_client_max_interp_ratio 2
These do literally nothing as a client, remove them.
The net settings you actually get (and have always gotten) with the settings you posted are these:
cl_interp_ratio 1
cl_cmdrate 66
cl_updaterate 66
cl_interp 0.015152 // rounded
If you feel a difference between these and what you're using right now, it's 100% certainly placebo.
Interp values below one updaterate frame (0.01515etc in this case) would cause extrapolation to always be occurring, so the engine, of course, forcibly limits it. If it were possible to go below one updaterate frame of interpolation, it would wreak total havoc on your hitreg.
It has always been like this. If anything, it should be restricted to 0.015-ish, but it's not because you set your cmd and updaterate to impossible values. Either way, the engine will use the 0.015 value because of cl_interp_ratio 1.
>sv_client_min_interp_ratio 0
>sv_client_max_interp_ratio 2
These do literally nothing as a client, remove them.
The net settings you actually get (and have always gotten) with the settings you posted are these:
cl_interp_ratio 1
cl_cmdrate 66
cl_updaterate 66
cl_interp 0.015152 // rounded
If you feel a difference between these and what you're using right now, it's 100% certainly placebo.
Interp values below one updaterate frame (0.01515etc in this case) would cause extrapolation to always be occurring, so the engine, of course, forcibly limits it. If it were possible to go below one updaterate frame of interpolation, it would wreak total havoc on your hitreg.
AGENT_ALPHA_Q_BOYshorasHasn't it always been like this?
no, before the updates I could use cl_interp 0 fine
I've had cl_interp 0 as well, but it hasn't ever been actually set to 0.
[quote=AGENT_ALPHA_Q_BOY][quote=shoras]Hasn't it always been like this?[/quote]
no, before the updates I could use cl_interp 0 fine[/quote]
I've had cl_interp 0 as well, but it hasn't ever been actually set to 0.
wareyaIt has always been like this. If anything, it should be restricted to 0.015-ish, but it's not because you set your cmd and updaterate to impossible values. Either way, the engine will use the 0.015 value because of cl_interp_ratio 1.
>sv_client_min_interp_ratio 0
>sv_client_max_interp_ratio 2
These do literally nothing as a client, remove them.
The net settings you actually get (and have always gotten) with the settings you posted are these:
cl_interp_ratio 1
cl_cmdrate 66
cl_updaterate 66
cl_interp 0.015152 // rounded
If you feel a difference between these and what you're using right now, it's 100% certainly placebo.
Interp values below one updaterate frame (0.01515etc in this case) would cause extrapolation to always be occurring, so the engine, of course, forcibly limits it. If it were possible to go below one updaterate frame of interpolation, it would wreak total havoc on your hitreg.
ok, thanks
[quote=wareya]It has always been like this. If anything, it should be restricted to 0.015-ish, but it's not because you set your cmd and updaterate to impossible values. Either way, the engine will use the 0.015 value because of cl_interp_ratio 1.
>sv_client_min_interp_ratio 0
>sv_client_max_interp_ratio 2
These do literally nothing as a client, remove them.
The net settings you actually get (and have always gotten) with the settings you posted are these:
cl_interp_ratio 1
cl_cmdrate 66
cl_updaterate 66
cl_interp 0.015152 // rounded
If you feel a difference between these and what you're using right now, it's 100% certainly placebo.
Interp values below one updaterate frame (0.01515etc in this case) would cause extrapolation to always be occurring, so the engine, of course, forcibly limits it. If it were possible to go below one updaterate frame of interpolation, it would wreak total havoc on your hitreg.[/quote]
ok, thanks
shorasAGENT_ALPHA_Q_BOYshorasHasn't it always been like this?
no, before the updates I could use cl_interp 0 fine
I've had cl_interp 0 as well, but it hasn't ever been actually set to 0.
well when i checked my interp before the updates it displayed it as 0
[quote=shoras][quote=AGENT_ALPHA_Q_BOY][quote=shoras]Hasn't it always been like this?[/quote]
no, before the updates I could use cl_interp 0 fine[/quote]
I've had cl_interp 0 as well, but it hasn't ever been actually set to 0.[/quote]
well when i checked my interp before the updates it displayed it as 0