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
12900kf 5.2 ghz (OC)
32 gb DDR 5
NVME.2 SSD 4th gen
1440p, cinematic quality, ray tracing on max, Vsync on (so 60) game stays at 60 for the most part, but have seen it dip down to 55 or so. I did have a cutscene in act 4 where it dropped to 37 for the entire thing, which was odd, because when I gained control, it went right back to where it was supposed to be. Usage sits at around 72% the entire way through, while CPU lingers at around 52%.
Game is very demanding, if you dont want FG on, you definitely need to lower settings and Raytracing.
That being said, I have had rare occasions where the game seemingly chokes on something and performance literally slideshows for a few seconds. When that happens I hit pause, wait for it to 'catch up'... then unpause and its back to normal. I've had this happen maybe 3 times or so only so its not that often.
Try the following:
1. Disable Cuda System Fallback in your nVidia controlpanel
2. Increase your pagefile.sys to the amount of your physical DDR5
3. refresh ALL your vc_redist
https://www.techpowerup.com/download/visual-c-redistributable-runtime-package-all-in-one/
- Garbage collection during world traversal when leaving/approaching/entering new-level areas.
- Assets & texture streaming during world traversal when leaving/approaching/entering new level areas.
- Remanent/pending (if a shader pre-compilation process is built-in) shader compilation workloads on the fly during gameplay, when triggering some game events/cinematics, loading new levels, or during world traversal when leaving/approaching/entering new level areas.
Unfortunately, many studios don't tweak or customize the engine source code (this requires hiring specialized and expert C++ engineers) to adapt it to their game project needs, and this is mostly mandatory when making large-instanced and sized semi-open or open-world games using Unreal Engine, if you don't want to have to deal with these issues.
Keep playing it and you will see. The game is good despite some technical flaws (nothing that ruins it), but you will likely notice the same issue later on in some situations and locations. What you experienced is due to reasons I explained and listed in my previous comment. Only the devs can resolve or mitigate it and optimize it.
Sadly, there is no sign of ongoing post-launch game support, as you can monitor from here: https://steamdb.info/app/2358720/depots/