neumond
commented
7 years ago Hello @acqu
Yes, vertex duplication is kinda by design. Speaking more strictly, it's a requirement of .md3 format: every vertex can have only one texcoord. With cube example, vertices have 3 texcoords for every plane they share. Script has to duplicate vertex coordinates to be able to export texcoords correctly.
When you import, it takes vertices "as is", so you can weld them in blender if you want. Probably I can weld them automatically on import. Need to take a look here.
Regarding max vertices, it's merely a warning, since the specification defines some limits. If your game engine supports more vertices - just feel free to overcome these limits.
mino-git
Hello neumond,
i once wrote about this but got no answer. Basically, your script produces new and unneeded vertices.
Example: make a simple cube with all the settings needed, then export, then import again into Blender. You will see the vertex count trippled.
The core problem is, that md3, as well as mdc, for which i wrote a plugin right now, needs each vertex to be mapped exactly once to the uv map.
I wrote a script, as i said above, for the mdc file format. Check this here: https://github.com/acqu/wet-blender-mdc/commit/55cf892135dd2cf8689d8b511fa8c258eea3308e
I hope this helps, and you can integrate this code, cause sometimes i hit a max vertices count with your import/export script, and generally i think this vertex growth is too much and it seems random. Can you explain why you do this? Or if it really matters? Would be interested on your opinion. Cheers.