Thank you to everyone playing the No Man’s Sky Singularity Expedition, especially those taking the time to report any issues they encounter via Zendesk or console crash reporting.
We are listening closely to your feedback, and have identified and resolved a number of issues. These fixes are included in patch 4.34, which is now live.
-
Players are now able to rebind movement to the cursor keys without that automatically resulting in them moving around while navigating the quick menu.
-
Fixed an issue that prevented the cursor from rendering while re-binding controls in the Game Mode options screen.
-
Fixed an issue that caused a number of options to be missing from the options menu, or some options to appear when they should not.
-
Fixed an issue that caused the Terrain Manipulator menus to scroll the wrong way in VR.
-
Fixed a rare issue that could cause all NPCs to fall out of the Space Station.
-
Fixed a rare crash that could occur in VR.
-
Introduced a rendering optimisation for VR.
-
Fixed an issue that could cause the depth of field effect to be applied far too strongly on some platforms.
-
Fixed an issue that could cause black speckles to flicker across the screen during interactions that made use of the depth of field effect.
-
Fixed a rare issue that could leave player-owned Interceptor ships without any installed technology.
-
Fixed a graphical glitch that could occur in the Atlas’ particle effects when playing on Switch.
-
Fixed an issue that caused eyeballs to be positioned incorrectly within a specific Traveller-style head in the Appearance Modifier.
-
Introduced a memory optimisation related to planetary creatures.
-
Fixed an issue that could cause the starship’s landing gear to be incorrectly raised after save/loading within a landed ship.
-
Fixed an issue that caused first-person cockpit exit animations to fail to play.
-
Fixed an issue that could allow too many creatures to spawn when playing in multiplayer.
-
Fixed a Mac-only issue that caused large bases to be loaded very slowly.
-
Fixed an issue that could prevent the Singularity expedition from converting into a Normal mode save after it was completed.
-
Fixed a crash related to synchronising freighters in multiplayer.
-
Fixed an issue that caused the ship at the start of the Singularity expedition to be missing its Vesper Sail.
-
Fixed an issue that caused incorrect collision on outpost landing pads.
-
Fixed an issue that could cause players to be ejected from the Multi-Tool comparison screen when attempting to pin repair instructions for a Multi-Tool they do not yet own.
-
Fixed a rare issue that could cause players to be erroneously told their inventory was full when claiming the reward for “Wayfarer” milestone.
-
Fixed a rare issue that could cause the galaxy map Mission Path to point to the wrong destination system.
-
Fixed an issue that prevented some freighter engines from being correctly recoloured when choosing a new engine trail.
-
Fixed a crash related to the Multi-Tool.
-
Fixed a graphical issue that could cause the player to briefly appear while teleporting.
-
Fixed an issue that prevented starship distress beacons from animating correctly.
-
Fixed an issue that could cause Multi-Tools belonging to other players to become attached to NPCs.
-
Fixed an issue that could result in players becoming permanently stuck to the chair in the Guild Envoy’s area of the Space Station.
-
Fixed an issue that caused Sentinel Interceptor ships to be worth 10x as much as other ships when salvaging.
-
Fixed an issue that allowed too many Communication Stations to spawn on expedition planets.
-
Fixed a hang related to reloading missions.
-
Fixed a crash related to base part rendering.
-
Fixed a rare issue that could cause the current expedition to end early.
-
Fixed a rare crash related to the mission log.
-
Fixed a PlayStation 4 crash related to reporting bases.
We will continue to release patches as issues are identified and resolved. If you experience any issues, let us know by submitting a bug report.
Even when I don't suspect it, I systematically run it on any new PC I build just to ensure I'm running with good RAM out-of-the-box. So far I've had this issue only once with a brand new pair but I'm glad I caught it early on.