Vector displacement suspected to cause geometry artefact and CUDA error #111277

New Issue

Niklas-Becker · 2023-08-18T19:41:42+02:00

Niklas-Becker commented

2023-08-18 19:41:42 +02:00

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23
Edit: Updated GPU driver to 536.99, error still exist.

Blender Version
Broken: version: 3.6.2, branch: blender-v3.6-release, commit date: 2023-08-16 16:43, hash: e53e55951e7a
Worked: 3.5

Short description of error
Blender Versions 3.6.2 and 3.6.1 create black geometry artifacts when rendering with CUDA (Viewport and renderer).
When the file is loaded with the 3.5 version, everything is normal.
3.6.3 crates this error too.

Exact steps for others to reproduce the error
I´ve attached a sample file which creates the error.
Just switch to rendered Viewport and you will see the black artifacts on the table (or see attached screenshot).

After testing we found that:

The black visual artefact is only there if vector displacement node is used.
And the CUDA error only happens when this artefact is seen.

Original description:

I´ve got CUDA to crash when i entered edit mode and selecting the vertices which are part of an artifact.
(Not happening every time)
I´ve attached a screenshot of such a CUDA crash.

The artifacts vanish instantly when you rotate the table the slightest to any direction.
I´ve seen the same artifacts on other objects in other scenes. They seem to only appear on surfaces which are absolutely planar to the YZ plane but this might be a false observation.
CUDA error: "Illegal address in CUDA queue copy_from_device (integrator_shade_surface integrator_sorted_paths_array prefix_sum)" as seen in the crash screenshot.

**System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 536.23 Edit: Updated GPU driver to 536.99, error still exist. **Blender Version** Broken: version: 3.6.2, branch: blender-v3.6-release, commit date: 2023-08-16 16:43, hash: `e53e55951e7a` Worked: 3.5 **Short description of error** Blender Versions 3.6.2 and 3.6.1 create black geometry artifacts when rendering with CUDA (Viewport and renderer). When the file is loaded with the 3.5 version, everything is normal. 3.6.3 crates this error too. **Exact steps for others to reproduce the error** I´ve attached a sample file which creates the error. Just switch to rendered Viewport and you will see the black artifacts on the table (or see attached screenshot). After testing we found that: - The black visual artefact is only there if vector displacement node is used. - And the CUDA error only happens when this artefact is seen. --------- Original description: I´ve got CUDA to crash when i entered edit mode and selecting the vertices which are part of an artifact. (Not happening every time) I´ve attached a screenshot of such a CUDA crash. The artifacts vanish instantly when you rotate the table the slightest to any direction. I´ve seen the same artifacts on other objects in other scenes. They seem to only appear on surfaces which are absolutely planar to the YZ plane but this might be a false observation. CUDA error: "Illegal address in CUDA queue copy_from_device (integrator_shade_surface integrator_sorted_paths_array prefix_sum)" as seen in the crash screenshot.

CUDA Error.blend

1.2 MiB

error artifact.jpg

119 KiB

error.jpg

189 KiB

Niklas-Becker added the

labels 2023-08-18 19:41:43 +02:00

Germano Cavalcante commented

2023-08-18 20:36:21 +02:00

Same problem seen in #92189 and #97633

It looks like it's a GPU driver problem. Users have reported that it has been resolved, but it is still not clear what causes it or how to resolve it.

Please double-check if the drivers are up to date. To upgrade to the latest driver, see here for more information: https://docs.blender.org/manual/en/dev/troubleshooting/gpu/index.html

Same problem seen in #92189 and #97633 It looks like it's a GPU driver problem. Users have reported that it has been resolved, but it is still not clear what causes it or how to resolve it. Please double-check if the drivers are up to date. To upgrade to the latest driver, see here for more information: https://docs.blender.org/manual/en/dev/troubleshooting/gpu/index.html

Germano Cavalcante added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2023-08-18 20:36:30 +02:00

Niklas-Becker commented

2023-08-18 21:58:53 +02:00

