Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

strange artifacts with denoise activated #169

Closed
dirkk0 opened this issue Apr 28, 2023 · 5 comments
Closed

strange artifacts with denoise activated #169

dirkk0 opened this issue Apr 28, 2023 · 5 comments

Comments

@dirkk0
Copy link

dirkk0 commented Apr 28, 2023

Hi!

First of all - thank you for this tool, it's fantastic!

Then: I experimentally switched from Blender 3.3 to the latest 3.5.1.
The good news is - it still works!
The not so good news is: activating the integrated denoiser results in (presumably) mixed up images, like so:
2023-04-28_16-00

Without the denoiser, it looks like that:
2023-04-28_16-01

Doing the same in Blender 3.3 (add plane and icosphere, acivate lightmapper for the whole scene, add denoise) works perfectly.

I wonder why that is?

Thanks again, Dirk

PS: I can provide the files if needed.

@Naxela
Copy link
Owner

Naxela commented May 11, 2023

Hi, thanks for checking this out. There definitely seems to be a bug with the internal denoiser (they've probably changed something between 3.3 and 3.5 related to the compositor). In the meantime, can you check if manually using OIDN works? (Package from here: https://github.com/OpenImageDenoise/oidn/releases)

Thanks again!

Naxela added a commit that referenced this issue May 11, 2023
@Naxela
Copy link
Owner

Naxela commented May 11, 2023

Hi again, I think I might have fixed the issue now - Could you test if it works for you now?

Thanks

@dirkk0
Copy link
Author

dirkk0 commented May 11, 2023

.. man, you're fast! :)
I will test as soon as I'm back on my machine!
thanks!

@dirkk0
Copy link
Author

dirkk0 commented May 14, 2023

works like a charm! thanks!

@dirkk0 dirkk0 closed this as completed May 14, 2023
@victorbnl
Copy link

I had this issue as well. If OIDN can be used as a workaround, shouldn’t this issue be kept open to further investigate on why Blender’s standard denoiser acts like that, and what should be done in consequence?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants