LuxCoreRender Forums

Just open this thread to discuss a bit about luxcore default setting. The point is to make the engine adapt with the user workflow.
Why that ?

As you can see luxcore is a very capable engine. It can deliver render of a scientist optical precision. But also be able to fit the need of a 3D visualizer artist who don't necessarly need that kind of precision and the slow speed attatched to it.

When someon will want to simulate Optical Phenomena With Lux by using Bidir engine with insane Value and almost no clamping Aka techinical User.

Some Other Just want to Render nice looking and plausible Products or Archviz/Interior at great speed and ready to pay a given amount of bias introduced by that benefit. Aka Artist User.


Theses twos kind of User Don't really need the same Things. and it is obvious when talking about Lamp default setting.

The Techinical user : need to know all luminance data/ Power / lumens / efficacy from the sun /lamp/area light

The Artist User : Need to have simple value to control no matter the name you give it. the artist want to deal with light power/color/smoothness in a simple language ,And with preset near to the Goal he want to achieve.


It also Obvious when tiping Number in Luxcore interface :

The technical user : need to tip the exact number with the exact metrical value no matter number are estimated in 10000000K or inverse 0.00000001

The Artist User : Need to tip human friendly number that produce almost same visual fidelity. For example :

A clamp value Of 10 to 100 work pretty well with Distant light and Linear tonemapp set to 1 without auto exposure. and it also work well with Lamp/area/spot set by default like this :
Anyway i explane it in Deph here on this post also :

viewtopic.php?f=4&t=942&start=10

If you want only one value for light strength, set power and efficacy to 0 and use only the gain.

B.Y.O.B. wrote: ↑Thu Feb 28, 2019 10:55 am If you want only one value for light strength, set power and efficacy to 0 and use only the gain.

Ok understood thanks for this new infos

But my point is to make it internally.

Also First sample default value is to low it make viewport preview hard to use. I think a value of 16 is a good start. Also i see that big first sample take too much time to disappear. can we reduce this latency ?

Sharlybg wrote: ↑Fri Mar 01, 2019 12:10 pm Also i see that big first sample take too much time to disappear. can we reduce this latency ?

There is parameter for that: rtpathcpu.zoomphase.weight

Dade wrote: ↑Fri Mar 01, 2019 12:14 pm

Sharlybg wrote: ↑Fri Mar 01, 2019 12:10 pm Also i see that big first sample take too much time to disappear. can we reduce this latency ?

There is parameter for that: rtpathcpu.zoomphase.weight

I already set this to 0 in the addon:
https://github.com/LuxCoreRender/BlendL ... ig.py#L147
As far as I understand, this should make the blocky samples disappear as quickly as possible.

I already set this to 0 in the addon:
https://github.com/LuxCoreRender/BlendL ... ig.py#L147
As far as I understand, this should make the blocky samples disappear as quickly as possible.

But if you can make a comparison with cycles viewport performance and responsivness To make luxcore close the gap as much as possible !

Maybe Cycles throws away the samples each time the resolution changes?

Another thing is the behaviour of Luxcore material/texture searching tool. When you click to change a give shader/texture to another one cycles start the search by selecting the current shader/texture name automatically for you.BlendLuxcore doesn't have this behaviour.

Luxcore search mode


Cycles search mode

Another thing is the behaviour of Luxcore material/texture searching tool. When you click to change a give shader/texture to another one cycles start the search by selecting the current shader/texture name automatically for you.BlendLuxcore doesn't have this behaviour.

something about that ?