No mans sky version 1.58 wont download

The card is also not overclocked, so I don't think it's a hardware issue. With the vendorid patch, the game loads normally up until the white screen when the game is fully loaded.

The screen then goes completely black apart from 2 UI elements being rendered, the red mission marker and centre white aim dot, and an xid 31 appears in dmesg. Any ideas on what could be causing these xid issues, it doesn't seem like anyone else here has them.

I looked through the nvidia forums as well, where people with this error code blamed it on a driver bug, and some DXVK users also get xid 31 with some games. I have no clue at this point. Info: Proton 4. Fixed a number of threading-related multiplayer matchmaking issues. Fixed an audio crash when quitting from the initial screen. Fixed a crash when quitting the game during audio initialisation. Fixed Steam VR in Linux. Fixed a rare issue where joining a full lobby causes an incorrect player ID.

Fixed an issue where players joining a group can be taken to the wrong system. Fixed an issue that caused some network games not to appear in the Join game screen. Fixed an issue that caused the Exocraft Technician to have an incorrect interaction. Fixed a crash caused by an invalid base index. So the behaviour I had in the beginning Black window and nothing else happening. The log seems to be a little shorter but still ends with the same stack overflow exception.

Still, very nice to see someone cares :smile: Here's the log from now: steampart aa. Has anyone verified that patch 2. Doesn't fix anything on my end. Have anybody found a fix for the loading screen crash yet? I have tried loading the game with proton 4. Edit: steam Then reapply the settings in-game. I believe setting tesselation above Enhanced is causing some crashes too. Before that I always had a crash to desktop when the loading screen ended and the game should have started.

After Hello Games released some fixes I wanted to know if I could play with the stable Padoka drivers again. With the experimental ACO driver the screen was frozen 2x times without any input possibilities left. But I didn't have such a bug before. However, the game crashed again at the same place directly after the loading screen. That's why I changed back to the ACO driver. I tried the latest patch and VR finally works!

This is awesome! Horrible performance to be expected on my and SteamVRs bug with async reprojection doesn't help there - but that's fine. The coming rx XT will probably handle that. Flying into space however made the game crash. Looked like the exact moment I was "in space", when I could see the asteroids. The window on the desktop froze, it didn't push any more frames to VR and audio kind of sounded like it was repeating the last 5 seconds or so.

Zamundaaa How did you get it to work? EDIT: And it just started working on experimental And go into the video settings, disable the 60fps cap, VSync, reduce the mirror window resolution etc. It's kind of OK for me with lowest settings, but without async reprojection it kind of stutters back and forth when moving the head.

On the VKx discord, an nvidia dev said they are trying to get in contact with Hello Games to issue a fix, since it was confirmed to be game's issue. Just tried the latest, unfortunately no progress for me. I tried launching with texture quality set to enhanced 1st launch in graph and at ultra 2nd , made no difference.

Still at fps no matter what. However, on the first launch I did crash and stutter heaps, but the second launch went fine. I think it was probably caching something. The latest experimental build also fixed my performance issues. I can now play the game without the spoof! This is fantastic! NMS was crashing right after the starfield loader. Upgrading to mesa Performances have improved significantly since last time I tried this game, but the menus are unusable, impossibly slow.

I'm using a polaris GPU and the game crashed in the start or loading screen. Loading or creating new save file doesn't work. Zamundaaa Confirmed, the experimental branch now appears to work as expected tested with Valve Index Headset. General performance is still an issue though this is also true on Windows.

The game worked great for me GTX with the nvidia to amd spoof. After today's update, I removed the spoof and the game still works great. I tried other tweaks suggested by the windows community but it still does not work. Looking at the VR frame graph, it seems the VR compositor is taking a long time doing something for some reason which makes the game lag. Other users on windows are reporting 90 FPS performance on no man's sky with setups like mine and VR.

I am getting like Yes, performance is still bad in VR, when you move your head around. That's on a Radeon VII, where all other games run just fine. If that works then it would probably be good to add your system report to issue Valve's either hit a wall or they're not putting in much effort to fix it. Is Async Reprojection now working on Linux at all?

