LuxCoreRender Forums

Dade wrote: ↑Mon Jul 12, 2021 9:27 pm Are you aware you are using the slowest possible settings (not the fastest) ? And it was a proof of concept: a depth of 32 is quite extreme.

P.S. don't use path.maxdepth, it is already exposed in BlendLuxCore (and you are overwriting the BlendLuxCore setting or BlendLuxCore is overwriting your; It depends on the order of definitions).

Was thinking the same just asked on the first post of this page . Thanks for confirmation.

Sharlybg wrote: ↑Mon Jul 12, 2021 12:13 pm Do I need this one

Code: Select all

path.maxdepth = 32

Look like light path value we change inside blender.
Or is something else ?

Would it be possible to implement a setting button inside the blender to select which mode, without having to change the config.py file? So, according to the work, we can choose whether we want more or less quality.

First we should determine the pros/cons of these settings and if the difference is noticeable and what are their effects.

Cluttering the addon for no reason don’t make sense and it would be more work for BYOB for nothing

However I agree that investigating this it’s worth the effort

juangea wrote: ↑Mon Jul 12, 2021 11:24 pm First we should determine the pros/cons of these settings and if the difference is noticeable and what are their effects.

Cluttering the addon for no reason don’t make sense and it would be more work for BYOB for nothing

However I agree that investigating this it’s worth the effort

I fully agree.

I try to only expose engine settings when absolutely necessary, there are already too many.
I think we should first try to find better defaults that work good in all kinds of scenes. Only if the evidence shows that it is sometimes necessary to deviate from these defaults and that this would bring serious benefits, I would consider to expose the settings (maybe in a preset kind of way, with 2-3 good configurations).

Sharlybg wrote: ↑Sat Jul 10, 2021 5:45 pm I think that nowdays there are multiple way to speed up a render engine while being ""fully unbiased""
a recent numerous papers just show. And introducing aggressive bias in engine tend to break lot of code
like bidirectional or light tracing.
I remenber clarissefx have something to filter fireflies without clamping

As I can see Arnold renderer also add support for the FireFly filter too and it is in the Clamp Filtering category. is this the same luxcore clamp option or a different one?

I have done more test with many different RR setting it doesn't change the story.
Even the Default look faster.
So investigation have to be done elsewhere for me about Path tracer only Performance.

Just the first time i found cycles and russian roulette in the same sentence. Like they use probabilistic path termination
But dont know if it is still the case :

https://developer.blender.org/T52313

Anyway just to share.