What version of Blender are you using, and what version of the Blender Source Tools are you using? Not that I'll be able to help based on that information, but it would be nice for Artfunkel (the Blender Source Tools' main author) to know.

If two (or more) vertices are at the exact same coordinates, regardless of whether you use DMX flexes or VTA flexes, StudioMDL will only apply flexes onto the first vertex in that location.

So to part lips, the base model must have the lips' vertices at least slightly offset from each other.


It makes "sense" for VTA flexes (they match to the nearest vertex; they're separate from the model's mesh, so they can't say "this vertex moves that way", only "the vertex closest to this point moves that way"), but it's stupid for DMX flexes.

In any case, this is not a bug with the Blender Source Tools plug-in, so you have to live with it.

What happens if you compile that model as a non-static prop model (and/or disable per-vertex lighting calculation for the model in some other way), then re-compile the map?

Pte Jack lähetti viestin:

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

That's wrong; Because that some people (presumably including Valve employees) would have ".bmp" at the end of material/texture names in the GoldSrc days simply to match the image filename, GoldSrc model compilers ignore everything from either the first or the last period and onwards in a material name, and that's carried over for Source model compilers as well.

So a material name of "TopTorso.VMT" in Blender would use "TopTorso.vmt" as the VMT filename, due to first ignoring the ".VMT" part and then adding ".vmt" on the end.

(Likewise, "Foo.Bar" as a material name in Blender would use "Foo.vmt" as the VMT. Edit: And Pte Jack has confirmed that a material name in Blender of "Foo.Bar.Baz" would use just "Foo.vmt" as the VMT when compiled, not "Foo.Bar.vmt".)

Which version of the Blender Source Tools are you trying to use?

The latest version compatible with Blender 2.79 is version 2.10.2. Versions 3.0 and up are not usable in Blender 2.79, instead being meant for Blender 2.80 and beyond.
You can download earlier versions of the Blender Source Tools here: http://steamreview.org/BlenderSourceTools/archives/

All Team Fortress 2 weapons (except for the Spy's invisibility tools) use "C_" models (dubbed so due to the model filenames).
That is, the first-person arms are one model, and then the weapons are another model that is bone-merged onto the former.

Team Fortress 2 used to use "V_" models for the default weapons (those that you have when the item server is unreachable) in first-person (with arms; not bone-merged onto other arm models), "W_" models for the default weapons in the world/third-person, and "C_" models (without arms; bone-merged onto other arm models) for non-default weapons. It has since been updated to use "C_" models in all cases (except for the Spy's invisibility tools), but the "V_" and "W_" models still exist, though they're unused now.



TL;DR: Except for the Spy's invisibility tools, the "V_" and "W_" weapon models are unused. Team Fortress 2 only uses "C_" weapon models bone-merged onto separate "C_" arm models now.

Malovato Budet lähetti viestin:

- ERROR: d:\steam\steamapps\common\team fortress 2\tf\workshop\content\models\workshop\player\items\heavy\hatt\hatt.qc(5): - could not load file 'Collision1.smd' -

This line says that on/around the 5th line in the QC file, you have a reference to "Collision1.smd", but that file doesn't exist beside the QC file.

Malovato Budet lähetti viestin:

I tried to do it, but the compiler show an error

Please try to compile the model again, copy the entirety of the model compile log, and paste it here for us/me to see (preferably between [code] and [/code]).

Which version of the Blender Source Tools are you using? The latest version of it supporting Blender 2.79 is 2.10.2, which you can find and download from the "Blender 2.74+" section here: http://steamreview.org/BlenderSourceTools/archives/

Malovato Budet lähetti viestin:

Ok, then how convert .smd to .phy?

Compile the Source model, in the same manner as if the model didn't have any physics mesh for it. It gets "converted" into a PHY file at the same time as the rest of the QC, DMX, SMD, et cetera files get compiled into MDL, VVD, and VTX files.