It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Hi everyone,
i just bought NMS on gog and found out that immediately after using the scanner i see some weird graphic anomalies, specifically located where there are holes in the ground.
I'm using a Radeon RX 570 and game just runs fine at max settings, but this "bug" is very annoying as it ruins immersion in the game.
I attached an image posted in another forum by another user who apparently had the same issue like me but his post was from one year ago and didn't seem to have a solution.
I hope there is a fix for this and someone can help. I don't feel like playin like the way it is now and will have to ask for a refund otherwise. :(

Thanks to whoever will help
Attachments:
No posts in this topic were marked as the solution yet. If you can help, add your reply
I have the same problem ever since the Pathfinder update. It's very annoying as you cannot really scan for resources.
No driver update nor hotfix, not even the Atlas-update, fixed this. I have never tried rolling back the drivers to an "ancient" version, although on the Steam forum it is suggested that the Radeon Software 16.xxx something fixes the problem. I just don't see a reason to roll back the drivers a year when everything else usually needs the latest drivers. Especially not since I have a fairly modern system, that was not even thought of by the driver properly a year back. I also do not intend to switch driver versions just to play one game, namely No Man's Sky.

My main specs:
AMD Ryzen 7 1700x with chipset drivers v17.30
16 GB DDR4
AMD Radeon Fury Nano (4GB) with latest driver v17.7.2

I just hope AMD or Hello Games will fix this with an upcoming update or driver release, but since this problem is here about half a year, I think it will stay forever. :-(
Post edited August 12, 2017 by Quasebarth
avatar
Quasebarth: ...I have never tried rolling back the drivers to an "ancient" version, although on the Steam forum it is suggested that the Radeon Software 16.xxx something fixes the problem. I just don't see a reason to roll back the drivers a year when everything else usually needs the latest drivers. Especially not since I have a fairly modern system, that was not even thought of by the driver properly a year back. I also do not intend to switch driver versions just to play one game, namely No Man's Sky.
Exactly! Rolling back drivers is never a real solution. I also doubt this is an issue concerning few users so i don't understand how could they not look into fixing it asap or at least inform their customers about this bug and how they are trying to sort it out.
In my opinion if they found out the issue is a responsibility of the video card manifacturer it should be their interest to inform them about it so that a fix can be released, it's called customer service. The standard user wouldn't be able to recognize on his own whether it's a bug depending on devs or video card manifacturer....
avatar
Quasebarth: ...I have never tried rolling back the drivers to an "ancient" version, although on the Steam forum it is suggested that the Radeon Software 16.xxx something fixes the problem. I just don't see a reason to roll back the drivers a year when everything else usually needs the latest drivers. Especially not since I have a fairly modern system, that was not even thought of by the driver properly a year back. I also do not intend to switch driver versions just to play one game, namely No Man's Sky.
avatar
Mightylucius: Exactly! Rolling back drivers is never a real solution. I also doubt this is an issue concerning few users so i don't understand how could they not look into fixing it asap or at least inform their customers about this bug and how they are trying to sort it out.
In my opinion if they found out the issue is a responsibility of the video card manifacturer it should be their interest to inform them about it so that a fix can be released, it's called customer service. The standard user wouldn't be able to recognize on his own whether it's a bug depending on devs or video card manifacturer....
AMD might not be aware of the problem unless Hello Games tells them. There was a pretty good and fast support when the game launched, but after the hype ... I am not sure how this works, but with more than 80% of all graphics cards being none AMD and how many of them still play No Man's Sky? I think the user base is just too small to be recognised, despite even getting an immediate hotfix for such minor, although very annoying, graphic glitch. There seem to be more important fixes needed after the Atlas-update if I look through the Steam forum. Hopefully this graphic bug will finally get on the agenda as well!

With the current history of this glitch, I would not count on a fast solution, maybe you should consider to return the game and get a refund as long as you can. Not an option for me since I bought this game on release, but on the other hand I played it with this bug for a long time now (290 hours on the counter). It's just not the best gaming experience you could have with this otherwise great game and it pisses me off every time I use the scanner.
Post edited August 12, 2017 by Quasebarth
avatar
Mightylucius: Exactly! Rolling back drivers is never a real solution. I also doubt this is an issue concerning few users so i don't understand how could they not look into fixing it asap or at least inform their customers about this bug and how they are trying to sort it out.
In my opinion if they found out the issue is a responsibility of the video card manifacturer it should be their interest to inform them about it so that a fix can be released, it's called customer service. The standard user wouldn't be able to recognize on his own whether it's a bug depending on devs or video card manifacturer....
avatar
Quasebarth: AMD might not be aware of the problem unless Hello Games tells them. There was a pretty good and fast support when the game launched, but after the hype ... I am not sure how this works, but with more than 80% of all graphics cards being none AMD and how many of them still play No Man's Sky? I think the user base is just too small to be recognised, despite even getting an immediate hotfix for such minor, although very annoying, graphic glitch. There seem to be more important fixes needed after the Atlas-update if I look through the Steam forum. Hopefully this graphic bug will finally get on the agenda as well!
That's ridiculous...;) Where did you get the loony idea that AMD GPU users were "Too small" to be recognized? Who told you that, nVidia?...;) FYI, I've used nothing but AMD/ATI since 2002, I own more than 350 games with all currently installed, btw, and some date back 30 years. Guess how many don't run? 0. Just FYI, you might also like to know that all Sony Consoles starting with the PS4 and all XbOnes *also* run nothing but AMD cpus and AMD gpus. I'm guessing you probably did not know that. BTW, the console GPUs are all based on discrete PC GPU designs from AMD. Learning is a wonderful thing...;) So are AMD GPUs--I love my RX-480.

