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
For points of references, I've seen 12th and 13th gen Intel's get this done in about 15-30 minutes.
My 5800X Ryzen 7 got it done in about 25 minutes.
Anything pre-9th gen Intel is gonna just slug ass through these. Even the 9th gen will be slow with it.
The shader compilation is a multi-threaded, all-core type of processing request your CPU does and it's most efficient with proper multi-threaded CPUs (hyperthreading on Intel which don't show up until much more recent generations compared to AMD's CPUs).
I think it depend where the game is installed.
Nvme = 15 min more or less
sata ssd : probably 20-30
hdd : probably 1 hour or more.
I have no reason to lie.
i think many players had shader comp in 15-20 min, just they are not the one who complain on the forum, so they are not the one you'll see there.
rtx2070super / 32 Go Ram / win10
errrm my mistake, after checking it's a i79700K not 9600K (8 cores, not 6)
I approximate mine having taken 25 minutes cause I rolled a joint and went and smoked it and a cig before coming back about 25 minutes later and it was done. I know it did take more than 15 minutes for me because I did check on my CPU temp and the progress between the joint and the cig, but coming back after the cig was about 8 minutes later and it was done. The last 30% zipped by for me.
Let enjoy a cpu at 100% for approximately 1 hour, non-stop. If the cpu resists, then you can enjoy the crashes.
As a detail, a bit of stuttering and bugs to make this port the biggest garbage and win the award for the worst port in history.
For the players. Great, great sony.
But my crashes were related to my GPU being overclocked. Disabled the OC and the crashing stopped. I got game engine crash reports with those crashes.
I tried to OC my GPU to get around potential vRAM spillover and that did help with that. But I wasn't even having performance spikes to begin with before so it was mostly wasted use of OC to get the odd artifacting and a few game crashes for this game. I'll stick with the rare 1% low for me on my system.
But the crashes are definitely there. There's more than just OC related crashes as well. Just haven't had the luck of experiencing any of these ones myself. But the crashes seem to be a lot more common in the later scenes in the game that get a fair bit more demanding.
R7 3800X, RX6800, 32GB, win 11 22h2
ram usage22GB/12GB vram, swap file was utilised by around 700MB
https://youtu.be/1bjX7wsPkDA