#15.2 interp or 30.3 interp

1 messages · Page 1 of 1 (latest)

solar elm
#

as a cringy chainer spy main, im tryin to determine which lerp is ultimately better and if there is even a noticable difference between both other than the compensation for dropping packets on 30.3. ik that 30.3 is overall better for gun, but im wondering if 15.2 makes a difference on knife. so i am lookin for some answers just because im curious if there is even a noticable advantage when it comes to hit registration between the 2

analog arch
#

30.3 is better with your knife as well, reasoning being the same as to why your primary is better on 30.3

#

15.2's only 100% fine if you're on LAN, where the networking conditions are perfect

#

cl_interp 0.0152: Although valid in some cases and not a misconception, it’s worth noting that this setting means you will be subject to inaccurate extrapolation which is not in line with the server’s history, all for getting lower visual latency on entity positions within a few milliseconds, which doesn’t matter when positions cannot be substantially different within that time. Instead, you will want to make sure your entity positions are at least in line with the server’s history as that is substantially more important for lag compensation and your own perception when predicting position based on velocity/trajectory. Thus, it’s recommended only for use with projectiles and not hitscan, and only if you have a stable enough connection to support it.
https://docs.mastercomfig.com/latest/tf2/misconceptions/#bad-cvars

vapid sparrow
#

the way i understand it, all hitscan (which includes melee) takes into account your interp settings, so higher interp values work well with them

toxic hollow
#

Yeah, the extra latency that comes with higher interp is not at all a detriment to hit-reg.

solar elm
#

alright sick i might try 30.3. what exactly are mcoms's recommended network settings for 30.3 lerp?

analog arch
#

if you're using mastercomfig it should set it automatically (unless you have settings overriding it)

#

if not, then use mastercomfig :)

#

(cl_interp .03;cl_interp_ratio 2;cl_pred_optimize 1 for spy)