LuxCoreRender Forums

Asticles wrote: ↑Thu Feb 15, 2018 5:43 pm I've tested with your fist build (from last post) and it renders a big instance when it should'nt.

I can reproduce it.

So it's not crashing anymore?

kintuX, can you test the following BlendLuxCore dev versions? This is the current master (I guess it will crash on your system): https://www.dropbox.com/s/fooqxxttd0tbf8d/BlendLuxCore-win64-ocl.zip?dl=1 And this is a version that does not do framebuffer updates: https://www.dropbox.com/s/7brsp8cw46q...

I found a way to disable Blender's Z-pass by default, so the problem is now solved and the DEPTH AOV is disabled by default

Yes, because it is enabled in Blender by default (in Cycles it's the same). It probably should not be, but if I don't enable it by default, there is a black "Depth" pass in the render result. I can't remove it unfortunately. However if you think it costs too much RAM or so I can disable it...

This is the new menu.
If "Use CPUs" is disabled, native thread count will be set to 0.
If all OpenCL devices are disabled, a warning label is shown. I'll also add a warning in case of hybrid + Metropolis sampler.
edit: with warning:

Dade wrote: ↑Thu Feb 15, 2018 11:42 am but is the management of opencl.native.threads.account available ?

I'll rework the whole thing and make it available.

By the way can the user disable hybrid rendering?
E.g. by setting opencl.native.threads.count = 0?

Me too, can't reproduce any crash.

The "Use CPUs" toggle button is already disabled by default. I could add an info label explaining that CPUs are already used even with "Use CPUs" disabled but I think this will be very confusing. Is it really important to keep this option? I can also add it again if we later noti...

Is it a good idea to hide the OpenCL CPU devices in BlendLuxCore now? (Remove them from UI)

Maybe my build has issues or it's a recently introduced bug.
It's probably best if you revert to the last alpha release for now.

Does it happen with every engine (CPU/OpenCL)?