EEVEE: Texture Coordinate Node in world shader render artifacts (AMD) #70004

New Issue

Dan Pastean · 2019-09-18T07:02:44+02:00

Dan Pastean commented

2019-09-18 07:02:44 +02:00

System Information
Operating system: Windows-10-10.0.17758 64 Bits
Graphics card: Radeon RX 580 Series ATI Technologies Inc. 4.5.13571 Core Profile Context 19.9.2 26.20.13003.1007

Blender Version
Broken: version: 2.81 (sub 11), branch: master, commit date: 2019-09-17 19:54, hash: 9609840b5e
Worked: (optional)
stable 2.80

Short description of error
Viewport shading glitches bad when using any HDRI, it doesn't show up in reflections, also using in-build textures like (noise, magic, voronoi etc) produces serious performance drops set to anything other then 2D mode.

Exact steps for others to reproduce the error
see screenshot attached

**System Information** Operating system: Windows-10-10.0.17758 64 Bits Graphics card: Radeon RX 580 Series ATI Technologies Inc. 4.5.13571 Core Profile Context 19.9.2 26.20.13003.1007 **Blender Version** Broken: version: 2.81 (sub 11), branch: master, commit date: 2019-09-17 19:54, hash: `9609840b5e` Worked: (optional) stable 2.80 **Short description of error** Viewport shading glitches bad when using any HDRI, it doesn't show up in reflections, also using in-build textures like (noise, magic, voronoi etc) produces serious performance drops set to anything other then 2D mode. **Exact steps for others to reproduce the error** see screenshot attached ![Capture.JPG](https://archive.blender.org/developer/F7754811/Capture.JPG)

Dan Pastean commented

2019-09-18 07:02:44 +02:00

Added subscriber: @Pastean_Narcis_Dan

blender-admin commented

2019-09-18 07:02:44 +02:00

#70159 was marked as duplicate of this issue

Jeroen Bakker commented

2019-09-18 08:04:53 +02:00

Added subscriber: @Jeroen-Bakker

Jeroen Bakker commented

2019-09-18 08:04:53 +02:00

Please attach a very simple scene that we can use. Rebuilding every scene for every report takes a long time for a developer and will leave less time for actual bug fixing. Thanks for your help!

Please note that there are other related issues with that specific driver. Could you install the previous AMD driver and see if it is also related to 19.9.2 release of the driver.

Please attach a very simple scene that we can use. Rebuilding every scene for every report takes a long time for a developer and will leave less time for actual bug fixing. Thanks for your help! Please note that there are other related issues with that specific driver. Could you install the previous AMD driver and see if it is also related to 19.9.2 release of the driver.

Jeroen Bakker commented

2019-09-18 12:29:06 +02:00

Might be related to #69972 ([OpenGL Driver Bug] X-ray causes viewport artifacts in Edit Mode when using Solid rendering)

Dan Pastean commented

2019-09-19 06:46:34 +02:00

viewport_issue.blend

Actually i`ve isolated the issue, its not driver related as the stable recomended driver from AMD 19.5.2 does the same thing. Its also not an HDR issue because it does the same thing no matter what i plug into the background node, it might be the texture coordonate node. see atached screenshots, also i have no issues with the xray with either drivers

[viewport_issue.blend](https://archive.blender.org/developer/F7757438/viewport_issue.blend) Actually i`ve isolated the issue, its not driver related as the stable recomended driver from AMD 19.5.2 does the same thing. Its also not an HDR issue because it does the same thing no matter what i plug into the background node, it might be the texture coordonate node. see atached screenshots, also i have no issues with the xray with either drivers ![with texture coordonate.JPG](https://archive.blender.org/developer/F7757453/with_texture_coordonate.JPG) ![without texture coordonate.JPG](https://archive.blender.org/developer/F7757454/without_texture_coordonate.JPG)

Jeroen Bakker commented

2019-09-19 08:37:04 +02:00

Issue seems to be related to the texture coordinate node, documentation states that it should work.

Might still be related to AMD Driver, but I am not able to reproduce it on HD620. Will have a look into it later today.

Issue seems to be related to the texture coordinate node, documentation states that it should work. Might still be related to AMD Driver, but I am not able to reproduce it on HD620. Will have a look into it later today.

Jeroen Bakker changed title from ~~EEVEE Radeon bug~~ to EEVEE: Texture Coordinate Node render artifacts

2019-09-19 08:38:00 +02:00

Jeroen Bakker self-assigned this 2019-09-19 08:49:03 +02:00

Jeroen Bakker changed title from ~~EEVEE: Texture Coordinate Node render artifacts~~ to EEVEE: Texture Coordinate Node in world shader render artifacts (AMD)

2019-09-19 10:34:02 +02:00

Jeroen Bakker commented

2019-09-19 11:15:53 +02:00

Issue is introduced by {3a08153d7a842b7ab1e40a9048730e1a3ddab5f7}

Jeroen Bakker removed their assignment 2019-09-19 11:31:08 +02:00

Clément Foucault was assigned by Jeroen Bakker

2019-09-19 11:31:08 +02:00

Jeroen Bakker commented

2019-09-23 08:23:56 +02:00

Added subscribers: @tibor81, @CarlG, @Mets

blender-admin commented

2019-09-24 18:05:14 +02:00

This issue was referenced by c6995b3095

This issue was referenced by c6995b309527835fac3b720c62b6db21ffd7a047

Clément Foucault commented

2019-09-24 18:21:31 +02:00

This is totally a driver bug. I did found a workaround but it is really strange as some other part of the drawing pipeline use the exact same feature and it does not produce unexpected result.

For the record, the issue was that the orco attrib was not bound to any vertex array (which is a valid thing to do, we use it for missing uv/tangent layers).
This seems to work with normal drawcalls but not indirect drawcalls, which is what the driver bug is about.
Note that the orco attrib is not used in the case of background shaders, only by dead code which seems to not be correctly discarded.
Surprisingly, there is no such bug with the uv attrib.

This is totally a driver bug. I did found a workaround but it is really strange as some other part of the drawing pipeline use the exact same feature and it does not produce unexpected result. For the record, the issue was that the `orco` attrib was not bound to any vertex array (which is a valid thing to do, we use it for missing uv/tangent layers). This seems to work with normal drawcalls but not indirect drawcalls, which is what the driver bug is about. Note that the `orco` attrib is not used in the case of background shaders, only by dead code which seems to not be correctly discarded. Surprisingly, there is no such bug with the uv attrib.

Clément Foucault commented

2019-09-24 18:21:47 +02:00

Changed status from 'Open' to: 'Resolved'

Clément Foucault closed this issue

2019-09-24 18:21:47 +02:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

EEVEE: Texture Coordinate Node in world shader render artifacts (AMD) #70004