4 months ago - Hello Games - Direct link
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 30/05
  • Fixed an issue that caused two Adrift milestones to both award Nutrient Processor plans.
  • Fixed an issue that caused the Horizon Omega and Prime Vector pre-order ships to be interpreted as freighters, causing a crash shortly after claiming them.
  • Fixed a minor issue related to planetary tornadoes.
  • Fixed an issue that prevented the claiming of some expedition milestones if one of the rewards upgraded a ship or multitool, but the current item was already at S-Class.
  • Fixed an issue that prevented players from claiming the Ship of the Damned if they had permanently declined the freighter rewarded by an earlier milestone in the Adrift expedition.
  • Fixed a number of minor text issues.

Experimental Branch 30/05
  • Fixed an issue that could cause the Locate Substance mission for Atlantideum to end as soon as it started.
  • Fixed an issue that could cause discoveries with custom names to revert to their procedurally generated name after a save/load.
  • Fixed a number of minor text issues.
  • Fixed an issue that incorrectly added an non-functional "Locate Substance" button to Silicate Powder in the catalogue.
  • Fixed a rare issue that could cause some pinning missions to briefly appear blank in the log immediately after selecting them.
  • Fixed an issue that caused some mission instructions to become truncated.
  • Fixed an issue that caused dragging items on to a damaged or partially installed Personal Refiner to be treated as an attempt to refine the items rather than apply them to the repair.
  • Fixed an issue that prevented the Surge Battery recipe from being learnt at the correct point of the Adrift Expedition.
  • Fixed a crash related to replicating biological horrors.
  • Fixed an issue that could block progress in some Adrift milestones if every rendezvous had been visited before starting them.
  • Improved the responsiveness of the Iron Vulture engine VFX.
  • Fixed an issue that prevented various weather and hazard related objects (such as meteors, tornadoes, firestorms or lightning) from spawning.
  • Fixed a rare issue that could block redemption of the Ship of the Damned on other saves that also had the Leviathan.
  • Fixed an issue that could prevent custom starship textures from replicating correctly.
  • Fixed an issue that could cause a misleading hint related to Helios to appear while on the Adrift Expedition.
  • Fixed an issue that could cause players piloting some specific ships in third person to appear to other players as if they were dangling below the ship.
  • Fleet expeditions can now be managed from the freighter's fleet management terminal in the event there is no navigator present on the bridge.
  • Fixed a number of starship texture customisation issues.
  • Fixed a number of collision issues on the damaged starship base parts.

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.