Zamundaaa I don't think async reprojection is working at all for me on Linux according to the SteamVR settings screen. Only regular reprojection works and is always triggered in NMS. Motion smoothing doesn't work either as it's not supported, amusingly it says it's not supported on "older versions of Windows" :smile:.

I tried disabling reprojection and confirmed on the SteamVR Settings screen that it was not reprojecting, but the framerate was still so low it was nausea inducing. The game runs at FPS in p with max settings when not in VR, with drops to for a split second when landing on planets or in other cases.

Unfortunately in VR it performs much much worse even with the lowest settings. Changing settings had effects on visual quality but none on performance.

Zamundaaa I did try turning it off, and it showed me it's off but that makes absolutely no difference. Turning down all details, VR resolution, etc also don't help. I tried with the SteamVR 1. Performance is MUCH better for me with this version. However, most of the time it still does not run well enough to get out of Reprojection so it is not yet playable for me I get sick due to the low framerate but at least it will be for some people. The strange thing was, last week on 4.

This just popped up today after I updated to 4. Going back to 4. The crash hard hangs my computer with audio from the game still playing. I usually regain control of the system within a minute or so and I get the above screenshot.

No "xid" messages in dmesg or popups, however. The game freezes but the audio keeps playing. I have to manually kill NMS. The process usually sits at about 4. Minor things I did notice were slight graphic artifacts.

If I had to describe this artifact, it would be like an occasional snow like effect on panels. Other than that I haven't noticed anything else to document. I didn't collect FPS stats, but It was smooth and seemed to be synced up with my freesync monitor.

I have artifacts and they are not minor. Almost every 3D model has artifacts: either a blueish or whiteish square or noise. Also trees in the distance have a white outline. Here are a couple of screenshots:. I think I only saw that when I was flying. It seems as they were loading they would start out with that white outline and then turn normal the closer I got to them. I'll have to look more closer to see if I'm getting that blueish shadow like artifact on the near by models.

I'm getting a crash while playing the game. Reproducible in about 10 minutes of playing. I don't get crashes here, that said I did have crashes on the first load of a new update a couple of weeks back due to having the nvidia fps overlay still enabled. I've also experienced a little instability with V-sync.

I can confirm those graphical glitches. I have tried the game with and without ACO enabled. So this problem seems not to be related to the compilerbackend.

I know that the problem doesn't exist when an nvidiagpu is used. So my guess is that it has something to do with the RADV driver.

No man's sky uses vulkan as its native API so dxvk is not causing those glitches. I struggled with xid 13s for a long time; I tried different drivers, even changing distro to no avail. I did manage to finally fix it by doing the following:. I can also confirm that this issue exists while running on Arch Linux with Proton 4.

I am using a Vega Unfortunately, this is a game bug and would require us to disable some valid optimization to work around this issue. It doesn't seem that the developers are spending attention on that anytime soon..

Anyone notice the terrain tessellation is quite slow in this game, You can turn around and watch it slowly grow the tessellation cells on the ground in front of you. Is there any hack us linux users can do to speed it up? When using an Ubuntu or derivate of it I am using Linux Mint I cannot get the game to boot at all with any version of Proton, even GE.

What steps should I take to diagnose this? I've already done those steps and I have the latest drivers. I'm on a 6gb. A few weeks ago I had d problem to start NMS, too. But instead of a research for the reason for it I simply deleted teh installation and all steam-directories of the game and completely reinstalled the game.

From this point ist runs without problems no pain for me; reinstalled in less then 40 minutes mbit internet connection. This is certainly not a very factual or professional tip.

But since your VK installation is correct according to your information, I am not left with a factual or technical tip in case of your error message. Where exactly are these error logs stored? I'm on Ubuntu The game just launches and closes with no black screen on Steam, and when trying the Wine Lutris install it gives me that Vulkan error.

Finally got the log to work. I uninstalled everything including steam and all my games. There may be other restrictions involved and you can search for ntfs on this issue tracker to find what others have tried. I use proton with my NTFS drives all the time without issues. I do have several flags set for the partitions tho.

