Cycles render artefacts with motion blur turned on #91728

New Issue

Bernhard Engstler · 2021-09-26T16:20:25+02:00

Bernhard Engstler commented

2021-09-26 16:20:25 +02:00

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12

Blender Version
Broken: version: 2.93.4, branch: master, commit date: 2021-08-31 09:23, hash: b7205031ce
Worked: ?

Short description of error
When rendering a certain animated mesh in Cycles and with motion blur turned on, the shader seems completely broken in the render output. Viewport render works without a problem (no motion blur of course). Also, rendering with Optix throws an error and does not work at all, while CPU rendering works but with a broken shader.
GPU rendering with Optix throws the following error:

CUDA_ERROR_ILLEGAL_ADDRESS in cuStreamSynchronize(cuda_stream[thread_index]) (device_optix.cpp:821)

Viewport:

Rendered (CPU):

Exact steps for others to reproduce the error
Open the attached file, ensure that CPU rendering is used (so it does render at all) and render with F12. If the problem does not show at the first try, render with GPU (Optix), switch back to CPU and render again.

SkinShader_RenderProblem.zip

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 472.12 **Blender Version** Broken: version: 2.93.4, branch: master, commit date: 2021-08-31 09:23, hash: `b7205031ce` Worked: ? **Short description of error** When rendering a certain animated mesh in Cycles and with motion blur turned on, the shader seems completely broken in the render output. Viewport render works without a problem (no motion blur of course). Also, rendering with Optix throws an error and does not work at all, while CPU rendering works but with a broken shader. GPU rendering with Optix throws the following error: CUDA_ERROR_ILLEGAL_ADDRESS in cuStreamSynchronize(cuda_stream[thread_index]) (device_optix.cpp:821) Viewport: ![ViewportRender.png](https://archive.blender.org/developer/F10609035/ViewportRender.png) Rendered (CPU): ![RenderOutput_CPU.png](https://archive.blender.org/developer/F10609046/RenderOutput_CPU.png) **Exact steps for others to reproduce the error** Open the attached file, ensure that CPU rendering is used (so it does render at all) and render with F12. If the problem does not show at the first try, render with GPU (Optix), switch back to CPU and render again. [SkinShader_RenderProblem.zip](https://archive.blender.org/developer/F10609102/SkinShader_RenderProblem.zip)

Bernhard Engstler commented

2021-09-26 16:20:25 +02:00

Added subscriber: @B_Engstler

Alaska commented

2021-09-27 03:10:42 +02:00

Added subscriber: @Alaska

Alaska commented

2021-09-27 03:10:42 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'

Alaska commented

2021-09-27 03:10:42 +02:00

I can confirm rendering errors with this model. Even in latest master with the Cycles-X merge.

The issue from testing appears to be with materials when the color having the Skintone attribute in it at some point and a bump node is attached to the material with a high strength. So you can simplify the node setup to something like this and still get issues (you can replace the subsurface scattering node with something else):

Sometimes you don't even need the bump node.

I can also confirm getting errors while rendering with OptiX. Even with the latest master with the Cycles-X merge

I can confirm rendering errors with this model. Even in latest master with the Cycles-X merge. The issue from testing appears to be with materials when the `color` having the `Skintone` attribute in it at some point and a bump node is attached to the material with a high strength. So you can simplify the node setup to something like this and still get issues (you can replace the subsurface scattering node with something else): ![Simplified Node setup.png](https://archive.blender.org/developer/F10621444/Simplified_Node_setup.png) Sometimes you don't even need the bump node. I can also confirm getting errors while rendering with OptiX. Even with the latest master with the Cycles-X merge

blender-admin commented

2021-09-27 17:38:53 +02:00

This issue was referenced by blender/cycles@cbf5c89bae

This issue was referenced by blender/cycles@cbf5c89baeeb39c082542a53bfd49ef88891d985

blender-admin commented

2021-09-27 17:38:53 +02:00

This issue was referenced by 5d8a7ba7de

This issue was referenced by 5d8a7ba7deb39863c60e49bfe694dfde6d3b488b

blender-admin commented

2021-09-27 17:38:53 +02:00

This issue was referenced by 5bea5e25d5

This issue was referenced by 5bea5e25d52fe26b53928781ec0b1f5d4ddf5ad0