Patch 7, figured I'd give it a go as there's been many patches. It still crashes very frequently. I don't have a top-notch PC but the components either match or exceed the 'recommended' settings. Seeing lots of people with 4090 also having lots of crashes.

[–] [email protected] 3 points 1 year ago (1 children)

Man, I keep hearing of the game running awful and crashing all the time, but that just was not my experience. I played it from day one. And yeah, the game did crash once and there were stutters in the wide-open areas of Koboh, but those were like half a second and while running around. My rig is no beast either, it's a 5600X and a 3070. As a general rule, at 1080p Ultra, I was getting a stable 60+ fps.

[–] Transcendant 2 points 1 year ago (1 children)

I'd be interested & grateful to know the answer to these qs, on your system... I imagine there are indeed some systems running it fine. Maybe this info can be helpful. Imo, it's a combo of a massive, beautiful game that's not been very well optimised for all PC use cases (which I accept, is a bit of a Sysphean task but other games seem to manage it).

Does your game do the 'compiling system files to improve performance' everytime you start it? I installed on my fastest m2 SSD, with that 'compiler' it takes me almost 10 mins to get into the game proper.
Do you run any overclocking software?
Did you buy the game via Steam or EA (or somewhere else)?
Which launcher do you use (I launch via Steam, going to try bypassing and launching direct from EA today)?

[–] [email protected] 2 points 1 year ago* (last edited 1 year ago) (1 children)

Yeah, it compiled system files/shaders on every launch. I'm honestly surprised they coded the game to do that instead of storing the shaders after first launch, though I suppose it's to account for newer drivers possibly changing the shader pipeline. I think I ran it off my M.2 drive, loading times to get in-game were around 5 minutes and nearly all of that was shader compile.

I haven't overclocked my CPU or GPU, but I have enabled the XMP equivalent on my RAM. That still only brings it up to 32GB@3200MHz.

Bought and launched through Steam.

And optimizing for PC is HARD. There's countless permutations of hardware. As a developer you can aim for the median configuration, the rig built of all the most common components, but what do you do when that's just not enough oomph to run the game well? Hell, there's variability even among the same components. CPUs of the same model can ramp up to higher or lower boost speeds due to minute imperfections in the silicon. Someone else, who got the same RAM sticks as I did, might find that their system becomes unstable at 3000MHz. As the components get more and more intricate, such tiny faults can have mounting effects on overall performance.

[–] Transcendant 1 points 1 year ago

Unfortunately my reply seemed to get eaten by the gremlins! Take two.

I made 4 or 5 changes at once so I'm not exactly sure which alteration fixed things for me; I saw advice on a forum post about this game crashing that said essentially, you might think you've got a stable OC, but then a game can push it and breach your 'safe' levels. I switched off my OCing, and touch wood have had no crashes since; I turned off ray tracing also, but have since turned that back on and again managed to play a complete session and exit to windows. Other things I changed, in case someone else is reading this looking for help:

manually set the page file size for the drive it's installed on (25gb)
turned off v-sync in game options, used the 'fast' setting on Nvidia Control Panel
set 'Anti-alias' to 'off' in Nvidia Control Panel

Like you say, optimising any program for PC is very difficult... so I'm always willing to give some benefit of the doubt with games that push the envelope. This has probably been the least-pro experience since the launch of No Man's Sky (which as it goes, is imo an excellent game now), AAA studios should be aiminig higher than tiny startups when it comes to stability!