LuxCoreRender Forums

Odilkhan Yakubov wrote: ↑Fri Jun 14, 2019 9:33 am It will be cool if someone implement this feature to the engine.

Although I am not a software developer and also do not know LuxCoreRender code I assert if there is not any gratis, free, open source software with a smart interface available the method described in the paper takes several months full time work to be implemented, not to mention all the details missing for a proper implementation.

The method is really cool and its results very promising but sorry implementation in LuxCoreRender is currently and in near future
impossible (personal opinion).

FarbigeWelt wrote: ↑Fri Jun 14, 2019 10:48 am

lacilaci wrote: ↑Fri Jun 14, 2019 9:48 am Results aren't that impressive

Are you sure? Did you look at the pictures on p. 125:11 of the paper linked on main post?

I don't see anything I wouldn't see with OIDN from my experience, so I doubt it is worth investing the time on this.

Maybe it could be better in some cases, and if we still had only BCD it would be definitely worth it. What is there to gain now? We have a good denoiser and we would have 2? While still missing key features like displacement for example...?

lacilaci wrote: ↑Fri Jun 14, 2019 11:25 am We have a good denoiser and we would have 2?
While still missing key features like displacement for example...?

This right, there is no need for a second one. And it is not sure that the one of the paper deals better than OIDN in scenes where PIDN fails currently.

I have the same opinion. Implementation of more useful missing features is more important.

By the way this sample based monte carlo denoiser takes at least 600 MB RAM for a 1920*1080 picture and takes estimated at least 3 s. (Estimation is based on paper‘s note that 75 floating point numbers are required per sample, guessing 16 operations per number.)