Cycles Regression: Modifying objects in the rendered viewport in certain ways leads to artifacts #91999

New Issue

Alaska · 2021-10-07T07:32:48+02:00

Alaska commented

2021-10-07 07:32:48 +02:00

System Information
Operating system: Linux-5.14.0-1-amd64-x86_64-with-glibc2.32 64 Bits
Graphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.63.01

Blender Version
Broken: version: 3.0.0 Alpha, branch: master, commit date: 2021-10-07 04:35, hash: eadbacdbb0
Worked: Prior to 04857cc8ef (identified by bisecting)

Short description of error
When modifying objects in certain ways with in the Cycles rendered viewport with GPU compute (Currently tested with CUDA and OptiX) leads to some graphical issues until the rendered viewport is reset. This issue does not appear to affect CPU rendering.

Exact steps for others to reproduce the error

Create a default scene.
Change the render engine to Cycles and change to GPU compute, currently CUDA and OptiX work for reproducing this sort of issue for me (the issue manifests different between CUDA and OptiX)
Enter the Cycles rendered viewport.
Select the default cube, give it a sub-division modifier with 6 levels
Apply the sub-division modifer.
Enter edit mode on the cube and use the To Sphere operation with a value greater than 0.
You should now notice a rendering artifact on the sphere. This issue will go away if you change back to something like solid mode in the viewport, then back to the Cycles rendered viewport.

Here is a video demonstrating this issue with a RTX 3090 (information at the top of the page) using OptiX.
Cycles rendering artifacts.mp4

**System Information** Operating system: Linux-5.14.0-1-amd64-x86_64-with-glibc2.32 64 Bits Graphics card: NVIDIA GeForce RTX 3090/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.63.01 **Blender Version** Broken: version: 3.0.0 Alpha, branch: master, commit date: 2021-10-07 04:35, hash: `eadbacdbb0` Worked: Prior to 04857cc8ef (identified by bisecting) **Short description of error** When modifying objects in certain ways with in the Cycles rendered viewport with GPU compute (Currently tested with CUDA and OptiX) leads to some graphical issues until the rendered viewport is reset. This issue does not appear to affect CPU rendering. **Exact steps for others to reproduce the error** 1. Create a default scene. 2. Change the render engine to Cycles and change to GPU compute, currently CUDA and OptiX work for reproducing this sort of issue for me (the issue manifests different between CUDA and OptiX) 3. Enter the Cycles rendered viewport. 4. Select the default cube, give it a sub-division modifier with 6 levels 5. Apply the sub-division modifer. 6. Enter edit mode on the cube and use the `To Sphere` operation with a value greater than 0. 7. You should now notice a rendering artifact on the sphere. This issue will go away if you change back to something like solid mode in the viewport, then back to the Cycles rendered viewport. Here is a video demonstrating this issue with a RTX 3090 (information at the top of the page) using OptiX. [Cycles rendering artifacts.mp4](https://archive.blender.org/developer/F10834599/Cycles_rendering_artifacts.mp4)

Alaska commented

2021-10-07 07:32:48 +02:00

Added subscriber: @Alaska