I don't think vertex animation has been implemented for DMX yet in the Blender Source Tools. Use SMD instead, so you'll get a VTA you can use. (Yes, you can use VTAs on DMX meshes. Even if the DMX has other flexes embedded already.)

Автор сообщения: Pte Jack

I guess the SMD compile knows the difference between the object data types and the DMX compile doesn't.

SMD merges all meshes together into one object before exporting. DMX does not. That means for SMD, there's technically not that object and bone with the same names, while there is for DMX.

Автор сообщения: Artfunkel

Not sure what's going on with the "default" slider in SFM though.

For controllers (flex sliders, camera field-of-view, and such), it sets it to the default value.
For bones, it almost always sets translation and rotation to 0 0 0, despite that (usually) not being the default location for the bone.

Select all objects, press Space, search for "Apply", choose "Apply Object Transform", tick on all three boxes on the left (Location, Rotation and Scale), press Space, choose "Apply Object Transform" again, and do it one more time just to be absolutely certain nothing's wrong.

Edit: By the way, are you using bodygroups or in some other way using multiple groups when exporting? If so, this might not fix it, and you should manually export every group one by one instead of using a scene export.

The engine path is used to check what the best available DMX type is for the target game engine. Only the "bin" folder of a game is necessary (the one with studiomdl.exe, just as the tool-tip says in Blender Source Tools, I think).

But without setting an engine path, you can still export DMXes, and as long as the target game engine supports the DMX type you manually choose to export with, you can still compile the model. Usually games support DMX types made for the game in question and DMX types made before the game was made.

The engine path does not matter at all for SMDs, by the way. (At least I don't think it does.)

2.75? Update to the latest version of Blender, then.

The best "work-around" is to import one mesh that's smooth-shaded, and another mesh with "preserve SMD polygons and normals" or whatever ticked on, then manually splitting/sharpifying the edges of the smooth-shaded mesh to look like the "preserved" mesh.

Blender Source Tools doesn't like importing sharp edges on SMD models.

Автор сообщения: ConfederateJoe

Doesn't it automatically cull?

Not unless the "weight link cull threshold" is above 0.

Автор сообщения: Zappy

I'd advice downloading the Source SDK, running it at least once, and inspecting the Team Fortress 2 class models' source DMX files' flex data blocks. (They can be found at [Installation]/
/steamapps/common/sourcesdk_content/tf/modelsrc/ or something like that.)