LuxCoreRender Forums

I think due to the way IEEE floats are specified, you will always have "bad spots" in the coordinate grid.

Your stuff is exactly at the world origin. This causes floating point precision problems.
Solution:
- move everything a bit
- or change the min. epsilon (multiply it by 10)

Happy new year!

This mesh contains custom split normals data, this is indeed not yet supported by the BlendLuxCore addon.
You can disable auto smooth and add an edge split modifier instead as a workaround.

Volo wrote: ↑Mon Dec 31, 2018 3:26 pm @B.Y.O.B. This time I used v2.1, but Autosmooth is still not working So I added extra loops to the mesh.

Can you post a test scene that shows the problem?
Maybe we misunderstand each other? I'm talking about the setting in the mesh properties:

This is a question for Dade.
I could only find out that irradiance is generally given in watt per square metre, while 1 lux is 1 lumen per square metre. Not sure what LuxCore uses.

Point lights are not intersectible since they are a point. So they are invisible to the camera.
You will need meshlights/arealights.

Yes, I also noticed, the forum and the wiki are lacking a favicon (main page has one).
I think only Dade has the admin rights to fix this.

Nice image

Volo wrote: ↑Sun Dec 30, 2018 3:57 pm Hope there will be a denoiser and support for auto smooth soon.

Both features are available in the latest beta versions of the upcoming version 2.1 - see the news section for download links.

Why does FreeCAD exports a .lxs file when all examples in the scene directory are built around a .cfg file where the geometry are stored in separate .ply files? Are there any special advantages using a .lxs file? The FreeCAD exporter seems to be very old. LXS was the file format of the old LuxRende...