Indigo Renderer Forum

I am not sure whether or not this needs to be supported in Blendigo and Indigo.
CAD models, when exported as .obj contain custom vertex normals (custom split vertex normals in Blender).
This helps reducing render artifacts and can only be worked around to a degree by exporting models with very high polygon counts.

The model in the images below has 21k faces/triangles. The images were created in LuxCore, which only started supporting custom split vertex normals with the latest 2.4 release.

The 1st image is based on a .obj, which includes custom split vertex normals, the second image is based on a .stl without custom vertex normals. The differnce is pretty clear.
When exported from Blender with Blendigo and then rendered in Indigo the result is the same as the second image, regardless whether I render the .obj or .stl.

it should. if you flip normals, refraction will look odd.

but i think the normal has to be on points instead of vertex......

When imported geometry has custom vertex normals, the Object Data Panel in Blender will allow you to clear the Custom Split Normals Data. Otherwise you can add that data. The imported .obj does have custom (split) vertex normals, as expected. The .stl does not, also as expected.

In LuxCore render the results of the .obj and the .stl are what you see in the images. LuxCore render only supports custom vertex normals since the latest release. With Blendigo/Indigo the results for both, .stl. and .obj look the same and look like the 2nd image.

That indicates to me that there is no support for Custom Vertex Normals in Blendigo/Indigo abd unfortunately it "renders" Blendigo/Indigo" as somewhat useless for rendering geometry created originally in CAD software.


I appreciate your response, but I really had hoped for a response from the developers as only they can provide accurate feedback. It is rather disappointing that after more then 3 weeks I don't see any response from the developers.

Maybe you should post an issue on Github: https://github.com/glaretechnologies/blendigo

And I fully concur with you, thinking more users & coders should drop by, sharing pros & cons from their experience, cuz it's an amazing engine (HQ oriented, predictive, capable of proper, scientific, light transport simulation, a kind of which Blender lacks. LuxCore is amazing, but too simplified and cut down in some parts.
After getting more exposure, hopefully devs, see the potential in Blender's user base and do something to better the situation instead of just offering a 'good enough' exporter.

anyway how did you find luxcore speedwise ?

Hm, that's quite relative and subjective issue. Also, speed isn't my priority.

Do you mind sharing your scene?

@pixie, what format do you want this in ?

The original file is in Blender, but I use an external material for the glass ( Lead Crystal form the material DB) and an HDRI for some of the illumination.
I cannot pack these into the Blender file, but can "ship" those with the Blender file, then you'll have to adjusts paths.
I can also send you the Indigo Scene file, but then you can only render one version of the model.
There are three different "models" in the Blender file.
1. Standard Resolution .obj this includes custom split vertex normals, and should provide better render results in Indigo, but does not
2. Standard resolution .stl. This doe not include custom vertex normals and looks exatly like the result rendered in LusxCore
3. High res .stl. This has its own problems and it looks like there is nor normal smoothing.

With the latest release of Blendigo 4.5.0 this issue has been fixed and Blendigo does support Custom Split Vertex Normals!

Headroom wrote: ↑

Thu Apr 15, 2021 3:38 am

@pixie, what format do you want this in ?

The original file is in Blender, but I use an external material for the glass ( Lead Crystal form the material DB) and an HDRI for some of the illumination.
I cannot pack these into the Blender file, but can "ship" those with the Blender file, then you'll have to adjusts paths.
I can also send you the Indigo Scene file, but then you can only render one version of the model.
There are three different "models" in the Blender file.
1. Standard Resolution .obj this includes custom split vertex normals, and should provide better render results in Indigo, but does not
2. Standard resolution .stl. This doe not include custom vertex normals and looks exatly like the result rendered in LusxCore
3. High res .stl. This has its own problems and it looks like there is nor normal smoothing.

Damn, only checked now! Sorry

It would be awsome if you sent in blender and ship those alongside the blender file.

@pixie the issue is resolved as Blendigo now supports custom vertex normals. Do you still want the files ?

if you may

Attached is a zip file containing the Blender file. The main object was exported from a CAD software as a triangulated mesh in two different resolutions as a .obj. The .obj data contains custom vertex normals.
The .stl object has a similar resolution as the lower resolution .obj.

The material on the glass sphere is the Lead Crystal from the material database.
The environment HDRI is from Light Probe Image Gallery

You'll have to adjust the paths accordingly.

Nice model, it just kills my gfx board! xD