Experimental Branch 04/07

[Hello Games]

Hello Everyone,

First of all, thanks so much to everyone who has already spent time playing No Man's Sky and letting us know about any issues you've experienced.

Steam users are able to opt-in to the Experimental Branch, where we have pushed a patch to address some problems. We'll be rolling out these fixes to other platforms as soon as possible.

To play in Experimental, right-click on No Man's Sky from the Steam library page and select "Properties". Among the available tabs will be the "BETAS" tab. Enter "3xperimental" in the textbox and press "CHECK CODE", then select it from the dropdown menu.

The patch notes are as follows:

Experimental Branch 11/07

• Fixed an issue that could cause markers to flicker.
  
• Fixed an issue that caused a crash when attempting to load invalid discovery data.

Experimental Branch 10/07

• Fixed an issue that could cause a crash on Xbox One when visiting the final planet of the Singularity expedition.
  
• Fixed a rare crash related to the projectile system.
  
• Fixed an issue that could cause a crash when downloading invalid discovery data from other players.

Experimental Branch 06/07

• Memory optimisations.
  
• Fixed a crash that could occur when ships land at an outpost.

Experimental Branch 05/07

• Memory optimisations.

Experimental Branch 04/07

• Optimised memory used by creature navigation.
  
• Optimised memory used to fade objects.

As always, thank you to all players who use Experimental and take the time to report any issues you encounter.

Please note there is the possibility that experimental builds may introduce new issues that haven't been caught in test. We'd like to recommend that all players back up their save files, by making a local copy of the st_[userid] folder found here on PC: %appdata%\HelloGames\NMS\ and here on mac: ~/Library/Application Support/HelloGames/NMS/

Note that we don't anticipate any issues here. However, performing your own backups could mean the difference between resuming play immediately, or waiting for the next patch.

If you decide to opt out of experimental and return to the main branch, we strongly recommend resuming from a backed-up save from the main branch, rather than taking an experimental branch save back to main, which may cause unexpected behaviour.

Feedback and reports of new bugs/issues being found on Experimental are welcome, so please reply to this thread or submit a ticket to https://hellogames.zendesk.com/ with the phrase "Steam Experimental" in the ticket title. If you are running any mods for the game, please list them along with your bug report.

[Isthatyoudave?]

It basicallly looks like the game is not saving any Vulkan shaders and loading them in realtime all the time. The only shaders in the Steam cache is dxcache and the files are only 1kb and 16 kb. This could be why people are getting constant stutters. Its still unplayable on a 5900x

I have tested on a fresh win 11 install with only steam and nms running. All correct latest drivers for motherboard and gpu.

every load of the game causes the game to stutter constantly and is not any better on the next load of the game. It stutters as soon as the star field loading screen starts and its the same now every start and load of a save or new game.

[Finaryman]

nms 11642141, not fixed (wirring error powered status)

[Navigator]

Honestly, Hello Games need to be more clear with these ~8Gb patches. I see nothing about bug fixes for the non-experimental build in the post yet I have to do a 7.7Gb update? Very sus.

[Musashi]

As soon as experimental goes public you will see the patchnotes

[darling]

i know y'all changed the jetpack please change it back it's horrible now

[Navigator]

Originally posted by Musashi:

As soon as experimental goes public you will see the patchnotes

How's that related to the 7.7Gb update for the non-experimental build?

[Finaryman]

Originally posted by Navigator:

Originally posted by Musashi:

As soon as experimental goes public you will see the patchnotes

How's that related to the 7.7Gb update for the non-experimental build?

that's what he/she ment, experimental will turn to non-experimental (public).

[Stu]

I have an Immediate crash with build 11667412 whenever I click the Discoveries tab. Can click through everything else with no problem, but as soon as I click Discoveries, it crashes to desktop. Loaded the game 3 times / traveled to new system with same result.

[Finaryman]

nms 11667412, not fixed (wirring error powered status)

Originally posted by Stu:

I have an Immediate crash with build 11667412 whenever I click the Discoveries tab. Can click through everything else with no problem, but as soon as I click Discoveries, it crashes to desktop. Loaded the game 3 times / traveled to new system with same result.

upload ur save to zendesk

[Stu]

Figured out and fixed my problem. I had visited the troublesome system in Exp. 10 with my normal save, so I had the bad data from there in the "DiscoveryManagerData" part of my save. Edited the raw JSON to remove the invalid data and no more crashes.

Hello Games: do you need some tutoring from Bobby Tables on sanitizing your data input, or did someone crack the discovery services db?

[Prescient Stones]

Originally posted by Stu:

Figured out and fixed my problem. I had visited the troublesome system in Exp. 10 with my normal save, so I had the bad data from there in the "DiscoveryManagerData" part of my save. Edited the raw JSON to remove the invalid data and no more crashes.

Hello Games: do you need some tutoring from Bobby Tables on sanitizing your data input, or did someone crack the discovery services db?

Is this the Famous Stu that Discovers all the Anomaly Planets? It's an honor to see your avatar and thank you for all the years of Discovery.

[PunsNRoses]

Originally posted by Stu:

I have an Immediate crash with build 11667412 whenever I click the Discoveries tab. Can click through everything else with no problem, but as soon as I click Discoveries, it crashes to desktop. Loaded the game 3 times / traveled to new system with same result.

Having the same issue.

[Captain.Jartyk]

Originally posted by Hello Games:

Experimental Branch 10/07

• Fixed an issue that could cause a crash on Xbox One when visiting the final planet of the Singularity expedition.
  
• Fixed a rare crash related to the projectile system.
  
• Fixed an issue that could cause a crash when downloading invalid discovery data from other players.

Could any of that have fixed the crash bugs for R1 (Zahmanum) on expedition 10?
I currently don't have the experimental version installed, but maybe someone else who has can test and see if the problem is fixed, or not..
--
The bug is that if you teleport or warp there, the game crashes immediately.
If you run the game offline, there is no problem.
--

[darthyoda6]

Experimental Branch 10/07
Fixed an issue that could cause a crash when downloading invalid discovery data from other players.

Experimental Branch 11/07
Fixed an issue that caused a crash when attempting to load invalid discovery data.

[Finaryman]

nms 11676932, bug not fixed (wirring error powered status)