Viewport Optix glitches #85148

New Issue

ML · 2021-01-28T11:59:47+01:00

ML commented

2021-01-28 11:59:47 +01:00

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

Blender Version
Broken: version: 2.91.2, branch: master, commit date: 2021-01-19 16:15, hash: 5be9ef4177
Worked: (newest version of Blender that worked as expected)

Short description of error
There is a big difference in rendered preview with the optix denoiser between version 2.83.10 and 2.91.2. As you can see at the picture below, 2.83.10 do ton render glitches in the darker background. But the same scene with same optix denoiser in viewport does.
2.91.2

vs
2.83.10

Exact steps for others to reproduce the error
The only special thing in the scene is the area light with the power of (- 1 MW) .. yes minus one megawatt for generating darker places. Other is basically standard, some emissions and area lights.

there is the file I am working with. Tried even with the geforce rtx 3080 - same problem. Optix_err.blend

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: GeForce RTX 2070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.09 **Blender Version** Broken: version: 2.91.2, branch: master, commit date: 2021-01-19 16:15, hash: `5be9ef4177` Worked: (newest version of Blender that worked as expected) **Short description of error** There is a big difference in rendered preview with the optix denoiser between version 2.83.10 and 2.91.2. As you can see at the picture below, 2.83.10 do ton render glitches in the darker background. But the same scene with same optix denoiser in viewport does. 2.91.2 ![2912.png](https://archive.blender.org/developer/F9602388/2912.png) vs 2.83.10 ![28310.png](https://archive.blender.org/developer/F9602390/28310.png) **Exact steps for others to reproduce the error** The only special thing in the scene is the area light with the power of (- 1 MW) .. yes minus one megawatt for generating darker places. Other is basically standard, some emissions and area lights. there is the file I am working with. Tried even with the geforce rtx 3080 - same problem. [Optix_err.blend](https://archive.blender.org/developer/F9602420/Optix_err.blend)

ML commented

2021-01-28 11:59:48 +01:00

Added subscriber: @MarcelLegindi

Robert Guetzkow commented

2021-01-28 12:08:44 +01:00

Added subscriber: @rjg

Robert Guetzkow commented

2021-01-28 12:08:44 +01:00

That looks like quite a significant difference. Could you please provide a minimal example file that demonstrates this issue? This allows all triagers and developers to investigate the issue on a common basis.

Robert Guetzkow commented

2021-01-28 12:09:06 +01:00

Changed status from 'Needs Triage' to: 'Needs User Info'

ML commented

2021-01-28 12:35:46 +01:00

With the final render - after you click on the render button the glitches is created by normal input (denoising - input passes - Color + Albedo + Normal). If you set ( Colo r) or ( Color + Albedo ) glitches are away - so the normal input is the problem I guess.

Robert Guetzkow commented

2021-01-28 13:55:11 +01:00

@MarcelLegindi I'm slightly confused by your description. Does the issue happen for you in the viewport or in the final render (or both)? OptiX denoising is only enabled for the viewport in your project file, but the Denoise compositing node you are referring to in your last comment only affects the final render.

@MarcelLegindi I'm slightly confused by your description. Does the issue happen for you in the viewport or in the final render (or both)? OptiX denoising is only enabled for the viewport in your project file, but the *Denoise* compositing node you are referring to in your last comment only affects the final render.

ML commented

2021-01-28 15:04:38 +01:00

Well, the issue is the viewport, there is the problem primarily. But secondary the same problem has the final render when you using in denoiser(Optix) Input Passes Color+ Albedo + Normal.

Robert Guetzkow commented

2021-01-29 12:38:37 +01:00

Added subscribers: @pmoursnv, @Stefan_Werner

Robert Guetzkow commented

2021-01-29 12:38:37 +01:00

I am able to reproduce the issue in both the viewport and the final render. For denoising the final render I have:

Enabled Render Properties > Sampling > Denoising > Render
Set the denoiser to OptiX
Enable View Layer Properties > Denoising and set the Input Parameters to Color + Albedo + Normal

Using Color + Albedo only appears to produce a better result. The resulting effect is consistent for 2.90 and later, so this doesn't appear to be a regression. The artifacts still appears when removing the area light with negative power and reducing the power of the other area lights.

Perhaps this is a case that isn't handled well by OptiX and much better by OIDN or there is genuinely an issue. @pmoursnv @Stefan_Werner your input would be welcome.

There appears to be a bit of a confusion about the different denoising options though. The entire compositor setup appears to be unrelated, but also incorrectly setup. If you use the Image socket from the Render Layers node as input to the Denoise node and have OptiX denoiser enable for the render, you are denoising it twice, once with OptiX and once with OIDN. If you want to use the Denoise node for Open Image Denoise, enable to Denoise Data pass in View Layer Properties > Passes > Data then connect the Noisy Image, Denoising Normal and Denoising Depth from the Render Layers node to the Image, Normal and Albedo sockets of the Denoise node.

I am able to reproduce the issue in both the viewport and the final render. For denoising the final render I have: - Enabled *Render Properties > Sampling > Denoising > Render* - Set the denoiser to OptiX - Enable *View Layer Properties > Denoising* and set the *Input Parameters* to *Color + Albedo + Normal* Using *Color + Albedo* only appears to produce a better result. The resulting effect is consistent for 2.90 and later, so this doesn't appear to be a regression. The artifacts still appears when removing the area light with negative power and reducing the power of the other area lights. Perhaps this is a case that isn't handled well by OptiX and much better by OIDN or there is genuinely an issue. @pmoursnv @Stefan_Werner your input would be welcome. There appears to be a bit of a confusion about the different denoising options though. The entire compositor setup appears to be unrelated, but also incorrectly setup. If you use the *Image* socket from the *Render Layers* node as input to the *Denoise* node and have *OptiX* denoiser enable for the render, you are denoising it twice, once with OptiX and once with OIDN. If you want to use the *Denoise* node for Open Image Denoise, enable to *Denoise Data* pass in *View Layer Properties > Passes > Data* then connect the *Noisy Image*, *Denoising Normal* and *Denoising Depth* from the *Render Layers* node to the *Image*, *Normal* and *Albedo* sockets of the *Denoise* node.

Robert Guetzkow commented

2021-01-29 12:39:50 +01:00

Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'

ML commented

2021-01-29 12:42:45 +01:00

Yes compositor is not cleaned, my bad, sorry about that, I tested different setups to avoid the problem and one of them was to turn off denoiser at all and use denoising in the compositor. I left it untouched. Sorry again

blender-admin commented

2021-01-29 13:35:00 +01:00

This issue was referenced by 9f89166b52

This issue was referenced by 9f89166b52b1de880c14847a1d0cd830d7c83f5b

Patrick Mours commented

2021-01-29 13:42:42 +01:00

Changed status from 'Needs Developer To Reproduce' to: 'Resolved'

Patrick Mours closed this issue

2021-01-29 13:42:42 +01:00

Patrick Mours self-assigned this 2021-01-29 13:42:42 +01: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

Viewport Optix glitches #85148