No Man's Sky (275850)

[Stumpftopf]

Just to document it:
Rendering in No Man's Sky don't work at this moment with amdgpu or radeonsi driver correctly.
It seems to be a mix on crappy shader code and some issues with mesa.
But there is a bug ticket on mesa's bugzilla:
https://bugs.freedesktop.org/show_bug.cgi?id=107581

Processor Information:
    CPU Vendor:  AuthenticAMD
    CPU Brand:  AMD Ryzen 7 2700X Eight-Core Processor         
    CPU Family:  0x17
    CPU Model:  0x8
    CPU Stepping:  0x2
    CPU Type:  0x0
    Speed:  4000 Mhz
    16 logical processors
    8 physical processors
    HyperThreading:  Supported
    FCMOV:  Supported
    SSE2:  Supported
    SSE3:  Supported
    SSSE3:  Supported
    SSE4a:  Supported
    SSE41:  Supported
    SSE42:  Supported
    AES:  Supported
    AVX:  Supported
    CMPXCHG16B:  Supported
    LAHF/SAHF:  Supported
    PrefetchW:  Unsupported

Operating System Version:
    Ubuntu 18.04.1 LTS (64 bit)
    Kernel Name:  Linux
    Kernel Version:  4.17.13-041713-generic
    X Server Vendor:  The X.Org Foundation
    X Server Release:  11906000
    X Window Manager:  Xfwm4
    Steam Runtime Version:  steam-runtime-beta-release_2018-06-14

