<div dir="ltr"><div>Thanks very much for the info and quick response. Though it answers my question for the most part, it has created a few more questions for me. Like how then does one find those references to the shared normals? Are they interleaved with the poly indices. I'm not using any collada sdk, so i have to manually find everything using an xml parser.<br><br></div>At the risk of asking too many noob questions, I'd better start digging through the collada wiki some more. Thanks again.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 22, 2016 at 9:47 PM, Gaia Clary <span dir="ltr"><<a href="mailto:gaia.clary@machinimatrix.org" target="_blank">gaia.clary@machinimatrix.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Hi, Khalibloo<br>
<br>
The collada format allows an optimization that only stores unique
normal vectors. Then later the normal vectors can be referenced by
using indexes. Also there can be more than one normal per vertex
since Vertex normals are defined per face AND per vertex. Because of
this the number of normals per vertex can be anything from 0 up to
the number of faces which share the vertex.<br>
<br>
If you are sure that you found a bug, then please file a bug report
and include a demo file that shows exactly where the data goes
wrong. Then we will take care of this of course.<br>
<br>
BTW: If we talk about Blender's built in collada module, then please
note that this is a functionality that was created in C++ and it
uses the OpenCollada library. <br>
<br>
cheers,<br>
Gaia<div><div class="h5"><br>
<br>
<div>On 22.06.2016 21:06, Khalifa Lame
wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div class="h5">
<div dir="ltr">
<div>
<div>
<div>Hello. I recently did some work on collada files
exported from blender. From what I understood from the
collada wiki from Khronos, the mesh normals xml node in
the collada file should contain a trio of number values
for each vertex. In other words, the mesh normals should
have exactly the same number of entries as the vertex
positions.<br>
<br>
</div>
This isn't always the case, however, when you inspect
collada files exported from blender. Sometimes, there are
more normals than vertices; sometimes, there are less. They
hardly ever match.<br>
<br>
</div>
Is this a bug on blender's part? or is this intentional? if
so, could someone please help me understand the logic behind
it and how to read the normals reliably?<br>
<br>
</div>
This doesn't seem like a python question specifically, but if it
turns out to be a bug, I'll have to write a python script to
modify that behavior.<br clear="all">
<div>
<div>
<div>
<div>
<div><br>
-- <br>
<div data-smartmail="gmail_signature">khalibloo®<br>
<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
</div></div><pre>_______________________________________________
Bf-python mailing list
<a href="mailto:Bf-python@blender.org" target="_blank">Bf-python@blender.org</a>
<a href="https://lists.blender.org/mailman/listinfo/bf-python" target="_blank">https://lists.blender.org/mailman/listinfo/bf-python</a>
</pre>
</blockquote>
<br>
</div>
<br>_______________________________________________<br>
Bf-python mailing list<br>
<a href="mailto:Bf-python@blender.org">Bf-python@blender.org</a><br>
<a href="https://lists.blender.org/mailman/listinfo/bf-python" rel="noreferrer" target="_blank">https://lists.blender.org/mailman/listinfo/bf-python</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">khalibloo®<br><br></div>
</div>