Maniphest T93081

Cycles rendering artefacts when camera placed inside volumetric material
Closed, Resolved

Assigned To
Thomas Dinges (dingto)
Authored By
Martin Nancekievill (Nancekievill)
Nov 14 2021, 9:44 PM
Tags
  • BF Blender
Subscribers
Jesse Yurkovich (deadpin)
Martin Nancekievill (Nancekievill)
Thomas Dinges (dingto)

Description

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

Blender Version
Broken: version: 2.93.5, branch: master, commit date: 2021-10-05 12:04, hash: rBa791bdabd0b2
Broken: version: 3.0.0 Beta, branch: master, commit date: 2021-11-02 22:38, hash: 11392829adfe

Short description of error
Cycles produces rendering artefacts for smoke simulation located inside another volumetric material, when the camera is located inside the second volumetric material. If the camera is moved outside the bounds of the second volumetric material, the rendering artefacts disappear.

Exact steps for others to reproduce the error

  1. Select default cube and execute "Quick Smoke"
  2. Duplicate default cube and scale to be larger than the first cube, such that the camera is contained within the duplicated cube.
  3. Enter the shader editor and modify the material for for the second, larger cube:
    1. Delete the "Principled BSDF" shader.
    2. Add a "Principled Volume" shader node, and connect to the "Volume" connector of the "Material Output" node.
    3. Adjust the density of the volume so that original default cube can just be seen.
  4. Run the smoke simulation (artefacts will vary depending on resolution or noise on/off).
  5. [OPTIONAL] Add/amend lights and add background geometry (might help to add contrast and emphasise rendering artefacts)
  6. [EDIT 15/11/2021 14:32 GMT] Set rendering device to GPU.
  7. Go into camera-view and switch to cycles render in the view-port, or "Render Image" (F11).

Interestingly, the artefacts are more exaggerated in Cycles X (Blender 3.0 Beta).

Render artefacts with version 2.93.5:

Render artefacts with version 3.0 Beta:

Render artefacts disappear once camera is moved outside bounds of volumetric region:

Render artefacts with version 2.93.5:

Related Objects

Mentioned Here
rB11392829adfe: Fix T92316: Inconsistent name for Set Curve Tilt node

Event Timeline

Martin Nancekievill (Nancekievill) created this task.Nov 14 2021, 9:44 PM
Thomas Dinges (dingto) added a subscriber: Thomas Dinges (dingto).Nov 15 2021, 8:54 AM

I don't see any artefacts with CPU render, might be GPU only.

Martin Nancekievill (Nancekievill) added a comment.Nov 15 2021, 3:30 PM
In T93081#1253665, @Thomas Dinges (dingto) wrote:

I don't see any artefacts with CPU render, might be GPU only.

Sorry, I should have clarified that. Yes, these artefacts are present when using GPU based rendering.

Martin Nancekievill (Nancekievill) updated the task description.Nov 15 2021, 3:33 PM
Thomas Dinges (dingto) added a comment.Nov 15 2021, 3:33 PM

No problem, I just tested with CPU to check if it happens there too. :)

Jesse Yurkovich (deadpin) changed the task status from Needs Triage to Needs Information from User.EditedNov 27 2021, 10:59 PM
Jesse Yurkovich (deadpin) added a subscriber: Jesse Yurkovich (deadpin).

@Martin Nancekievill (Nancekievill) Are you still having this issue on the latest release candidate build of 3.0? And does this happen if you use CUDA instead of Optix etc? I am not able to reproduce your issue using a 1070 CUDA GPU here, nor when using CPU+GPU rendering.

Note for others: The provided .blend in question has the camera outside the Fog volume. Move the camera inside when attempting to reproduce the issue.

Martin Nancekievill (Nancekievill) added a comment.Nov 28 2021, 8:01 PM

I can confirm that the problem seems to be resolved with version: 3.1.0 Alpha, branch: master, commit date: 2021-11-27 22:09, hash: rBf7f558e293e9

Thumbs up guys! Great job! Thank you.

Thomas Dinges (dingto) closed this task as Resolved.Nov 28 2021, 8:47 PM
Thomas Dinges (dingto) claimed this task.

Great to know that it works for you now! Thanks for getting back to us.