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 latter is relatively minor, a few shaders don't seem to be precompiled which causes very infrequent hitching on a first run through and the cache isn't rebuilt if you do something like reinstall the same version GPU drivers.
The former though? There's no way that didn't get caught in QA, it impacts every single hardware combination (albeit to varying degrees). Really makes me wonder what the cause is and why they weren't able to fix it prior to release.
In every instance I can think of the traversal stutters come at a point where you're seconds or more away from seeing any new assets, so why does it hold up frame generation? Do you really need to wait ~100ms to load assets that are going to be visible in 30 seconds when a player goes up an elevator?
I'd love an honest deep dive from the devs on why this issue occurred and how they fixed it (presuming they fix it). Although I doubt we'll get one.