when you put render and this happens
Blender 2.81a with Luxcorerender 2.3beta1
Forum rules
Please upload a testscene that allows developers to reproduce the problem, and attach some images.
Please upload a testscene that allows developers to reproduce the problem, and attach some images.
Blender 2.81a with Luxcorerender 2.3beta1
- Attachments
-
- Blendluxwhite.blend
- (552.73 KiB) Downloaded 170 times
Full Hybrid Back/Forward path tracing - I don't like clamping - Bidir it's great but very slow - I have 4096 MiB de Vram and I want to cry.
Re: Blender 2.81a with Luxcorerender 2.3beta1
The default light intensities have not yet been tuned after the change of the tonemapper defaults.
In this case the sky is too bright, lower the gain to compensate.
I hope I can improve the defaults before the final release of v2.3.
In this case the sky is too bright, lower the gain to compensate.
I hope I can improve the defaults before the final release of v2.3.
Re: Blender 2.81a with Luxcorerender 2.3beta1
Thanks BYOB
Full Hybrid Back/Forward path tracing - I don't like clamping - Bidir it's great but very slow - I have 4096 MiB de Vram and I want to cry.
Re: Blender 2.81a with Luxcorerender 2.3beta1
IMHO I think it's better to leave the sky values untouched and work with the camera Gain Value, it will make much easier to work with the lights and the sky/sun will feel more natural, I think that at least
Correct me if I'm wrong @B.Y.O.B.
Correct me if I'm wrong @B.Y.O.B.
Re: Blender 2.81a with Luxcorerender 2.3beta1
It doesn't really matter if we tune the sky gain down or the tonemapper gain down.
My goal is to make the lights compatible with Cycles and Eevee by default, so users can switch between the engines seamlessly.
My goal is to make the lights compatible with Cycles and Eevee by default, so users can switch between the engines seamlessly.
Re: Blender 2.81a with Luxcorerender 2.3beta1
When is the 2.3 deadline?