LuxCoreRender Forums

kintuX, can you tell us the reason why you don't simply do what I suggested earlier?



Could then be possible to just have a command for load/compile shaders using single GPU w/o running Blender and rendering a scene.

I don't really see an advantage that would have over opening a simple cube ...

I think so, but there might be subtle differences with the floats being stored in Blender properties and passed through Python, etc.

It might be the default epsilon settings that are different between luxcoreui and BlendLuxCore.

Not exposed yet, no.

Dade wrote: Fri Jul 16, 2021 8:07 pm What are you looking exactly for ?

In Cycles it looks like below. It's a mapping with the position in camera space as the output.

moko wrote: Tue Jul 13, 2021 7:00 pm cannot import name 'pyluxcore' from 'BlendLuxCore-master.bin'

It sounds like you just git cloned the repo. Download a release from the release section instead, only those contain the necessary binaries.

The transparent film option is ignored when exporting with filesaver:
https://github.com/LuxCoreRender/BlendLuxCore/blob/274c7a3e79f085239f6a8affb8075dc89ca66e48/export/aovs.py#L68
To enable it, open this file and remove the part "and not utils.using_filesaver(context, scene)".

I don't remember why ...

DionXein wrote: Tue Jul 13, 2021 7:42 am Hm, is there any pool of this new features which need to be expose?

I log them as issues with the tag "enhancement" here:
https://github.com/LuxCoreRender/BlendL ... nhancement

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 ...

You put them in this file at this location: https://github.com/LuxCoreRender/BlendL ... fig.py#L63