game crashes after the relic update

[Towhard]

my game ccrashes after the relic update on startup. verified files, re installed .. everything i can think of. game tries to start but just exits out. no error or anything

[smurfy]

Fraqment a écrit :

trillytroy a écrit :

huh?

I had 2 patches in the last few days totaling 80gb that were certainly the biggest patches I got until today and on the day next to another patch one with 5.3 gb and when I started the game everything worked.

Are you running the Experimental build?

Experimental Branch 28/03

• Fixed an issue that could block interaction with Galactic Palaeology Society representatives at dig sites during the Relics expedition.
  
• Fixed a graphics driver related crash.

[Fraqment]

My impression was rather that they were NVIDIA cards, I myself still run an older AMD graphics card.
But most people don't describe what CPU or graphics cards they have installed in their system.

[daboss]

day 3 and still no fix still waiting so sad

[PersonalC0ffee]

Fraqment a écrit :

My impression was rather that they were NVIDIA cards, I myself still run an older AMD graphics card.
But most people don't describe what CPU or graphics cards they have installed in their system.

RTX 3080 10gb with a i7 7700k. No crashing, just major hang of 2-5 minutes on start up but it does start.

[doctor.molotov17]

same

[player144]

When start the game, i get the Hello Games logo, then the screen with Havok/Wwise. Music also works, and then i get an error with this code which is copied onto clipboard, then CTD.

141248_0x13020_ST76561198096236071

[Cordial]

As of the last couple days, I've been fortunate to have not run into this issue.

I was able to play just yesterday, yet this morning, I ran into the same game crash just as soon as you try launching *any* save file as described by many others above. This is accompanied by an error code thankfully, but the issue would render the game entirely unplayable, aside from the main menu and option screen.

Closing and relaunching the game, nor did verifying integrity of files work, but a much simpler resolution proved to do the trick. Try restarting your system if you haven't already, as it evidently had refreshed what it needed to in NMS to allow the game to work again.

Hope you guys are able to find a resolution.

[peterba1983]

still not working after new update

[peterba1983]

player144 a écrit :

When start the game, i get the Hello Games logo, then the screen with Havok/Wwise. Music also works, and then i get an error with this code which is copied onto clipboard, then CTD.

141248_0x13020_ST76561198096236071

i have this problem too onli diferent numbers

[pirateguillermo]

I get crashes all the time, now, post-update. I've seen this before. It's frustrating, but it seems to be happening to me right around autosave. Like, the autosave happens (I exit my ship) and start going somewhere and then bang.

[Floid]

It still surprises me that people expect the game to work around the time of expedition releases lol - the game is not going to work during these periods. It's like this with every expedition release.

However that said - it dose not mean that as a member of the NMS community / player base you should just ignore NMS when expeditions release. The least / only thing you can do, is just boot up the game, note down the inevitable error code number, and pop it off to zendesk. Then hope it gets patched.

It's best to think of NMS as a pseudo-live service game. You have to understand that HG is / and will continue to "break" the game a little more and more with each update, until eventually no one can play it at all :)

[Towhard]

Floid a écrit :

It still surprises me that people expect the game to work around the time of expedition releases lol - the game is not going to work during these periods. It's like this with every expedition release.

However that said - it dose not mean that as a member of the NMS community / player base you should just ignore NMS when expeditions release. The least / only thing you can do, is just boot up the game, note down the inevitable error code number, and pop it off to zendesk. Then hope it gets patched.

It's best to think of NMS as a pseudo-live service game. You have to understand that HG is / and will continue to "break" the game a little more and more with each update, until eventually no one can play it at all :)

theres plenty that can play the game fine, but theres a large group of ppl who cannot, and what im sure isnt a hard fix just hasnt been done, they have focused on the other things. the game wont even start up for many people

[Floid]

Towhard a écrit :

...the game wont even start up for many people

Yeah in those situations, that is the worst I would say.
If the game won't even give you a crash report or an error code to pass onto HG - then yes, that's when it is justifiable for your focus to shift to more of an approach with HG.

( ps - obviously before you do that, you should just make sure it's not an addressable problem on your side first, like hardware or software enforcement, and once you've eliminated those variables, then move onto more of an approach with HG. )

[Towhard]

Floid a écrit :

Towhard a écrit :

...the game wont even start up for many people

Yeah in those situations, that is the worst I would say.
If the game won't even give you a crash report or an error code to pass onto HG - then yes, that's when it is justifiable for your focus to shift to a more disruptive approach.

thats exactly whats happening to most, not even an error

[smurfy]

I am frankly astounded that you have been able to use an AMD R9 GPU for the last couple of years, let alone the last couple of weeks.
It is well into Legacy driver support by AMD (Adrenaline 21.5.2 was released 2021-06-21) and does not support Vulkan 1.3, let alone the Vulkan 1.4 API that NMS now uses.
The Steam Store page published minimum requirements have stated it needs an RX480 at least for the last year.

I don't think you should be holding your breath for HG to fix your issue.

Note: I am not trying to be critical of your hardware choice. I am an AMD fan and used an R9 280 and a PhenomII back in 2016 when we first started playing NMS and had to implement a manual workaround while hoping/waiting for a patch to make the PhenomII compatible.
I just doubt there will be any official support to back-date hardware support for GPUs that clearly don't meet the minimum and don't support the newer features being added to the game. That old CPU still runs the game, but the R9 has been long retired and replaced with a 2nd hand GTX1060.

You may have to "jump through some hoops" as you put it to make your dinosaur work.
Try disabling the game's version of vulkan dll which will force your system to try to use the Windows\System32 version that should have been installed by your Graphics driver.

{steamlibrary}Steam\steamapps\common\No Man's Sky\Binaries\vulkan-1.dll

(it is version 1.4.307)
Rename it to vulkan-1.dll.bak (as in backup)

No guarantees this will work.

/edit/
Just to verify I am not suggesting you do anything dangerous to your system, I just did the same dll rename on my game
https://steamcommunity.com/sharedfiles/filedetails/?id=3455420447
However, the system32 vulkan-1.dll in my system is almost the same version (March 2025 nVidia driver update) so was less likely to cause issues.