LuxCoreRender Forums

Indeed, it would be a CPU-only feature

you say that this feature save memory and we can't use for GPU that have this particular issue

Sharlybg wrote: Fri Apr 10, 2020 12:59 pm

Indeed, it would be a CPU-only feature

you say that this feature save memory and we can't use for GPU that have this particular issue

If you can connect your HD to your GPU.

If you can connect your HD to your GPU.

But you say RAM as cache

Sharlybg wrote: Fri Apr 10, 2020 1:19 pm

If you can connect your HD to your GPU.

But you say RAM as cache

Yes, CPU ram is a cache of the HD.

For GPUs, you will need to to use the GPU ram as a cache of the CPU ram and the CPU ram as a cache of the HD ... a cache of cache of cache of cache of cache ....

remind me about centileo render back in 2012 was wondering how that get possible finally the renderer was never really out and well use

https://youtu.be/JZIXlXD5tTM

https://www.youtube.com/watch?v=JA6A0ZXEUl0

Sharlybg wrote: Fri Apr 10, 2020 2:10 pm remind me about centileo render back in 2012 was wondering how that get possible finally the renderer was never really out and well use

https://youtu.be/JZIXlXD5tTM

https://www.youtube.com/watch?v=JA6A0ZXEUl0

Anyway is that really important now that AMD and Nvidia seem to have a built in feature for that ?

AMD HBCC
Nvidia Nvlink or something else i don't remenber correctly.

In this comparison its pretty clear that octane too (like fstorm, corona, vray) clamps just secondary ray intensity. This keeps sharp highlights in glossy reflections and direct lighting mostly intact and providing nicer clean render not just removing fireflies.

Aaand testing octane a bit more it seems fireflies and noise are treated in two steps.

First is clamping(secondary bounces only)
Second is hotpixel removal (as a tonemapping postprocess) this removes some remaining fireflies not handled by clamping.