New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No Man's Sky (275850) #438
Comments
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 |
Works flawlessly with an nvdia card though |
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. |
Hello, |
No Man's Sky (App ID:275850) black screen on resolution higher than 1920*1080 Issue transferred from #1034. Ubuntu 18.04.1 LTS "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. /home/username/.local/share/Steam/steamapps/common/No Man's Sky/Binaries/SETTINGS restart the game, and it will become playable. |
No Man's Sky [App ID:275850] Crash on nvidia Issue transferred from #1072. 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] sudo lshw results : |
Ubuntu 16.04, NVIDIA GTX 970, Proton 3.7-5 Beta:
^ Default graphics preset is High |
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 |
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. |
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 |
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. |
[ISSUE] No Man`s Sky no sound ( 275850) Issue transferred from #1459. Compatibility Report
System Information
Computer Information: Processor Information: Operating System Version: Video Card: Sound card: Memory: Miscellaneous: Recent Failure Reports:
I confirm:
SymptomsThe 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 Reproductionfor me its easily done by launching the game |
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. |
What does ulimit -aH tell you? could be a limited open files issue which is often associated with load freezes. |
output of ulimit -aH
|
Hello @viggy96, give https://github.com/zfigura/wine/blob/esync/README.esync a read and increase the max open files limit on your system. |
@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.
|
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. |
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? |
@viggy96 Are you still having trouble? |
Sorry, meant to update. My issues were fixed with 3.16-3. |
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? |
@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. |
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. |
Is it possible for you to share the save game? |
I don't really know whether they're tied to my account or not, but here are the files: https://gofile.io/d/0eVCYQ |
@euclip Okay i got to test this on both Linux and Windows now. |
Fwiw I don't get this issue with my save; might try the save above with my system. |
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. |
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 |
I have been getting random GPU driver crashes since the last patch. dmesg output:
Steam Runtime Diagnostics: https://gist.github.com/lavadrop/2295103919919355d26c5e9ce5c6f1ca |
I just updated my report @kisak-valve |
@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. |
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. |
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). |
Not sure if it belongs here, but after yesterdays update of NMS and SteamVR, it has become unplayable in VR - constant stuttering 😢 |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
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. |
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... 😞 |
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? |
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.
UPDATE: |
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
The text was updated successfully, but these errors were encountered: