LuxCoreRender Forums

ok, thanks for the explanation.

Nice. By the way, what happens to the intermediate shapes after the session is started? When doing subdivision + displacement, we have: - original mesh (no longer needed if not instanced) - subdivided mesh (no longer needed) - displaced mesh (needed during render) Maybe more, due to e.g. pointiness....

Dade wrote: ↑Tue Oct 15, 2019 7:34 am

lacilaci wrote: ↑Tue Oct 15, 2019 4:29 am Hopefully this also means the region/border rendering will work much better too

It is not related. It has a different explanation and an easy workaround.

Yes, it is on me (or anyone else who could work on the Blender addon) to fix this in the addon by using LuxCore's subregion.

That earball is hilarious.

happyboy wrote: ↑Mon Oct 14, 2019 7:58 am Can I ask questions about it here?

Better open a github issue in that repo.

Dade wrote: ↑Sun Oct 13, 2019 9:39 pm I was thinking to include hybrid rendering but how to you weights the GPU+CPU performance ?

Hm, true, it's not really suited for a benchmark.

I'll look into it when I have time.

By the way, I also have a version of the wallpaper scene that uses Path OpenCL + light tracing, so it wouldn't have to be a CPU-only benchmark.

Two new scenes:
The good old LuxBall, and some examples for usage of the pointiness feature, by Egert Kanep.
https://luxcorerender.org/download/#ExampleScenes

:D But can we use procedural textures also for displacement? Yes. Note: In LuxCore, displacement is a geometry transformation while (I think) it is a material attribute in Cycles. However LuxCore use one single material with each mesh so it is really only a formal difference. I think in BlendLuxCore...

Dade wrote: ↑Sun Oct 13, 2019 10:30 am BTW, anyone has the the latest version of the LuxBall scene ? It should be included in the collection too.

I have it, I can add it later.