Experimental Branch 08/12

[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.

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 20/01

• Updated Nvidia Streamline to version 2.10.0

Experimental Branch 08/12

• Fixed an issue that could cause a hang when using Intel XeSS.

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.

[Tolwyn]

First person view of the newest astronaut outfit still has issues.
Some of the mannequins in Space Stations are still incomplete.
Still some tearing on the stair lighting in Pirate Capital Ship bridges.

(yes all these reported a few times)

[nanoplasm]

(EXPERIMENTAL 08/12) Frigate Expedition Mission Blocked – Cannot Board “Frigate of the Expedition Commander” if it is a Living Frigate

Platform: PC (Experimental Branch 08/12) No Mods Installed: Confirmed

Severity: High (Blocks progression in frigate expedition feature)

Description & Chronological Context: The frigate expedition mission “Assist Journey into the Infinite” requires players to dock with the Fleet Commander’s frigate to translate a mysterious message:

“Warp to the expedition system and dock with the frigate of the expedition commander to translate the mysterious message.”

This bug specifically occurs when a Living (Organic) Frigate is assigned as the Fleet Commander, as these vessels cannot be boarded like standard frigates, leading to mission failure.

Observed Behavior History (Context of 08/12 Experimental Branch):

• Previous Build Behavior (Original Bug): The mission marker pointed directly to the Living Frigate, which is non-landable. (See Supporting Evidence: B. Initial Bug Marker)
  
• 08/12 Experimental Behavior (Attempted Fix): The mission marker behavior changed. It now targets a non-organic frigate within the same fleet. (See Supporting Evidence: C. 08/12 Marker Redirection)

Actual Outcome (08/12 Build): The mission still does not progress. Even after landing on the newly targeted non-organic frigate and completing the triggered dialogue, the objective fails to register. The frigate expedition mission cannot progress and must be abandoned.

Impact: This bug blocks progression in a key Frigate Expedition feature, causing confusion and unnecessary expenditure of player time and resources.

Expected Outcome: Players should be able to complete the mission regardless of the expedition commander’s frigate type.

If the target is a Living Frigate, the game should either: – Provide an alternate interaction method (e.g., proximity-based trigger) – Or allow completing the dialogue from any fleet member’s frigate to count toward mission progress

Since the Voyager update, Corvettes dock by parking alongside conventional frigates instead of using landing pads. This same docking mechanic could be extended to Living Frigates for a consistent solution.

Supporting Evidence:

1. The Problem and Previous Behavior

A. Mission Text Requirement: The in-game text demanding the player "dock with the frigate of the expedition commander."
https://steamcommunity.com/sharedfiles/filedetails/?id=3512604557

B. Initial Bug Marker (Previous Builds): The mission marker incorrectly targeting the Living Frigate, which is impossible to land on.
https://steamcommunity.com/sharedfiles/filedetails/?id=3575975944

2. Behavior in 08/12 Experimental Branch

C. 08/12 Marker Redirection (Attempted Fix): The marker is now correctly redirecting to a standard, boardable frigate in the same fleet.
https://steamcommunity.com/sharedfiles/filedetails/?id=3620383252

D. Proof of Failure (Objective Does Not Progress): Landing on the redirected frigate triggers the dialogue prompt, but the mission remains stuck.

• Landing on Redirected Frigate: https://steamcommunity.com/sharedfiles/filedetails/?id=3575975970
  
• "Translate a mysterious message" prompt: https://steamcommunity.com/sharedfiles/filedetails/?id=3578026121
  
• Prompt options 1-3 (no mission completion):
  https://steamcommunity.com/sharedfiles/filedetails/?id=3578026128
  https://steamcommunity.com/sharedfiles/filedetails/?id=3578026134
  https://steamcommunity.com/sharedfiles/filedetails/?id=3578026141

3. Context for Proposed Solution

E. Existing Docking Mechanic (Corvette): A Corvette utilizing the new, pad-less docking mechanic alongside a conventional frigate.
https://steamcommunity.com/sharedfiles/filedetails/?id=3566230103

F. Application to Living Frigate: A Corvette positioned in the same manner alongside a Living Frigate, suggesting the mechanic could be universally applied for interaction.
https://steamcommunity.com/sharedfiles/filedetails/?id=3566230086

This suggests a potential unified mechanic: allowing Corvettes to dock with Living Frigates as they do with conventional frigates.

Related Player Feedback: Multiple players have reported similar issues:

“One such mission of mine requires boarding a living frigate… I tried flying around looking for a way in and could not do so.” “Cannot board my organic frigate to translate alien code for fleet expedition mission.”

Source: Reddit – r/NoMansSkyTheGame: How to board a living frigate?

[Gyson]

From the previous update:

Originally posted by Hello Games:

Fixed an issue that could cause Corvette technology slots to re-arrange themselves after playing in multiplayer.

This was not fixed in the update. Not at all, from what I can tell. My corvette technology slots continue to rearrange themselves (I play multiplayer) just as they did prior to the patch. I have noticed zero improvement in that regard.

I hate to say this, but there seems to be a habit of Hello Games mentioning a fix in the patch notes only for the problem to still remain. Or, the very next patch reintroduces the problem back into the game. Are you confirming these fixes are working with internal testing, or just relying on us to let you know whether a "potential" fix you implemented worked or not?

As an example, after the Voyagers 6.0 update introduced the Skyborn Exosuit (and the bug with it's backpack effects showing up when running in first person), that issue was specifically mentioned and fixed in the Voyagers 6.02 update. But then it was reintroduced in the 6.03 update and has remained with us ever since.

[MonkeyUdders]

Originally posted by Gyson:

From the previous update:

Originally posted by Hello Games:

Fixed an issue that could cause Corvette technology slots to re-arrange themselves after playing in multiplayer.

This was not fixed in the update. Not at all, from what I can tell. My corvette technology slots continue to rearrange themselves (I play multiplayer) just as they did prior to the patch. I have noticed zero improvement in that regard.

I hate to say this, but there seems to be a habit of Hello Games mentioning a fix in the patch notes only for the problem to still remain. Or, the very next patch reintroduces the problem back into the game. Are you confirming these fixes are working with internal testing, or just relying on us to let you know whether a "potential" fix you implemented worked or not?

As an example, after the Voyagers 6.0 update introduced the Skyborn Exosuit (and the bug with it's backpack effects showing up when running in first person), that issue was specifically mentioned and fixed in the Voyagers 6.02 update. But then it was reintroduced in the 6.03 update and has remained with us ever since.

I believe this bug had two versions - multiplayer would trigger it - but also if you switched ships in some way that would trigger it. Maybe they only fixed one. I'm sure most bugs are like this. Between the nuance of the exact situation being fixed and the writing of the patch notes, I'm not surprised that this happens a lot where a patch note describes something that is not fixed. It probably fixed something, just not what you thought.

[Gyson]

Originally posted by MonkeyUdders:

I believe this bug had two versions - multiplayer would trigger it - but also if you switched ships in some way that would trigger it. Maybe they only fixed one. I'm sure most bugs are like this. Between the nuance of the exact situation being fixed and the writing of the patch notes, I'm not surprised that this happens a lot where a patch note describes something that is not fixed. It probably fixed something, just not what you thought.

Let's try this another way then: Can anyone who had the problem of their corvette modules rearranging tech-slot positions *prior to the patch* noticed that their corvette modules are no longer having their tech-slot positions rearranged *after* the patch?

Anyone?

Not aimed at you specifically MonkeyUdders, because I get the sense you're just trying to help. But I want to clarify something here before the white knights come charging into the defense of the game. Some developers add fixes to their patch notes only after those fixes have been thoroughly tested by and verified to work. But some developers add *potential* fixes to their patch notes and instead rely on the playerbase to let them know whether their attempt at a solution completely solved a problem or not. Star Citizen developers are an example of the latter.

So, I'm just trying to figure out which way Hello Games operates, because there have been examples of their patch notes claiming something is fixed when it actually isn't. That's not a slight against them; it depends on how they approach the patch process (although I would personally prefer not to be free QA testing and instead see these fixes tested in-house), but it will help to set expectations whenever a patch is rolled out.

[Rocky]

Would be awesome if you guys could take the time to fix the jellied eel recipe (fleshy cylinder and jellymeat) so it's not making seafood stew instead. Thanks for your time and effort

[AJ, Lord of Chaos]

Unrelated but congratulations on winning the price, guys. Very earned.

[havenwood29]

Why is corvette maneuverability still changing? It's frustrating as hell.

[DraRex368]

Hi, i have a serious question, in game that you need to pilot a plane or a ship, you can use the Flight Stick (No matter what type of Flight Stick), Lets say Elite Dangerous Allows Flight Stick to be used but your game can't use joystick, i'm so used to play ED With Flight Stick, can you make an update that allows the use of the Flight Stick? Pls

[frvind74]

New Bug
Setting "reflections" to a high or higher value in the graphics settings causes problems with the carapace of living ships: when you move a few meters away from the ship (even with a camera), the textures disappear and you only see the fluid movement of the ship's "liquids."
Really really ugly.
Introducing new bugs with the last two updates is the worst thing that can happen!

[frvind74]

Hi,
...in the circumstance you pass from DLSS to DLAA game stops immediately: this problem has happened just from December 2024 and never taken in priority. Is this normal?
PC Steam, RTX2060 (a Vulkan semaphore error).
Thanks

PS
Merry Christmas

[bssnewbie]

My game don't turning on/loading even with experimental

[blakespot]

Is anyone else experiencing this issue? I noticed it running PC Experimental in the last couple of weeks or so (I think...).

I've been playing since day one in 2016, and my main “1.0 save” file is still my main save, and for a little while I've noticed when I teleport out of a Station to somewhere and then try to teleport back (looking for the Station listed under Stations tab in the Teleporter menu), it's not showing any of the recent Stations I've been in and warped out of. The latest Station listed is in Eissentam, and I'm in Euclid as I've been exclusively for a while now – I've warped out of quite a few stations in Euclid and none are showing at the top of (or anywhere in) the list.

I used a old Expedition save and did a test where I warped out of a Station to a base and then warped to another system and then went to its Station and looked at the Teleporter Station list and there at the top was the one that I came from - as it should have been. This is not updating any longer in my main save.

I have thousands of hours in this main "1.0" save, and worry that playing on in this save is risky -- something is not right. New bases I create are listed under Bases, so I can still teleport there, but I worry about playing on in this save -- will it get worse? And I **REALLY** don't want to lose my progress and all I've built here; in no other save on this PC have I completed any of the core quests -- there would be A LOT of work to get myself back to a position where I can access Purple systems in one of those other saves.

(I have not edited this save in a Save File at any point.)

[wkitty42]

Originally posted by blakespot:

Is anyone else experiencing this issue? I noticed it running PC Experimental in the last couple of weeks or so (I think...).

it is a known defect... there is no known fix players can apply... report it to the HG zendesk... the more reports they get about it, the higher and faster it will float up the TODO list...
https://hellogames.zendesk.com/

[blakespot]

Originally posted by wkitty42:

Originally posted by blakespot:

Is anyone else experiencing this issue? I noticed it running PC Experimental in the last couple of weeks or so (I think...).

it is a known defect... there is no known fix players can apply... report it to the HG zendesk... the more reports they get about it, the higher and faster it will float up the TODO list...
https://hellogames.zendesk.com/

Ah, good to hear - sounds like it likely will be fixed, then. I did report it with my ancient and large save file (215MB ZIPed) shortly before my post here. Fingers crossed.