Video Card:
    Driver:  X.Org AMD Radeon(TM) HD 8800 Series (PITCAIRN, DRM 3.25.0, 4.17.13-041713-generic, LLVM 8.0.0)
    Driver Version:  4.4 (Compatibility Profile) Mesa 18.3.0-devel - padoka PPA
    OpenGL Version: 4.4
    Desktop Color Depth: 24 bits per pixel
    Monitor Refresh Rate: 60 Hz
    VendorID:  0x1002
    DeviceID:  0x6810
    Revision Not Detected
    Number of Monitors:  2
    Number of Logical Video Cards:  1
    Primary Display Resolution:  1920 x 1080
    Desktop Resolution: 3840 x 1080
    Primary Display Size: 23.54" x 13.23" (26.97" diag)
                                            59.8cm x 33.6cm (68.5cm diag)
    Primary VRAM: 2048 MB

Sound card:
    Audio device: ATI R6xx HDMI

Memory:
    RAM:  16035 Mb

[LeJimster]

There's a fix for it but I don't believe its available right now. Should appear in mesa-dev soon.

https://www.phoronix.com/scan.php?page=news_item&px=RadeonSI-GL-4.5-Compat-Patches

[djhi]

Works flawlessly with an nvdia card though

[jarrard]

This game actually has a issue with nvidia cards, it can't allocate vram correctly so you end up with texture and terrain mesh pop in that is quite bad.

If you switch between windows and linux and just pan/walk around you can see this effect quite obviously. Do 180deg turn and the textures slowly load in along with tessellation mesh etc...

this is probably a result of the game unable to detect correct amount of vram for the videocard for some reason and auto assigning quite a low amount instead of utilizing the GPU's full amount.

The warning can be turned off in NMS config but it doesn't fix the issue, no amount of setting fixes it.

[Stumpftopf]

Hello,
today it seems now NMS is finally working, in some case...
The white screen is gone and the game is playable. But the ground textures are glitching around.
I use this ppa to get the newest mesa build: https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers
They have merged the workarounds that i mentioned before and where discussed in this mesa bug report: https://bugs.freedesktop.org/show_bug.cgi?id=107581
I hope somebody can report back if he have the same issues with the ground textures.

[kisak-valve]

No Man's Sky (App ID:275850) black screen on resolution higher than 1920*1080

Issue transferred from #1034.
@Liodinis posted on 2018-08-30T22:52:04:

Ubuntu 18.04.1 LTS
I7 6700K @ 4.00Ghz
Nvidia GTX 1070
Nvidia driver 396.54
Proton 3.7-3
RAM 16Go
SSHD 1To Toshiba H200
Display Acer Predator 24" 2560X1440

"No Man's Sky" doesn't work on resolution higher than 1920*1080.

Launch the game is displaying a black screen, but the game seems to be working, because sounds can be hear in background.
If you put your screen resolution at 1920*1080 or edit the config file TKGRAPHICSSETTINGS.MXML with the native resolution of your screen at the place below :

/home/username/.local/share/Steam/steamapps/common/No Man's Sky/Binaries/SETTINGS

restart the game, and it will become playable.

Hardware Configuration.txt

No Man's Sky config file.zip

[kisak-valve]

No Man's Sky [App ID:275850] Crash on nvidia

Issue transferred from #1072.
@hitchhiker54 posted on 2018-08-31T13:42:44:

The game plays flawlessly so far except for scanning when an npc base is in view. Tested on Minor Settlement and Observatory type, if the base is in view the game instantly crashes to desktop when in visor view. Player bases, ships, exocraft all seem to be fine. Using gtx980ti, i76700k on Ubuntu 18.04, Nvidia drivers 396.54

[edits additional]
Game version 1.58, issue also reported to Hello Games

sudo lshw results :
https://www.dropbox.com/s/xxu34qjfnjp7f01/specs.txt?dl=0

[mimattr]

Ubuntu 16.04, NVIDIA GTX 970, Proton 3.7-5 Beta:

Steam System Information

Test	Result
Singleplayer	Working as expected
Local Co-op	N/A
Online Multiplayer	Working as expected

Configuration	...
Input	Steam Controller
Display	1920x1080
Fullscreen	Yes
Preset	Medium^
VSync	Off^^
API	OpenGL

^ Default graphics preset is High
^^ Default VSync setting is On

[Griffen8280]

Tried with Proton 3.7-3.

The game worked flawlessly. With my setup. Attached pastebin shows the specs of my machine and versions of all relevant drivers/software.

My specs: https://pastebin.com/9hQP94N1

[jarrard]

Yes it works technically better then on windows for me because on windows I can't remove screen tearing without vsync enable which seems to cost fps. But under linux with vsync off there is no tearing.

I did find the game caches textures a bit slow on NTFS, you can speed it up a bit by using big_writes in the disk drive mount options. Or move it to BTRFS or EXT4 drive.

[nathanjackson]

No Man's Sky seems to actually run smoother on my aging graphics card in Linux! Seems to be working out of the box.

Fedora 28
Core i7-4770
Nvidia GTX 760
Proton 3.7-3

[8BitCerberus]

I had the same black screen issues as comment: #438 (comment)

In the same TKGRAPHICSSETTINGS.MXML file, setting "Borderless" to True will also allow the game to run properly, even if the desktop resolution is higher than the game's resolution. I want to run games at 1920x1080 for any recording/streaming, but my desktop is set to 1920x1200, setting the borderless option allows me to do so.

In Windows have no problem just setting my monitor to 1920x1080 when needed, but in Linux I am having an issue which I suspect is with my DVI cable, that's not letting the system recognize any 16:9 resolutions for this monitor, and I've been unable to add them with xrandr (keep getting a BadMatch error when trying to add it to DVI-I-1.) I've got a DisplayPort cable on order that I'm hoping will open up the full range of resolutions my monitor is capable of. My second monitor connected via HDMI has all of it's modes properly recognized, my main monitor doesn't have an HDMI port or I would have tested it to be sure it's the DVI cable.

Update: It was the DVI cable. DP cable came in last week and all display modes/resolutions are available now.

[kisak-valve]

[ISSUE] No Man`s Sky no sound ( 275850)

Issue transferred from #1459.
@Rainakins posted on 2018-09-15T09:23:49:

Compatibility Report

• Name of the game with compatibility issues: No Man`s Sky
• Steam AppID of the game: 275850

System Information

• GPU: GTX 1050ti
• Driver/LLVM version: Nvidia 396.54
• Kernel version: 4.15
• Link to full system information report as Gist:

Computer Information:
Manufacturer: Unknown
Model: Unknown
Form Factor: Desktop
No Touch Input Detected

Processor Information:
CPU Vendor: AuthenticAMD
CPU Brand: AMD Ryzen 5 2600 Six-Core Processor
CPU Family: 0x17
CPU Model: 0x8
CPU Stepping: 0x2
CPU Type: 0x0
Speed: 3400 Mhz
12 logical processors
6 physical processors
HyperThreading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Supported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported

Operating System Version:
Ubuntu 18.04.1 LTS (64 bit)
Kernel Name: Linux
Kernel Version: 4.15.0-34-generic
X Server Vendor: The X.Org Foundation
X Server Release: 11906000
X Window Manager: GNOME Shell
Steam Runtime Version: steam-runtime-beta-release_2018-06-14

Video Card:
Driver: NVIDIA Corporation GeForce GTX 1050 Ti/PCIe/SSE2
Driver Version: 4.6.0 NVIDIA 396.54
OpenGL Version: 4.6
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 60 Hz
VendorID: 0x10de
DeviceID: 0x1c82
Revision Not Detected
Number of Monitors: 1
Number of Logical Video Cards: 1
Primary Display Resolution: 1920 x 1080
Desktop Resolution: 1920 x 1080
Primary Display Size: 20.08" x 11.30" (23.03" diag)
51.0cm x 28.7cm (58.5cm diag)
Primary Bus: PCI Express 16x
Primary VRAM: 4096 MB
Supported MSAA Modes: 2x 4x 8x 16x

Sound card:
Audio device: Nvidia GPU 80 HDMI/DP

Memory:
RAM: 16052 Mb

Miscellaneous:
UI Language: English
LANG: en_US.UTF-8
Total Hard Disk Space Available: 194192 Mb
Largest Free Hard Disk Block: 107787 Mb
VR Headset: None detected

Recent Failure Reports:

• Proton version: 3.7-6

I confirm:

• [ x ] that I haven't found an existing compatibility report for this game.
• [ x ] that I have checked whether there are updates for my system available.

steam-275850.log

Symptoms

The sound was working initially for about a week and for some reason yesterday the sound completely stopped working everything else still runs fine and performance is great but the sound simply does not work any longer

Reproduction

for me its easily done by launching the game

[viggy96]

For me the game freezes after difficulty selection. I just get a black screen, and GNOME becomes completely unresponsive. The sound for the game continues, however, I am unable to interact with the computer further, and a hard reset is required. I have tried manually changing the game to borderless and windowed modes to no effect.

I'm using an R9 Fury, Mesa 18.3, LLVM 8 from Padoka unstable as recommended by Proton, and kernel 4.18.8.

[jarrard]

What does ulimit -aH tell you? could be a limited open files issue which is often associated with load freezes.

[viggy96]

output of ulimit -aH

core file size          (blocks, -c) unlimited
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 63415
max locked memory       (kbytes, -l) 16384
max memory size         (kbytes, -m) unlimited
open files                      (-n) 4096
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) unlimited
cpu time               (seconds, -t) unlimited
max user processes              (-u) 63415
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited

[kisak-valve]

Hello @viggy96, give https://github.com/zfigura/wine/blob/esync/README.esync a read and increase the max open files limit on your system.

[viggy96]

@kisak-valve I thought I did it properly before, but apparently not, LOL. However, regardless, No Man's Sky still fails in the same way for me.
output of ulimit -aH

core file size          (blocks, -c) unlimited
data seg size           (kbytes, -d) unlimited
scheduling priority             (-e) 0
file size               (blocks, -f) unlimited
pending signals                 (-i) 63415
max locked memory       (kbytes, -l) 16384
max memory size         (kbytes, -m) unlimited
open files                      (-n) 1048576
pipe size            (512 bytes, -p) 8
POSIX message queues     (bytes, -q) 819200
real-time priority              (-r) 0
stack size              (kbytes, -s) unlimited
cpu time               (seconds, -t) unlimited
max user processes              (-u) 63415
virtual memory          (kbytes, -v) unlimited
file locks                      (-x) unlimited

[viggy96]

I still can't seem to get past the black screen on this game. Not sure what could be causing this. I've increased the max open files limit, as above, but still no dice.

[garpu]

Nvidia 396.54.09, Geforce GTX 1050ti, Proton 3.16-1 Beta, Slackware 14.2 multilib. After this morning's update to Proton 3.16-1, I'm getting an error saying No Man's Sky needs at least 1.5 GB of VRAM and that the adapter (blank) is reporting 0. The game loads and plays just fine, if you click through, though. Bug? Or something I need to change?

[SwooshyCueb]

@viggy96 Are you still having trouble?

[garpu]

Sorry, meant to update. My issues were fixed with 3.16-3.

[kisak-valve]

Hello @euclip, it should be noted that the first space station you arrive at is in a randomly selected star system, and occasionally some star systems behave differently for whatever reason. Can you note the graphics settings you were using when you saw the rendering artifact?

[euclip]

Can you note the graphics settings you were using when you saw the rendering artifact?

Sure.

Desktop

Steam Deck

[stalkerg]

@kisak-valve I think I should make an issue for Mesa, but just for information on Vega10 (Vega56), I have GPU hung if I enable FSR2, constant. Maybe I can fix it by myself but have no time now to debug kernel and mesa.

[euclip]

I started a new game and, curiously, experienced no issues this time, not on my desktop and not on my Deck. I would say it seems like a bug in the game itself, but the fact that the old save still crashes on my desktop but not on my Deck suggests there might be more to it than that. I don't know what it could be though.

[Blisto91]

Is it possible for you to share the save game?

[euclip]

I don't really know whether they're tied to my account or not, but here are the files: https://gofile.io/d/0eVCYQ

[Blisto91]

@euclip Okay i got to test this on both Linux and Windows now.
I believe it's a game bug as the foggy issue is present with the native game and i can also get it to crash by running around (tho seemed a bit easier on Linux radv, but might be a coincidence). I have sent a bug report to the devs.

[FuzzyQuils]

@euclip Okay i got to test this on both Linux and Windows now. I believe it's a game bug as the foggy issue is present with the native game and i can also get it to crash by running around (tho seemed a bit easier on Linux radv, but might be a coincidence). I have sent a bug report to the devs.

Fwiw I don't get this issue with my save; might try the save above with my system.

[Blisto91]

Fwiw I don't get this issue with my save

Since the game is semi random/procedural the issue sems to have been tied to the location in the save above.

I think the crash might have been fixed in the latest game update as just when trying again now i wasn't able to reproduce. The visual "white foggy issue" is still present tho.

[TheTwoBoom]

It's very weird that I also got the white foggy issue on windows (same hardware, dual boot) after using a save game saved on linux
Maybe it's a bug that's OS independent?

[lavadrop]

I have been getting random GPU driver crashes since the last patch.
White screen when loading a save, then the x session crashes completely and the computer is sent to the user log in screen.
I have been able to play if I press "Delete Proton Files" from the new steamui but it still isn't infallible. Tested with Proton 7, 8 and experimental.

dmesg output:

[ 1780.133780] amdgpu 0000:07:00.0: amdgpu: GPU fault detected: 147 0x03980401 for process NMS.exe pid 5073 thread NMS.exe pid 5073
[ 1780.133784] amdgpu 0000:07:00.0: amdgpu:   VM_CONTEXT1_PROTECTION_FAULT_ADDR   0x08B4A534
[ 1780.133786] amdgpu 0000:07:00.0: amdgpu:   VM_CONTEXT1_PROTECTION_FAULT_STATUS 0x0E004001
[ 1780.133787] amdgpu 0000:07:00.0: amdgpu: VM fault (0x01, vmid 7, pasid 32795) at page 146056500, read from 'TC1' (0x54433100) (4)
[ 1790.342669] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=266582, emitted seq=266584
[ 1790.342972] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process NMS.exe pid 5073 thread NMS.exe pid 5073
[ 1790.798106] amdgpu: cp is busy, skip halt cp
[ 1791.058901] amdgpu: rlc is busy, skip halt rlc

Steam Runtime Diagnostics: https://gist.github.com/lavadrop/2295103919919355d26c5e9ce5c6f1ca

[kisak-valve]

Hello @lavadrop, please copy the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report.

[lavadrop]

I just updated my report @kisak-valve

[Blisto91]

@lavadrop Are you still having crash issues? I tried playing a bit on my rdna3 GPU with the same mesa version but haven't encountered a issue yet.

[lavadrop]

It appears to have been resolved @Blisto91 , I'm on Mesa 23.1.5 and it didn't crash the x server for a couple of hours. However haptic feedback/adaptive triggers are still not working either via USB nor Bluetooth.

[JPLeBreton]

Steam Cloud has seemingly stopped uploading my save since the latest update, and I'm not sure if it's a Steam issue, a No Man's Sky issue, or something else. See here for details: ValveSoftware/steam-for-linux#10014

Linking that report here just in case other people have been seeing this (it would be good to be able to rule out or rule in it starting with Thursday's update).

[mnn]

Not sure if it belongs here, but after yesterdays update of NMS and SteamVR, it has become unplayable in VR - constant stuttering 😢

[Patola]

On VR, now using SteamVR 2, No Man's Sky is not registering the trigger, so I can't even select anything on the first screen. And when I call the overlay to check the steamvr input, again the enormous lag on the controller windows is there, so much that I can't see or change the bindings.
using Mesa 23.2.1 on Arch, RX 7900 XTX, Ryzen 7 7800X3D, Valve Index with Knuckles and 3 base stations.

[mnn]

The constant micro stuttering is still present (maybe bad reprojection?), tried SteamVR 2.0 and the current beta (2.0.9). I am using Proton Experimental (not sure about version; I have also tried Proton GE 8-15, same behaviour). Pretty much the same issue in both SteamVR versions (one seemed to have slightly bigger "lag"). Compared to the previous working version, there are now black and white artifacts on edges of "screens" (it follows lens shape, I guess it should have been solid black color). I also saw "Error 303" from SteamVR, but it didn't seem to change anything (it was behaving same without the reported error). It seems related to NMS, because I tried few other games and there are no issues. It is quite frustrating, because it used to work fairly well, so I started playing with a friend and now we can't continue... 😞

[LukeStonehm]

I'm getting "No connection to matchmaking service". I am seemingly unable to try 5.11 in current year (it hangs on a white screen after the star fly through loading screen thing).

Any suggestions?

[nadrolinux]

After Omega* update I see a massive memory leak. Game freezes after ~15-25 seconds when my 16GB RAM is filled. I have RX6600 with RADV driver.

• Before Omega update I used Fedora 39 Workstation + rpm Steam, now I use Fedora 39 Silverblue + Flatpak Steam, so maybe my OS or Flatpak cause issue, I'm not sure and sadly I don't have access to F39 Workstation anymore. Anyone here with Flatpak Steam and working NMS?

UPDATE:
After switch to Gnome (Xorg) NMS works fine, so probably it's not Omega or Steam issue, but Gnome.