I think for the denoiser to work it needs to operate on the whole image. I would suggest rendering it with DR instead of deadline tiles.
Set the denoiser to only generate render elements. Then render, and let your draft/jigsaw job re-assemble everything. Then run a VDenoise (standalone denoiser) job over that. The Standalone denoiser does a better job anyway, as it can use multiple frames (+/-1 frame is typically adequate), and this works with Deadline’e frame dependencies if you set it up to include adjacent frames when calculating pending frames.
Of course this method uses a lot of disk space…
It can also easily double your overall render times.
How so? I have never seen that. I guess if your frames render fast and your denoise takes a while because you have big frames, or lots of layers/render elements?
Is vdenoise slower than using the Intel denoiser? I prefer to use no denoiser at all if the render times work.
The standalone denoiser is as fast as the build in denoiser;)
Hey, this might be a solution for stills. But with Vray 5.2 it worked fine. Standalone Denoiser might be the solution now
Standalone denoiser is best for animations, as it can take into account the adjacent frames. It is also good if you might want to tweak the denoising amount after the render (of course you can also keep the un-denoised data and blend that).
It can be a pain to deal with, though, and if your per frame render time is fast then the additional overhead of another denoising pass could add significantly to the overall render time. We have a few nodes with some older (1080/2080 generation) GPUs that are just used for the denoising and I/O tasks, and using Deadline frame dependencies they can be processed in parallel as the render progresses.
