Hi PaQ,

> ... but that's something I allready tried to explain,
> without real succes ...

Hmmm, well I guess maybe don't try to explain the actual cause since that is going nowhere, just give the facts?? Like:


Simple cube exported from MoI - doesn't work properly in Octane.

Simple cube exported from Modo - also doesn't work properly in Octane - this certainly proves it is not anything specific to MoI.

Same cube works properly in every single other renderer...

So that's a pretty significant bug, Octane should be able to render those cubes the same as other renderers are able to.

The cube OBJ files are nice and simple short files without much data in them so eventually he should be able to dig into them and figure out what is going wrong in Octane.


> The model is actally looking like a mess in Octane, inverted
> normal seems indeed inverted ... so somehow ... Octane is
> reading the vertex normal direction from the .obj file.

Hmmm, well it sounds like he is possibly reading them in but somehow only using them for frontface/backface type calculations and not actually for generating the pixel level shading.

That would be quite strange though, because the primary purpose of vertex normals is to be used for shading!

For welded data though, the cube examples seem to show that they are not actually being read in properly for cases where faces have a shared 3D vertex but individual "per-face" normals. In some cases if a program only has lists of data at the vertex level it can have difficulty dealing with per-face type data, that might be one structural problem area.

- Michael