I did some more testing:

Updating driver - did not help
Rendering with CPU (AMD RYZEN 5 3600):
- with Open Shading Language: Problem Gone
- without Open Shading Language: Problem still there
My brother tested it on his PC (Same Blender version, same file)
GTX 780, Intel CPU:
- Have seen the same problem with CUDA rendering
- No problem at all with CPU rendering (Open Shading Language on or off)
Shading:
- smooth Shading: Problem gone
- flat Shading: Problem still there

It seems that it is not a single GPU/GPU-Driver problem since it also happened on CPU rendering.

It is only happening on the YZ plane (around X axis).

I did some more testing: 1. Updating driver - did not help 2. Rendering with CPU (AMD RYZEN 5 3600): - with Open Shading Language: Problem Gone - without Open Shading Language: Problem still there 3. My brother tested it on his PC (Same Blender version, same file) GTX 780, Intel CPU: - Have seen the same problem with CUDA rendering - No problem at all with CPU rendering (Open Shading Language on or off) 4. Shading: - smooth Shading: Problem gone - flat Shading: Problem still there It seems that it is not a single GPU/GPU-Driver problem since it also happened on CPU rendering. It is only happening on the YZ plane (around X axis).

Germano Cavalcante added

Status

Needs Triage

and removed

Status

Needs Information from User

labels 2023-08-18 22:25:44 +02:00

YimingWu commented

2023-08-19 06:15:00 +02:00

This looks like a problem with normal attributes and OSL. ~~The black triangle problem is gone after merge by distance, you probably have duplicated faces etc. Try merge by distance and see if it runs correctly on GPU.~~

After a bit testing (CPU render)

The black triangle will still be there even if you move related vertices from and back to its original position.
The material doesn't seem to use any OSL node, but turning on OSL did get rid of this black triangle.

Not sure what is going on with the geometry, could be that material has some div by zero situation going on, but that shouldn't cause CUDA to error like that.

Can't test CUDA for now due to my exceptionally broken nvidia driver on linux...

This looks like a problem with normal attributes and OSL. ~~The black triangle problem is gone after `merge by distance`, you probably have duplicated faces etc. Try `merge by distance` and see if it runs correctly on GPU.~~ After a bit testing (CPU render) - The black triangle will still be there even if you move related vertices from and back to its original position. - The material doesn't seem to use any OSL node, but turning on OSL did get rid of this black triangle. Not sure what is going on with the geometry, could be that material has some div by zero situation going on, but that shouldn't cause CUDA to error like that. Can't test CUDA for now due to my exceptionally broken nvidia driver on linux...

图片.png

139 KiB

YimingWu added

Module

Render & Cycles

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2023-08-19 06:15:27 +02:00

YimingWu added

Status

Confirmed

and removed

Status

Needs Information from User

labels 2023-08-19 06:24:13 +02:00

Niklas-Becker commented

2023-08-19 07:23:02 +02:00

I think i have it narrowed down to the "Vector Displacement" node.
If in this node the "Tangent Space" is selected, the error occurs.
If "World Space" or "Object Space" is selected, the error is gone.

I have changed the sample file so you can reproduce the error.
In the shader settings of the wood material (only white diffuse in there now) you can see this behavior on the Vector Displacement Node.

Somehow there is a UV-map for the object (i cant remember doing this). The faces with the artifacts have a width of zero in the UV-Map editor. When i project a new UV-Map the artifacts are gone.
The weird thing is that this UV-Map is not used in the material. To be sure that it is not used i plugged the "generated UV-map" into the normal input of the shader.

I think i have it narrowed down to the "Vector Displacement" node. If in this node the "Tangent Space" is selected, the error occurs. If "World Space" or "Object Space" is selected, the error is gone. I have changed the sample file so you can reproduce the error. In the shader settings of the wood material (only white diffuse in there now) you can see this behavior on the Vector Displacement Node. Somehow there is a UV-map for the object (i cant remember doing this). The faces with the artifacts have a width of zero in the UV-Map editor. When i project a new UV-Map the artifacts are gone. The weird thing is that this UV-Map is not used in the material. To be sure that it is not used i plugged the "generated UV-map" into the normal input of the shader.

