Even more bug reports? Okay... So yeah, if I have a group of mesh objects, go set the type of flexes to advanced (by supressing the group in the export panel), and click the generate button thing, go to the text editor, and select the generated flex thingie, it's almost blank. There is some stuff there, but nothing for the actual flex(es) in the mesh. If I ungroup the mesh, and then generate a new block of flex stuff, I can then gain access to the flex' controls, like wrinkle scales and such.
(Not that it matters, though, as grouped objects can't get advanced flexes anyway...?)

Edit: Finally got the link url stuff right.

So many bug reports in a row, huh? Oh, well, if I have a grouped .dmx (8 mesh objects, all grouped to "vz_mare"), I can't set the flex type (simple/advanced) for it (3 of the mesh objects have shapekeys), unless I tick the "Supress" box. (Yes, I have tried selecting a mesh with a flex. Didn't work. It neither worked when I clicked one of the meshes in the "Group properties".) So what if I want to export 1 grouped .dmx with advanced flexes rather than 8 different .dmx files? Is that just impossible, or...?

More randomness. Anyways, if I import an .smd mesh and .vta flex for the mesh, the shapekey in Blender may not always be correct (actually very rarely, if ever), even though the compiled model would look fine in the Source Engine.
Some vertices do move as intended, but it's far away from all.
Does the Source Tools look for if a .vta vertice is exactly at where a mesh vertice is? (StudioMDL looks for .vta vertices which are at most about 1/16th (0.0625) of a unit away, leaving very slight support for out-of-reach vertices. Maybe the Source Tools has 0% tolerance for out-of-reach vertices?)
If screenshots are required, just ask, and I can get some.

Dun dun dun. Randomness. But seriously, though, if I export a .dmx (Engine Path is directed at the FilmMaker), the armature "object name" thingie is correct... but if I import that .dmx, re-export it, and re-import it, the armature's "object name" will be set to the "root" mesh object's name (or first-selected mesh?).
If I for example have vz_mare as first mesh, then some more things (vz_mare_tongue, eyel, eyer, and such, stuff like that), how do I make the armature be named "vz_mare_bones" instead of "vz_mare", making the "vz_mare" mesh object become "vz_mare.001"?

Alright. (You can also just make the "proof-of-concept" in Blender, if you had the models required for it.)

That didn't answer my "why make a Source engine model" question.

But without a StudioMDL.exe to compile, what made you want to use the Blender Source Tools at first? Plus, Blender itself has a game engine and such, I guess.

Maybe StudioMDL.exes just won't work on Linux. And if there isn't a StudioMDL.exe to compile the models, why would you even begin using the Source Tools?

So, no steamapps/COMMON/Team Fortress 2/bin/studiomdl.exe?

Nguyên văn bởi Vintage Zappy:

I know Team Fortress 2 has a StudioMDL (at least for Windows), so if you have that installed, try that.