Some of what I have below is probably not needed and does nothing great. Also the compatdata folder needs to be symlinked back to the users. Has the latest update broken the game for anyone else? The game used to work perfectly for me without any changes, but recently the game just freezes up my desktop. All my other games are working as normal so I'm confident nothing has gone wrong with my drivers.

Also reinstalling didn't work. Hello Cybiko , that sounds similar to Can you check if that's what you encountered? It's the Steam Overlay.

ERROR: ld. I haven't tested in-game as I don't own the game, so would be glad if anyone could report back. We won't backport this workaround to mesa stable as it's a bit too invasive, sorry for that. BlazeKl thx for testing. If you are sure, you added the patches it's 6 patches correctly, could you check on the reported application name if it's reporting "No Mans Sky"? Because I'm pretty sure I got the artifacts removed in a renderdoc capture, but maybe the workaround doesn't get enabled for some reason.

When will we get the patch? I am using the oibaf ppa right now. But the artifacts are still visible. Some users reported issues on the Proton 5. It may have only affected users that never ran it on older versions of Proton. In any case, we included a fix for No Man's Sky in 5. It's almost as if the game is being forced into Desktop mode?

I can use the mouse and keyboard to navigate the menus, but my VR controllers are not active. Looks like there is an issue with Proton 5. Hey there. I recently purchased No Man's Sky and I have not been able to get it to run.

When I click the Play button in the Steam Library's interface, the screen goes black for only a second, then the screen returns to the Library UI and the Play button is visible again. From the logs, it throws the following error when the game exits:. I searched for this error in several places to see if any users were having the same issue and, while I did find it for some other games, I did not find any information concerning NMS.

Any help would be appreciated. Thank you. It looks like your Vulkan drivers are at fault. What's your distro, is your system up to date and what's the output of "vulkaninfo"? An upgrade to a newer Ubuntu, Ubuntu Alternatively there's the easier option of some ppas like the padoka ones stable or unstable, take your pick that will update your drivers.

Can you run other vulkan applications like vkcube? I used to use the Padoka PPA as well Therefore I switched to the kisak-PPA. The kisak PPA updates the Mesa drivers to the latest version currently Additionally you should install or update the Vulcan drivers: sudo apt install mesa-vulkan-drivers mesa-vulkan-drivers:i KuJo-Ger Thanks for your post.

And yet still the game won't run. I get the same errors. So, this might lead me down the path that telans and Zamundaaa suggested: a new linux distro. Which one do you like to use? Zamundaaa I'm not familiar with pkcube. I'll have to look into it and get back to you. Just run it in the terminal, it should already be installed. For gaming it's usually best to pick a rather up to date distro, the best options would be Arch, Manjaro, Fedora, Solus but the latest Ubuntu should also be enough as long as you don't want to use new hardware like GPUs soon after launch.

Hello trentchilders , please do not use multiple mesa PPAs at the same time, this is completely untested and may have strange side effects. If you want to test with my PPA, please ppa-purge oibaf's PPA before adding mine, and vice versa if you want to switch back. This is based on the unstable and not yet released Mesa version Currently version This may also be the reason that NMS is not running.

This is e. KuJo-Ger Got it. Thank you so much. I'm at work right now but can try this when I get home. I had multiple PPAs for mesa drivers, which was dumb, but I'm still learning about all of this. Zamundaaa telans kisak-valve Thanks to all of you for replying. I really appreciate it. No Man's Sky runs very well besides a few stutters during cut scenes. The only problem I'm getting is random crashes during gameplay. I'll try capturing the error log but the mouse disappears in the crash window.

The game has now crashed multiple times on entering space. I was able to capture the error log. Alright, here's Proton's log. I found an odd thing with No Man's Sky where the game won't open after like a few minutes.

The game doesn't even open with proton 5. System Info. FuzzyQuills posted on T While walking around on planets, the LOD fade-in effect is corrupted; parts of trees flash slowly on and off as you approach them, billboarded objects flash a noisy box when transitioning to the actual model, base parts flash orange noise on approach, etc.

Haven't seen this reported anywhere at all, with only one reddit comment with a gif showing the artifact as well on a different AMD GPU.

