The laggy common infected problem

[The Binster]

I have seen many forum posts dating all to way since 2009 until now that have this same issue with no fix.

Whenever there is a horde the zombies lag and it makes it impossible to aim at them. This only happens in multiplayer regardless of server type. The strange thing is that this happens when PING AND FPS ARE GOOD making this issue really weird.

Messing around with V-sync and multicore processing doesnt affect anything. reinstall doesnt do anything. changing priority doesnt do anything. removing mods doesnt do anything. turning off AA doesnt do anything either. reinstalling NIVIDIA gerforce drivers doesnt do anything either.

Is anyone else having this issue? and is there a fix?


ive looked at many forum posts with no answer or answer that has helped me out. some are below to show others are having this issue too.

https://steamcommunity.com/app/550/discussions/0/2592234299558409546/
https://steamcommunity.com/app/550/discussions/0/1471966894882156107/
https://www.reddit.com/r/l4d2/comments/7ko2go/laggy_stuttery_teleporting_zombies/
https://steamcommunity.com/app/550/discussions/0/1291817837615882424/
https://www.reddit.com/r/l4d2/comments/34qd5g/unfixable_strange_lag_like_thing_in_l4d2/

[Sonya]

This is probably not it, but try putting "rate 99999999" in the console.

Me and some of my friends had this problem with l4d where it set rate to something really low and it just happened out of nowhere after a fresh windows install. I never figured out why it happened, but the console command fixed it.

Edit: in the threads you linked people are suggesting fixing netcode settings as well. Such as make sure your cl_lerp is 0.1

[AustrAlien2010]

I suppose it can´t hurt to look at the server browser (may be accessible from your Steam client, by clicking on ´View´, in top menu bar, then ´Servers´), and then, on the history tab, select a server with very low latency, and see it it happens there too.

Also. You say enemies simply appear out of thin air. I remember to have seen that from time to time as well. That may happen sporadically, but not all the time.

[The Binster]

Originally posted by ♥:

This is probably not it, but try putting "rate 99999999" in the console.

Me and some of my friends had this problem with l4d where it set rate to something really low and it just happened out of nowhere after a fresh windows install. I never figured out why it happened, but the console command fixed it.

Edit: in the threads you linked people are suggesting fixing netcode settings as well. Such as make sure your cl_lerp is 0.1

OMG THANK YOU the "rate 99999999" in console did the trick. I just tested this out on survival and set the rate to 1 and got really bad common infected stutters and set it to 999999 and it did the trick.

im suprised this hasnt been said anywhere else i looked thanks.

[1986Hz]

] rate
"rate" = "30000" ( def. "10000" )
** NOTE: The real value is 9999999.000 but the server has temporarily restricted it to 30000.000 **
user
- Max bytes/sec the host can receive data

https://www.youtube.com/watch?v=xn07GeZ7Psk
Look at my NET_GRAPH in this screenshot?

https://steamcommunity.com/sharedfiles/filedetails/?id=2255514218

[Shao]

Lerp prediction was willingly set to 100.0ms to prevent commons from stuttering at the cost of accuracy because L4D2 runs at low tickrates. It refreshes your existence 10 times per 30 ticks which is generally smooth because the game doesn't have to correct itself so much. Commons should look like they are going around at 300 FPS. (Which is also the engine fps_max default, going higher would have the commons look like they stutter again.)

If you had something like 33.3ms, it would refresh 30 times per tick so every 1 tick in the 30 ticks, which is on part with pubs that run at 30 ticks, however doing it this much would make commons look like they are at 30 FPS themselves because you're not giving much headroom for the prediction to interpolate aka smooth things out. This is would be a near 100% accurate representation of the server though.

Therefor, setting 66.6ms would be much more reasonable because that'll let the game refresh twice as less (or 15 times) per 30 ticks which leaves loose 2 ticks and therefor results in 60 refreshes visually, so 60 FPS feedback.

Changing the update rate shouldn't do anything because pub servers don't go higher than 30000 anyway.

[1986Hz]

Shao that it pretty nice information you should put it into a guide on your profile