Cactus
Published
The game in general is a bit buggy but seems to work great, even with easy atni cheat!
I was skeptic about easy anti cheat being used but the game runs no problems. I was able to play about 5 multiplayer matches without any issues.
While you can play the game using keyboard, a mouse is much better.
Mouse movement causes the game to have performance problems but using the keyboard keys works fine.
Installs fine but unable to load into the game. The ID launcher starts for a few seconds and then closes.
Played the game for over 2 years now and it still runs flawless!
After the recent "Beyond update" this game is completely broke and unstable without tweaks for Nvidia users. First you should modify your TKGRAPHICSSETTINGS.MXML like everyone suggested before by settings the "TerrainTessellation" value to "Low".
Now the crucial part is compiling a hacky work around to spoof your vendorid to be AMD rather than Nvidia. Clone this repo ( https://github.com/volca02/spoof_vendorid ) and compile it. In steam, edit the "Set launch options" for No Man Sky with the value shown on the git repo. Additional info can be found here ( https://github.com/ValveSoftware/Proton/issues/438#issuecomment-522725441 )
Once this is done, I was able to play No Man Sky again perfectly with no crashing or FPS issues for over 10 hours, just like it was before the Beyond update!
Easy Anti Cheat
Game runs fine but you can only do tutorial or practice. Attempting to play online will remove you because of Easy Anti Cheat.
The game runs flawless and has no issues with framerates even with every setting maxed out. The issue is Easy Anti-Cheat, it will kick you out of public games within a minute. I was able to play multiple matches for over an hour with friends in a private lobby though!
Installs and plays fine after increasing vm.max_map_count value. Controller works perfect.
I was able to fix the occasional crashing by increasing my vm.max_map_count value. Most kernel's have this value default set at 65536. You can verify this by running the following command
cat /proc/sys/vm/max_map_count
You can set your vm.max_map_count by running the following command (this only last's until you reboot your system, there is a way to set this value permanently if desired).
sudo sysctl -w vm.max_map_count=2147483642
I found the following value to use at the Arch Wiki
I'm not using any other launch options, just proton expirmental and the vm.max_map_count increase. This seemed to resolve any consistant crashing and I've been able to play consistantly for 40+ hours with very minimal crashing or issues.
