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
The reason you're having those issues is due to the dynamic occlusion methods, wherein objects that are completely obstructed by other objects are forcibly unrendered. There's also "frustrum occlusion", which culls objects out that are not currently in your FOV. These sorts of system is normally fine in practice, however they are very CPU intensive when there are MANY objects to render/unrender at once. This can start to cause hitches on some CPUs. If you've ever noticed you hitch more when you're moving fast / turning fast, this would be the explanation. Hellmark in this case, has over 25k StaticMeshes, which is A LOT for one map. The detailing is pretty dense as well. This is especially true for the second area you described.
And then there was that one area with the bar shops that had the cage and the fire underneath; your framerate would drop quite a bit if you walked through there. Same goes for the train station area if you're on the overpass.