Simply launch the game on the above system configuration. Or for that matter any GPU using the amdgpu driver. Additional note: I am also not sure where else to report this, so apologies in advance if this is in the wrong place. Hello FuzzyQuills , mesa If you're able, please test the game with mesa I swear that was a fix for something else from a long time ago, but duly noted.

Looks like I'll have to work out how to build mesa on Debian Edit: actually never mind, looks like it was submitted to experimental two days ago, will try it soon. Alright, so the fix is definitely working! No more orange flashing. Now that Mesa Thanks a lot! I've never seen issues graphically with No Man's Sky, it may be just with the hardware I've got in my desktop or it has to do with using Arch Linux.

But as I've commented before, there's gaemplay issues. Since the crossplay patch however some planets are rendering invisible when you're far enough away from them. Since this didn't happen before the patch, this could be the game to blame. I sometimes get a momentary freeze when first leaving a planet upon loading my save, but that happens on Windows as well so it's on the game there. I'm assuming you're launching through Steam? Try forcing specifically 5.

I can also give a GE build a go on my end and see if it crashes. The game plays well for me, but there is one new issue as a result of their recent update: TLS 1. TLS 1. Pretty sure Proton already uses 1. Update: deleting the proton prefix and letting it regenerate seems to have fixed multiplayer for me.

I could be wrong, as I've done little investigation into the matter not sure where to start really , but I can say that multiplayer is currently broken for people running Windows 7 and apparently for people running the game via Steam Play.

The only way to play online is to play via Windows 10 for now , I guess. That's what's strange; it only seemed to break for me after a friend tried adding my friend code; online discovery services and uploading bases seem to work, but matchmaking fails. I have a feeling given what I saw on a Steam Community Forum post that in my case adding his friend code should fix mine. Will report back if that does work, as it was working two days ago for me.

Running latest proton 5. That's what's strange; it only broke for me after a friend tried adding my friend code; online discovery services and uploading bases seem to work, but matchmaking fails.

Im not sure this is a Proton issue as much as a NMS issue, when the crossplay update first came out Navi GPU would crash landing on a planet and while its working ok atm its still a known issue regards to Navi. Crossplay is also very wonky atm with bugs to be worked out. I've looked in the proton log and it actually looks like HTTPS in general is completely broken in Proton for some reason; No Man's Sky spams a bunch of "unsupported" messages from the winsock library, and in-game it's saying the matchmaking connection couldn't be made.

New update; finally decided to try downgrading proton, which forced my game's Proton pfx folder to get rebuilt. Soon as I did that multiplayer started working again, which points to an issue with the latest proton and certain prefix setups.

Can someone having issues with multiplayer try deleting the pfx folder for No Man's Sky so it's forced to rebuild it? If that doesn't work, try downloading version 4. That's what I did to get it to work, and after doing that, switching back to 5. Update: just tested deleting and rebuilding with 5. Tested by saving in the space anomaly and just reloading save after altering my Proton install This points to a regression in 5. I may try comparing. Have you tried the latest Proton-GE build, its unofficial but if it fixes issues for anyone then it might be worth looking into which specific patches resolved said issues.

If there is a way to add it to Steam as a valid Proton install to use, I can try it, I don't have experience using GE builds otherwise. Restart steam, look under NMS proton list. It's generally good practice to wipe the game pfx folder between changing major proton versions. Then out of the blue a No Man's Sky patch addressing crossplay bugs broke it on Linux on that version of proton. I wonder what's messed it up.

Going to try this with mine as well, must be a corrupted Proton dist file causing the bug. Just a heads up; make sure to find your NMS save inside the prefix and back it up, as deleting the prefix may cause Steam Cloud to wipe your save.

Wasn't aware of this until I nearly lost my 3 month old save. I had a backup from my Windows partition. Again, seems something is messed up in version 5. Yeah, I noticed the save was in the pfx directory so wanted to avoid deleting it. Reinstalling proton did fix it for me. Let me know your results. Hello FuzzyQuills , Proton 5. What you've described is that the game changes its behavior in a win10 environment. When you run the game with Proton 4.

Given some Windows 10 installs for other people were also failing, my guess is that this is actually a bug in No Man's Sky that also triggers on Proton 5. I assume single player works? Was just having issues with multiplayer. Yeah I'll test MP later tonight, however I don't know anyone to test with so hopefully it just lets you connect to any server.

