Odd artifacts during denoise process in Blender 3.5

Support Technical Support
1

Unless I’m missing something, my project isn’t rendering correctly anymore after installing 3.3.0 and the new Nvidia drivers, specifically relating to openimagedenoise. Performing 1280 x 720 test renders with Openimagedenoise has worked fine for the times I’ve been working on my project, but seemingly out of nowhere I’ve started to get strange bright white artifacts even when re-rendering older copies of the project that did not have this issue. It seems to be specifically related to Openimagedenoise, as Optix works without issue but with obviously worse results. Screenshot below:

Blender 3.3.0, Openimagedenoise

openimagedenoisebug
openimagedenoisebug1280×720 172 KB

I hope this issue can be remedied as I really liked the results from Openimagedenoise when it came to render times. Thanks in advance for any advice.

1 Like
2

Hi @Songbearer and welcome!
There is no Blender 3.5 version, so you might want to check exactly what version you are running.

1 Like
3

Maybe you could upload the render without any denoising, too? This way one can look at what it is glitching out on.
Have you tried different combinations on the denoising settings yet?

1 Like
4

That’s what they want you to think :wink: This guy broke into the top security Blender vault and is using the secret Blenders, don’t be surprised if he mysteriously disappears

1 Like
5

No idea where I got 3.5 from, sorry. 3.3.0.

I’ve tried all different combinations on the Openimagedenoise setting and the white artifacts are always present. Here’s it under Optix:

optixdenoisecomp
optixdenoisecomp1280×720 1.27 MB

Which works, but Openimagedenoise is faster and has generally better results for the render. I did a full render of the section of the animation I worked on during the 31st of last month which worked correctly, and re-rendering the project from that day with the same saved settings also includes the artifacts.

If I put the raw noise image in the results, there’s nothing that should lead to artifacts like those. It’s only until the denoise happens - and it’s even worse when that denoised image goes through the compositor, where it’ll turn into glitchy squares.

1 Like
6

And for the final comparison, here’s the noisy image:

noisy
noisy1280×720 472 KB

Please note that before these updates the project rendered without issue - nothing has really changed between the projects other than additional animation keyframes. Lighting, textures, compositor settings and so on are all the same between the two projects.

7

I never had that particular problem so I’ll be shooting blindly. There are couple things I’d try:

  • if you switched Blender version during project check if older version still has artifacts
  • You can try to append all project data to fresh new scene in newest Blender version
  • compare OIDN denoising from properties panel with the one you can do in the Compositor
  • rollback your drivers and test which exact version combination is causing problem
  • do a test copy of your scene and try to find out by removing/simplification which object/combination of objects are causing artifacts
  • clear all orphaned data, and assets that are not in use in your scene ← I’d do that on a copy just to be safe

All of those might be helpful either with fixing it on your side or finding if there is a reproducible bug which can be reported.

3 Likes
8

Thanks for your response. The two things I tried were:

Rolling back my Nvidia drivers and trying the Studio drivers as an alternative. No change.

Rolling back Blender to 3.2. This solved the issue:

blender32render
blender32render1280×720 161 KB

This is using exactly the same project data from the 3.3 release with no alterations made. No artifacts appear and the animation renders as expected. As for the cause? Not a clue! I guess I’ll just stick with 3.2 until 3.3 gets a few updates and see if that fixes it.

9

Really strange considering that OIDN library haven’t been updated :thinking:

If you want to check if this problem is fixed in corrective release you can test alpha (currently 3.4) Blender version.
Here are all bugfixes that are going to be ported to 3.3 LTS:

https://developer.blender.org/T100749

If this bug will not be cached by a developer the only way it can be fixed is if someone report it with reproducible example scene.

2 Likes