Graphical artifacts

Status
Not open for further replies.
RestInPieces

RestInPieces

Refugee
They appear only in A18.0 (not in previous versions) on any mode or graphical setting, only on terrain textures. I don't seem to have any problems with other demanding games or stress/stability tests. Hopefully GPU (rx 5700) is fine. Tried various and latest driver versions.

The artifacts: https://streamable.com/7khpm

Specs: http://speccy.piriform.com/results/rf8HFT5Et71STQBKnKkr6iW

Log: https://pastebin.com/EuRymKhy

Log keeps showing this error, not sure if it's relevant: Detail rendering shaders not found for the active render pipeline, falling back to default shader.

The artifacts also go away if I launch with openGL. However this is not a preferred alternative.

Update: Found many more users on reddit who have the same problem with a 5700 or 5700xt. Here is a video shot by one of them: https://streamable.com/iops3

Update: The problem described in the thread appeared on 18.0, disappeared with 18.1, and came back with 18.2 patch and persists until now.

 
Last edited by a moderator:
As your log says, it's a problem with Unity's renderer not using the correct shaders. Something the devs have to fix on their end.

 
As your log says, it's a problem with Unity's renderer not using the correct shaders. Something the devs have to fix on their end.
Click to expand...
Not sure if this error is the root of that problem because I've seen others in the dev thread mentioning it without mentioning any graphical artifacts. However yes, it's probably (and thankfully) a software issue since a lot of people with the same gpu get it.

 
scrolling down the list i noticed

TimeZone

TimeZone:

GMT +2:00 Hours

Language:

English (United States)

Location:

United States

how can you be in the US if the timezone is GMT +2 ?

 
scrolling down the list i noticed
TimeZone

TimeZone:

GMT +2:00 Hours

Language:

English (United States)

Location:

United States

how can you be in the US if the timezone is GMT +2 ?
Click to expand...
Snooping around my speccy report eh? :p

 
simply for testing purposes. try underclocking to a stock reference card memory and gpu clock speeds. Try say 100mhz or so under and then move up until it doesnt do it. if that works you can just make a profile for just 7days.

This same phenomenon happened with the rx 580 and even the 280 series. a lot of the factory overclocked/superclocked cards had issues.

Note: 7days to die hammers gpu memory.

 
simply for testing purposes. try underclocking to a stock reference card memory and gpu clock speeds. Try say 100mhz or so under and then move up until it doesnt do it. if that works you can just make a profile for just 7days.
This same phenomenon happened with the rx 580 and even the 280 series. a lot of the factory overclocked/superclocked cards had issues.

Note: 7days to die hammers gpu memory.
Click to expand...
Already tried it, would have sent it for rma if the problem went away by underclocking.

 
Already tried it, would have sent it for rma if the problem went away by underclocking.
Click to expand...
it is most likely a vram issue though, given that specific graphical glitch. did upping power limit make it better or worse? imho, especially with gfx cards i usually see if others have same cards and setups that arent having issue. if a handful of others having same issue with same cards it could simply be a bad batch of chips/modules, meaning it could even be affecting different brands and versions of same card and an RMA would usually be from a different lot. by the time a corrected driver that may or may not fix it A40 will be out and your card might be out of warranty. its AMD.

 
Ugh... AMD graphics card strikes again. And ppl wonder why we prefer to pay the premium and go with Nvidia.

I'm sure the devs will fix the issue or AMD will release a new driver eventually... but the point is, you just don't get game support issues like this nearly as often with Nvidia.

 
I have the same issue. But it doesn't happen when in the prefab editor.

Not sure if it happens when you remove the top layer of ground, will test that later (on an older mac).

 
Ugh... AMD graphics card strikes again. And ppl wonder why we prefer to pay the premium and go with Nvidia.
I'm sure the devs will fix the issue or AMD will release a new driver eventually... but the point is, you just don't get game support issues like this nearly as often with Nvidia.
Click to expand...
Not sure about that, had my share of gripes with nvidia as well and driver support isn't all that different. There was virtually no premium price you had to pay with the pascal cards - they were just a great gpu generation compered to the last one, however lack of competition caused nVidia to increase the prices for turing in disanalogy with their performance and that was reflected on their lower market share as well.

Anyhow, I would very much like to have the slightest clue about why this problem is caused, however TFP haven't commented on it yet afaik.

 
Not sure about that, had my share of gripes with nvidia as well and driver support isn't all that different. There was virtually no premium price you had to pay with the pascal cards - they were just a great gpu generation compered to the last one, however lack of competition caused nVidia to increase the prices for turing in disanalogy with their performance and that was reflected on their lower market share as well.
Anyhow, I would very much like to have the slightest clue about why this problem is caused, however TFP haven't commented on it yet afaik.
Click to expand...
i believe bitcoin mining had a greater impact on prices both new and used for nvidia. amd cards were at a premium when they were "better" at it in the early life of mining.

artifacts shouldnt happen at all though meaning the problem is usually never fixed on the dev side. something is pushing a weak limit of the card causing it to display corrupted. this is why if you contact a manuf. directly and tell them you are getting artifacting at stock they usually go straight for a replacement.

nvidia drivers were always and still are generally better stability and perfomance wise because they have more resources to work directly with game devs which is why they are sponsors of more games. They got a little better when they went from ATI to AMD.

 
Artifacts like that are usually what you see on your monitor when a cable is going bad.

If you're seeing it directly from the card, that's usually a sign the caps are failing. It could also just be a bad driver version. ATI cards can do this with Win 10 on some driver versions when you are running more than one monitor. It's also remotely possible that it's a bad power bus to the GPU, and your PSU is actually the issue. a18 does put a lot more demand on the GPU than just about anything else atm.

And Yes, Nvidia has always had better quality drivers with much higher compatibility standards than ATI has. Since even before AMD purchased ATI. Clock speeds don't mean jack if you can't play due to driver issues.

As a workaround, I'd try using the GLCore renderer.

 
Artifacts like that are usually what you see on your monitor when a cable is going bad.
If you're seeing it directly from the card, that's usually a sign the caps are failing. It could also just be a bad driver version. ATI cards can do this with Win 10 on some driver versions when you are running more than one monitor. It's also remotely possible that it's a bad power bus to the GPU, and your PSU is actually the issue. a18 does put a lot more demand on the GPU than just about anything else atm.

And Yes, Nvidia has always had better quality drivers with much higher compatibility standards than ATI has. Since even before AMD purchased ATI. Clock speeds don't mean jack if you can't play due to driver issues.

As a workaround, I'd try using the GLCore renderer.
Click to expand...
Yes, possible causes could be all of the things you mentioned and more. However I'd wager it is a driver problem with 7dtd since everything seems to be ok in stress tests and other more demanding games, and more importantly, since a number of people seem to be having it.

I actually prefer these artifacts to GLCore (videos I have captured show the problem at its worst - when lightning is high on light colored textures).

 
Update: Latest patch fixed the problem. Dying to know what caused it in the first place though.
Click to expand...
My guess? ♥♥♥♥ed up shaders. They must have only tested with NVidia cards, and didn't try AMD's recent ones, so they didn't factor in NVidia's driver deviating from spec all the time when working on them.

 
The problem described in the thread appeared on 18.0, disappeared with 18.1, and came back with 18.2 patch and persists until now. Any educated guesses of what is going on?

 
Status
Not open for further replies.
Back
Top