I think No Man's Sky is actually peer to peer based, so no servers can be picked. If anyone on your friend's list Steam or NMS, doesn't matter plays it, either host a session yourself or get a friend to do so. Just fly into the Anomaly. If you see other people, it works. If you don't see anyone else, it's not.

Can you confirm so that we can remove the "RADV" tag? I'm on Only seems to affect one of my bases as well, others are fine. What fixed multiplayer for me was just switching to Proton 4 from my existing 5 prefix, then back to 5. Everything worked perfectly at that point.

I think Steam also reinstalled the dependencies during this process, which may have something to do with this bug. That's what I initially did when I encountered the bug, then I tried wiping the wineprefix on both versions to see what they did.

Almost lost my save doing that Hadn't played in about 3 months or so and decided to give it another try. Using a fresh install of archlinux, proton, and NMS I kept getting an error message most of the time before I could finish the loading screen.

I managed to fix it by installing vulkan-radeon and uninstalling amdvlk. Now the game works perfectly. When either just amdvlk is installed or both amdvlk and vulkan-radeon are installed the above error appears.

I have posted a screenshot of the error. Finding them on the internet isn't difficult thankfully. A bug with LOD fade was fixed in Mesa I had the amdvlk IDCs installed so I know that wasn't the problem. Must have been a problem with the driver itself.

Also I noticed that there is a new version of amdvlk just released so I'm going to test that and see if it fixes the problem. I will report back. Edit: the new amdvlk works now without crashing. However it seems to have lower FPS than vulkan-radeon provided by mesa. JPLeBreton posted on T Can't play multiplayer since the game's Cross Play Update last month. The older release version of Proton, 4. Note that I can still connect to the game's "discovery services", ie the server that lets players log and see each other's discovered planets, bases, etc, just fine.

I believe that's a whole separate kind of network access. Also guys if you happen to dualboot I do for games that don't run reliably on proton yet -- check system clock, if it's skewed even a little bit multiplayer won't work. Or probably the easier method Set Linux to use local time. I have an issue with No man's sky for now. Few days ago i'm tried NMS, got periodically long time hangs. I've updated my system to latest kernel and issues is gone completely.

But today i have the same issue again. Game periodically every min hangs completely - only sound play. This is true for proton4 and 5 - no any difference. Steam and game reinstall don't help. My system specs and application logs: sysinfo. Net version 4. It shouldn't require anything extra to make it work. Try proton-GE, and perhaps GE Those who're crashing, have you tried a newer nvidia binary?

Seems like I played using The other issue was I had major performance issues where the frame would keep dropping down to fps continuously like a wave depending on where I was looking.. Went back to windows, no issues. Playing this on a Ti. Dropping the texture resolution right down helped somewhat, but not that much. Applying the spoofing fix fixed it right up. Stable framerates and much better performance, with everything set as high as it will go.

Something about the game's Nvidia-specific code path for texture streaming still just doesn't seem to be working right. Just installed proton-ge-custom-bin from AUR today and I'm having a graphical issue with the latest drivers.

Any fixes? You can find the long list of fixes and improvements below. Over the weeks since launch there have been near daily releases between experimental PC and all three platforms. Development has been intense, and very productive. Right now the team is split between high priority bugs, as well as longer term, larger gameplay improvements.

More on this coming soon. Development Update — 1. We'd like to use cookies to help make this site better. If you're happy with this, please accept. Multiplayer Dogfight, race exocraft, build colonies, explore, trade, fight and survive together. VR The entire game playable in virtual reality for a more immersive experience.

Beyond Our 2. Explore In an infinite universe Be the first to land on beautiful, unknown planets teeming with life. Build Base building, anywhere, on any planet Team up to build anything from small outposts to complex multi-planet colonies. Multiplayer Explore, Build and Survive Together Experience up to 32 player multiplayer when you summon the social hub, the Space Anomaly, from anywhere in the universe. Community Join the intergalactic neighbourhood Join one of the thriving community Galactic Hubs, where you and like-minded travellers can create a new frontier.

We'd like to use cookies to help make this site better.