LuxCoreRender Forums

I'm making progress.
Just rendered the first hair generated by the new code (contains bugs though).
10k hairs are exported pretty fast (final numbers + comparison when everything's working again).

You can download the scene here: https://github.com/LuxCoreRender/LuxCor ... chmark.zip
Sorry that it took so long to make it available.

You can always multiply, add, subtract, ... the output of the Depth AOV with Blender compositing nodes if you need to rescale it.

The decimate modifier solution was more for testing. For the final version I also had something like the VRayProxy in mind, where a percentage of triangles is picked randomly. Best way of displaying proxy is however point cloud imho. but I don't think that's doable in blender viewport(or is it?) How...

Looks like the terminator artifact.
From the wiki (bottom of the page):

Unfortunately there is no real solution. You can only try to mitigate the effect by subdividing the geometry further and/or increase the size of the light source that is causing the problem.

I think I'll create a DefineBlenderStrands() function in pyluxcoreforblender that will do the heavy computations in C++. Unfortunately I will have to iterate over each hair in Python because I need to call some Blender functions to get e.g. the coordinates of each hair segment. But I will try to do ...

Hm it seems numpy is already built, there is a file "libboost_numpy34.a" in the target-64-sse2/lib folder. Maybe I have to explicitely link against it somewhere? edit1: ha, found it. I had to rename libboost_numpy34.a to libboost_numpy.a. edit2: now it crashes when I try to extract the num...

I would like to reduce the amount of memory required by the hair export. Currently, we use Python lists to store the segments, points etc. Python lists use doubles as far as I can see. The cyhair used in LuxCore on the other hand uses floats for everything except segments, which use unsigned shorts....

There is no Ambient Occlusion in LuxCore.

What do you mean with "Settings for Depth"?
The Depth AOV contains the distance from the camera in meters.
There are no settings to adjust.

Have observed similar behavior before, issues when Camera or lights are positioned on XYZ (0,0,0), so i checked coordinates. Then, after another change: Spot Light moved on X to 0.01, all went smooth. Nice find, this is most likely the cause. It's probably a bug triggered by numerical precision iss...