There is a spot in all AMD drivers where users can report problems with specific games--everyone who has an AMD GPU should know where it is.
avatar
Quasebarth: AMD might not be aware of the problem unless Hello Games tells them. There was a pretty good and fast support when the game launched, but after the hype ... I am not sure how this works, but with more than 80% of all graphics cards being none AMD and how many of them still play No Man's Sky? I think the user base is just too small to be recognised, despite even getting an immediate hotfix for such minor, although very annoying, graphic glitch. There seem to be more important fixes needed after the Atlas-update if I look through the Steam forum. Hopefully this graphic bug will finally get on the agenda as well!
avatar
waltc: That's ridiculous...;) Where did you get the loony idea that AMD GPU users were "Too small" to be recognized? Who told you that, nVidia?...;) FYI, I've used nothing but AMD/ATI since 2002, I own more than 350 games with all currently installed, btw, and some date back 30 years. Guess how many don't run? 0. Just FYI, you might also like to know that all Sony Consoles starting with the PS4 and all XbOnes *also* run nothing but AMD cpus and AMD gpus. I'm guessing you probably did not know that. BTW, the console GPUs are all based on discrete PC GPU designs from AMD. Learning is a wonderful thing...;) So are AMD GPUs--I love my RX-480.

There is a spot in all AMD drivers where users can report problems with specific games--everyone who has an AMD GPU should know where it is.
What's wrong with you, stood up on the wrong foot? Intel and nVidia graphics certainly make up 80% of the relevant gaming graphic cards market share (see attached Steam statistic). Having the console GPU on the AMD-side certainly does not help the PC when it comes to driver updates or individual optimisations. At least not in case of No Man's Sky. The GeForce 6800GT (paired with an Athlon XP 2500+) was my last nVidia card and my last Intel CPU was an even more ancient Pentium@166 MHz (with an Riva TNT and 3DFX Voodoo at its side). Cannot be arsed to look when they were state-of-the-art. Ever since then I had complete AMD systems, so don't tell me about hardware history pal. ;-)

It is not my job to hunt and report bugs to AMD and keep track of their repair. Sorry, but I paid 650 € for my graphic card and 60 € for the game, so I might be a bit spoiled when it comes to service that I expect! I usually submit an error once or twice, but this graphic glitch we are looking at in this thread is here for over half a year. Nothing happens and nothing probably will ...

Back on topic:
If you are using No Man's Sky with GOG Galaxy you can opt in the experimental beta branch by using the password: 3xperimental.
I am currently running beta v1.31, but the graphic bug is still the same as expected. Imho it's a AMD problem and they don't seem to fix it anytime.
Some more gameplay oriented problems have been fixed in the beta, like for example that you could not progress in the base building quest line. Still there are many gameplay bugs that have not been fixed yet, like the permanent question mark for discoveries and the alien language that cannot be read, even though you already learned a lot of vocabulary. Some of these bugs maybe related to using an old save game, not starting a new game though.
Attachments:
Post edited August 13, 2017 by Quasebarth
So I think it is time for an update since we are now on v1.34. There is no change (see attached pics)!

I played around with newer AMD Radeon drivers, currently v17.8.2. No change! I cleared the shader cache of AMD driver, as well as No Man's Sky shader cache and game cache. No change!

I have not encountered the severe graphic distortion that some people have or the frame rate drops. The game runs, except for the scanner shader and the lense flare blending effect, absolutely stable and fluid at 60 fps. Probably because my drivers are installed clean and I also always deactivated the AMD optimised shader cache in the driver ever since Pathfinder Update v1.2.

The only thing I don't intend to do is rollback to an ancient driver version, like 16.8.x like some suggested. Another solution might be to use a mod that changes the shader and lense flare effect, but I have not tried it yet. Anybody who wants to give it a try, here are some links that were suggested to work from the Steam forum:
https://nomansskymods.com/mods/ati-radeon-hd-6xxx-crash-fix/
https://nomansskymods.com/mods/toned-down-lens-flare/
https://nomansskymods.com/mods/chromatic-aberration-vignetting-scan-lines-removal-for-altas-rising/

I still think there is something terrible wrong with the scanner shader that can either only be solved by Hello Games or by AMD with an driver update. Although the AMD driver works absolutely stable and flawless on every other game I have. I have sent this thread as a link in a bug-report to Hello Games for further investigation.
Attachments:
Post edited August 27, 2017 by Quasebarth