Wings 3D Development Forum

Full Version: collada export - wrong normals
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Alas models exported in Collada format have wrong normals.
Yep - almost all of them....
I checked 1.4.1 and 1.5.pre1.78

Here's a cube
[attachment=109]

All normals point straight up. even bottom ones.
Neon22,
Now that I have finally found a free .dae viewer I see what you mean about all the normals pointing up. Maybe someone can figure this one out. I am still having trouble finding time for Wings3d... Sad

Here is a link to the .dae viewer I found... AssimpView

oort
oort, I checked and Wings3d is exporting the right face normals.

Specifically about the viewer, I noticed that if I just export the simple mesh its logs points a error:
Quote:...
Debug, T11292: START `postprocess`
Debug, T11292: FindInvalidDataProcess begin
Error, T11292: FindInvalidDataProcess fails on mesh uvcoords: All vectors are identical
Info, T11292: FindInvalidDataProcess finished. Found issues ...
...
after that, I UV mapped my mesh and the normals was shown right:
[Image: normals_wings_zps8729f748.png]left: without UVs; right: after add the UV mapping;

So, maybe other importers need this too.
Neon22, can you check this?
In which case:
Can I request that the exporter always export vertex normals - even if a face is not UV mapped ?

The face normals are not of much use on their own. Vertex normals are what is used for shading...
I cannot tell much about that because for start changing/adding this I'll need to know about the .dae file format - it should accept this kind of information.

Anyway, you tried to UV map an object, export and check if it can be imported right? If so, at least we will know that UV mapping the object before import it in other 3D app would be mandatory. Please, make this test.

TIA
Micheus