BlendLuxCore Development
Re: BlendLuxCore Development
Yes solving this dynamically would be best.
check out my newest stuff http://q3de.com/research/
portfolio http://q3de.com/
MB Pro i7 2.3Ghz, IrisPro 1.5GB, GTX750m 2GB - BigSur
Xeon X5650@4Ghz, RX 5700 - BigSur , Windows 10, Ubuntu 20.04
portfolio http://q3de.com/
MB Pro i7 2.3Ghz, IrisPro 1.5GB, GTX750m 2GB - BigSur
Xeon X5650@4Ghz, RX 5700 - BigSur , Windows 10, Ubuntu 20.04
Re: BlendLuxCore Development
Unfortunately it has to be implemented in Blender itself, an addon doesn't have the necessary powers.
Re: BlendLuxCore Development
Oh yes it is part of the define .... that's bad
check out my newest stuff http://q3de.com/research/
portfolio http://q3de.com/
MB Pro i7 2.3Ghz, IrisPro 1.5GB, GTX750m 2GB - BigSur
Xeon X5650@4Ghz, RX 5700 - BigSur , Windows 10, Ubuntu 20.04
portfolio http://q3de.com/
MB Pro i7 2.3Ghz, IrisPro 1.5GB, GTX750m 2GB - BigSur
Xeon X5650@4Ghz, RX 5700 - BigSur , Windows 10, Ubuntu 20.04
Re: BlendLuxCore Development
DLSC and Env. light cache persistence are now supported.
Re: BlendLuxCore Development
BlendLuxCore can now read some basic Cycles world and light settings. For more info see https://github.com/LuxCoreRender/BlendL ... issues/272
Re: BlendLuxCore Development
Woahou this is a nice touch !
Thanks BYOB !
Thanks BYOB !
Re: BlendLuxCore Development
This is great, thanks!
Re: BlendLuxCore Development
Very interesting! Thank you.
Re: BlendLuxCore Development
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:
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:
Code: Select all
bpy.ops.luxcore.convert_to_v23()
Re: BlendLuxCore Development
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!
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!