In Blender, are the vertices of the mesh connected? (Before you do the export?) And how many vertices does Blender say the mesh has before you export?

Originally posted by Zappy:

In Blender, are the vertices of the mesh connected? (Before you do the export?) And how many vertices does Blender say the mesh has before you export?

Yeah they're connected and at the top it says there's 2233 verts

And do you have any mirror or edge split or subsrface subdvision modifiers on the object in Blender?

Don't froget that they are applied on export then StudioMDL triangulates and optimizes the mesh on compile.

So, the actual count in Blender may be different than the actual count on the finished model.

Originally posted by Pte Jack:

And do you have any mirror or edge split or subsrface subdvision modifiers on the object in Blender?

I don't use Blender so I don't even know how to add a modifier. I understand that the count can be different from in Blender the issue is how absurd it is since StudioMDL matches vertices from a DMX based off their indices. It also messes up my importer since it bases smoothing groups off of the indices.

The important thing is that both models have the same number of indices and the same draw count. This means that they render equally quickly. The difference in the number of verts means only that more memory is being used.

As for why the vert count is different, it looks like the Blender tools are doing something that prevents StudioMDL from optimising the size of the vertex buffer. This is presumably something to do with normals, UV co-ordinates, or weights.

Originally posted by Artfunkel:

This means that they render equally quickly. The difference in the number of verts means only that more memory is being used.

https://pastebin.com/FTg1yq1Y
Used a demo so it'd be mostly consistent. I did have to spawn the modle roughly 100 times but this would mean if a team uses DMXs from Blender it will have worse performance than SMD or using another program to export everything.

I'm surprised. There must be a shader doing per-vertex operations seperately from the main render pass? In any case this needs fixing. I'm working on it but it's something of a black box!