Tangent space.JPG

134 KiB

Vector Displacement Error.blend

1.3 MiB

Object space.JPG

127 KiB

YimingWu commented

2023-08-19 07:29:46 +02:00

Thanks for the investigation... Then this is something that needs fixing in vector displacement.

Still not sure if this caused the cuda error tho, is the cuda error still there?

Thanks for the investigation... Then this is something that needs fixing in vector displacement. Still not sure if this caused the cuda error tho, is the cuda error still there?

Niklas-Becker commented

2023-08-19 08:01:04 +02:00

Just tested it again, the CUDA error is still there and only if the artifacts are seen.

YimingWu commented

2023-08-19 08:50:48 +02:00

Then I guess it's the problem in the vector displacement code.

YimingWu changed title from ~~CUDA queue Error / Black geometry artifacts~~ to Vector displacement suspected to cause geometry artefact and CUDA error

2023-08-19 08:52:27 +02:00

Alaska referenced this issue

2023-08-19 11:17:06 +02:00

Cycles Light Tree: Add case for when an emitter is not selected #111292

Alaska commented

2023-08-19 11:18:08 +02:00

I decided to take a quick look into debugging this issue. This is what I could find so far.

This issue is not necessarily something wrong with the Vector Displacement node.
The issue only occurs (in my testing) when using the Light Tree with the Vector Displacement node. So turning off the Light Tree resolves this issue.

Now onto why.

From a quick look at debugging, when the Light Tree is deciding which light to sample, during one of the calculations, it will pick an emitter_index that is outside the range of viable index. And in doing so, Cycles encounters an assert, and CUDA reports back with an "illegal address" error.

Why is the light tree picking an invalid emitter_index? Due to issues with the Vector Displacement node and the input it is being fed. The Vector Displacement node is causing some NaN normals to appear on the surface (the black spots). And since the light tree uses the normal of the surface for some of it's calculations, various values can end up as NaN and weird code paths can be taken.

So there are two potential areas where this bug can be fixed.

The Light Tree code can be modified to handle these cases better to avoid errors. #111292
The Vector Displacement code can be modified to avoid NaNs fixing both the error and the black rendering. (OSL already seems to do this) #111294

I decided to take a quick look into debugging this issue. This is what I could find so far. 1. This issue is not necessarily something wrong with the `Vector Displacement` node. 2. The issue only occurs (in my testing) when using the `Light Tree` with the `Vector Displacement` node. So turning off the `Light Tree` resolves this issue. Now onto why. From a quick look at debugging, when the Light Tree is deciding which light to sample, during one of the calculations, it will pick an `emitter_index` that is outside the range of viable index. And in doing so, Cycles encounters an assert, and CUDA reports back with an "illegal address" error. Why is the light tree picking an invalid `emitter_index`? Due to issues with the `Vector Displacement` node and the input it is being fed. The Vector Displacement node is causing some `NaN` normals to appear on the surface (the black spots). And since the light tree uses the normal of the surface for some of it's calculations, various values can end up as `NaN` and weird code paths can be taken. So there are two potential areas where this bug can be fixed. 1. The Light Tree code can be modified to handle these cases better to avoid errors. #111292 2. The Vector Displacement code can be modified to avoid NaNs fixing both the error and the black rendering. (OSL already seems to do this) #111294

👍 4

Alaska referenced a pull request that will close this issue

2023-08-19 12:35:18 +02:00

Fix #111277: NaN in Vector Displacement leading to render errors #111294

Sergey Sharybin referenced this issue from a commit

2023-08-21 15:22:13 +02:00

Fix #111277: NaN in Vector Displacement leading to render errors

Sergey Sharybin closed this issue

2023-08-21 15:22:14 +02:00

Blender Bot added

Status

Resolved