Optix denoiser imagepipeline plugin
- Odilkhan Yakubov
- Posts: 209
- Joined: Fri Jan 26, 2018 10:07 pm
- Location: Tashkent, Uzbekistan
Re: Optix denoiser imagepipeline plugin
ohh, my apologize. Thanks.
___________________________________________________________________________
LuxCoreRender Developer for Blender
___________________________________________________________________________
LuxCoreRender Developer for Blender
___________________________________________________________________________
Re: Optix denoiser imagepipeline plugin
No need to apologize
Re: Optix denoiser imagepipeline plugin
I have tested a "min spp" property in the OptiX denoiser plugin, but it does not completely solve the issue.
For example, if I raise the min spp until the black squares go away in one particular camera view, they may still appear after moving the camera around. I guess we will have to not use the Normal AOV as you suggested until this bug is fixed in OptiX.
For example, if I raise the min spp until the black squares go away in one particular camera view, they may still appear after moving the camera around. I guess we will have to not use the Normal AOV as you suggested until this bug is fixed in OptiX.
Re: Optix denoiser imagepipeline plugin
First tests with OptiX in the Blender addon: https://youtu.be/xZf1XW9AqRI
Sometimes Blender crashes when ending a render with OptiX, however I don't know yet wether this is caused by the OptiX raytracing part or the denoiser part.
Sometimes Blender crashes when ending a render with OptiX, however I don't know yet wether this is caused by the OptiX raytracing part or the denoiser part.
Re: Optix denoiser imagepipeline plugin
Amazing BYOB
Re: Optix denoiser imagepipeline plugin
Seriously this is realtimeB.Y.O.B. wrote: ↑Sat Aug 01, 2020 2:46 pm First tests with OptiX in the Blender addon: https://youtu.be/xZf1XW9AqRI
Sometimes Blender crashes when ending a render with OptiX, however I don't know yet wether this is caused by the OptiX raytracing part or the denoiser part.
As i told years before eevee is almost dead.
Re: Optix denoiser imagepipeline plugin
Is it already in the daily build?
Re: Optix denoiser imagepipeline plugin
Yes, it should work.
In the user preferences, make sure you are using the CUDA backend, with OptiX enabled, and use a CUDA film device.
Re: Optix denoiser imagepipeline plugin
I assume, just to be clear, this is Optix with RTX hardware (i.e. a slower render will make the Optix denoiser work harder so RTX indirectly helps too). But older GPUs shouldn't be far from this kind of speed too (in this scene).B.Y.O.B. wrote: ↑Sat Aug 01, 2020 2:46 pm First tests with OptiX in the Blender addon: https://youtu.be/xZf1XW9AqRI
P.S. you have RTX accelerating ray tracing and tensor cores accelerating the denoising.
Re: Optix denoiser imagepipeline plugin
Yes, this was done on an RTX 2080.
It feels so fluid that I suspect the denoising time is only a few milliseconds.
This is also why I have so far just put in the denoiser plugin into the imagepipeline, meaning the denoiser runs on every film refresh (very often).
This is not doable with a slower denoiser like OIDN, I tested it, the UI becomes extremely laggy and unusuable (which is why I run OIDN in the background in a separate process).
Indeed, we should decide what to do on slower devices: Do we implement a separate code path where Optix is only run every few seconds, in the background? Or do we just say that users with slower hardware should use OIDN instead?
I tend towards the second option (it would save work and maintenance effort in the future).
However, the existing OIDN denoising could be improved, for example by adding the option to denoise in intervals every few seconds instead of only once when the render pauses.
It feels so fluid that I suspect the denoising time is only a few milliseconds.
This is also why I have so far just put in the denoiser plugin into the imagepipeline, meaning the denoiser runs on every film refresh (very often).
This is not doable with a slower denoiser like OIDN, I tested it, the UI becomes extremely laggy and unusuable (which is why I run OIDN in the background in a separate process).
Indeed, we should decide what to do on slower devices: Do we implement a separate code path where Optix is only run every few seconds, in the background? Or do we just say that users with slower hardware should use OIDN instead?
I tend towards the second option (it would save work and maintenance effort in the future).
However, the existing OIDN denoising could be improved, for example by adding the option to denoise in intervals every few seconds instead of only once when the render pauses.