Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I've given up trying to figure out the exact mechanic behind it, it's just one in a long line of bugs that seemingly never get fixed. For me it's only a thing on L4D1 maps, L4D2 maps all seem to work fine.
As a bonus, it often gets worse when you fire your gun, especially SMGs.
For some, it seems this problem only started relatively recently, due to either:
1) New updates to the game. Quite possible, because after the TLS update the CI on l4d1 maps were changed back to old l4d1 style CI, could be that. They also added and tweaked some animations (like the crappy looking recoil animation), could be that too.
2) New OS. Could be. Who knows.
3) New drivers. Also a very likely candidate. It's an old game and new drivers can sometimes switch to do old things in new ways, which added to the layers of abstraction with game + driver + gpu -> screen output can give any number of weird behaviours.
Wish I could be of more help, but that's all I've got atm.