LuxCoreRender Forums

Yes solving this dynamically would be best.

u3dreal wrote: ↑Tue Jan 21, 2020 1:51 pm Yes solving this dynamically would be best.

Unfortunately it has to be implemented in Blender itself, an addon doesn't have the necessary powers.

Oh yes it is part of the define .... that's bad

DLSC and Env. light cache persistence are now supported.

BlendLuxCore can now read some basic Cycles world and light settings. For more info see https://github.com/LuxCoreRender/BlendL ... issues/272

Woahou this is a nice touch !

Thanks BYOB !

This is great, thanks!

Very interesting! Thank you.

There is now a script to convert scenes from v2.2 or before to v2.3, since we had some changes that broke backwards compatibility (see the release logs of v2.3 for details).
You can run the converter with the big button in the new LuxCore Tools panel in the render properties.

Note that if your v2.2 scene had linear tonemapper gain set to 1 and auto tonemapping disabled, the converter can not decide wether these settings were chosen by you or were set because they are the new defaults. It will show a warning in this case and you have to change these settings back to the old defaults (gain 0.5 and auto tonemapping enabled) if necessary.

In case you have many scenes and want to automate the conversion task, you can also call the operator from the console or a Python script:

Just noticed HDRI rotation doesn't match Eevee: BlendLuxCore Hdri Rot = 360 - Eevee Hdri Rot.

Otherwise, the Cycles scene reader is very nice! But in my opinion the "Use Cycles Settings" feature should separates Materials, Lights and Camera.
I hope translucency and texture coordinate + mapping are next on the list!