When you compile, Studiomdl optimizes the model and it tris it. (which is why imported decompiled SMDs are always triangled mesh.) Have you tried triangulating the mesh before exporting it?

(in Face Mode, Select all faces and then use the Quads to Tris function in the Face Menu option)

What does that exported SMD/DMX look like if you re-import the export back into Blender?

Also, try the recompile after converting quads to tris.

Correct...

to fix the problem, remove your edge split modifier(or turn it off), check your original mesh for doubles and internal faces and incorrectly connected vertexes. Clean up the mesh then reapply your edge split. Re-export and recompile.

I'm working a similar problem here with the roof on this train locomotive. I created the problem while indenting the ribbing using mirror and edge splits modifiers and applying them. It really pooched things up. LOL

https://i.imgur.com/U6nT3vP.png

Only a suggestion...
Check inside your model for hidden faces. You may have joined a couple of opposing verts creating faces inside the mesh..

Edit, also check for non manifold vertexes, you may have disconnected doubles.

I just noticed where you posted this topic and this isn't really a BleST problem, you should have posted in the FUSE discussion area. But look at these, they may help you under stand the other picture I posted.

Because I don't know what export options you selected when you created your OBJ File from Fuse

https://psteamcommunity.yuanyoumao.com/sharedfiles/filedetails/?id=1888533870

https://psteamcommunity.yuanyoumao.com/sharedfiles/filedetails/?id=1888539226

And because I don't know what version of Blender you're using...

https://psteamcommunity.yuanyoumao.com/sharedfiles/filedetails/?id=1888595293

This is how materials and textures work in SFM.

https://psteamcommunity.yuanyoumao.com/sharedfiles/filedetails/?id=1528003376

Check Blender to see how the materials are named then either rename them to what you want to name your VMTs or rename the VMTs to what they are named in Blender.

Tested your theory Zappy, again, I stand corrected. But, to avoid confusion, for simplicity sake and in my humble opinion, one should not use name.ext or name.something.ext in material names in Blender.

https://psteamcommunity.yuanyoumao.com/sharedfiles/filedetails/?id=1881466325

Yes, the same as the VMT filename you want to use (without the .VMT extension)

For example:

If you don't want to change the name of the material in Blender, (the TT in your picture) then the VMT that calls the texture has to be called TT.vmt

If you change the name of materials in Blender (again using the TT material in your picture)
and you rename the TT to say TopTorso,
then your VMT has to be named TopTorso.VMT...

If you renamed the material in Blender to TopTorso.VMT,
then your VMT would have to be named TopTorso.VMT.VMT

_nr" (NR?) Not just N in the normalmap filename???

BUT, that being sad, Select your object in Blender and look at the Materials tab. Is your Material name there Material or is it TableClock ? If it is still Material you have to change the name in Blender to TableClock and make sure the vertexes in the UVMap are ASSIGNed to that Material.

This is how the relationship between Blender and Valve models work

https://psteamcommunity.yuanyoumao.com/sharedfiles/filedetails/?id=1528003376

Once that is done, re-export the model and recompile.

Somewhere during the import sequence, python could not find something and create a type ='None' which doesn't have a data type and the python script bailed.

We can't help you with this error without a lot more detail. Like the qc itself, where you have the source smd/dmx files on your computer, etc. and whether or not you have the source files in the proper folder for the qc to find them. (If they aren't, that would cause this error.)

upload your images to a photo service like imgur.com and provide links here.