Check the console for errors, such as where the VMT and/or VTF is supposed to be located, and then move the VMT and/or VTF into their proper locations.

Hm. I think you forgot to append "[FIXED]" to the start of the title after fixing this, Artfunkel (and/or NimrodX), making it seem like an unfixed bug when browsing bug reports...

On a scale of 1 to 10, the "title" makes 0 sense.

If I import a mesh I've made, go to pose mode for the skeleton, press I, add a keyframe for "LocRot", and then go down to change the export directory for the "animation" from "anims" to ".", it clears out the "Source Engine Exportables" content, and grays out the "Export" button in "Source Engine Export", making me unable to export anything (until I reload the Blend file or start a new session or something). That means I don't remember what I have to type to make animations export in the directory I choose in "Source Engine Exportables". Either way, it's still a bug.

Originally posted by Twitchy:

none off the paths i use work... im trying to just export my model for gmod... any help?

../SteamApps/common/Team Fortress 2/bin.

The title is... not helpful at all, but if you import mesh A, and then import mesh B (which is made to work on mesh A), while mesh B has bones mesh A doesn't (such as jigglebones), either Blender says "X vertices weighted to invalid bones" if Append to Existing Model is checked, or one has to manually remove old bones on mesh B and re-parent new bones on mesh B if Append to Existing Model is unchecked, since joining skeletons/armatures just adds ".001" and such to bones on the first-selected skeletons/armatures with the same names as on the last-selected skeleton/armature.

So here I bring a suggestion: A tickbox to choose whether to automagically add the new bones to the old skeleton/armature, if new ones are found while importing another SMD/DMX mesh (with Append to Existing Model checked).

It can be grayed out if the old skeleton/armature has keyframes, if that won't be compatible.

Atleast there then is a reason for me to remake the weight-mapping on my pony models (as I had cut it down to 3 before the "Weight Link Cull Threshold" was added to the Blender Source Tools). Thanks for responding, especially so quickly.

In Source, vertices in SMD meshes can have as many weight-links to different bones as one wants. Vertices in DMX meshes are restricted to at-most-3 weight-links, though, even though the format itself apparently can accept lots of weight-links (like SMD)*. But... Source 2. Does anyone know if there are currently weight-link limits in DMX meshes for Source 2? (By "currently", I mean the Dota 2 WorkShop Tools Alpha thing.) Or will only time tell?

* As in, I can export a DMX with more than 3 weight-links on one or more vertices from Blender, import it in Blender again, and it still has more than 3 weight-links.

Originally posted by Artfunkel:

Since this only affects a handful of files in a legacy format, I suspect that manual fix-up is the best solution you're going to get.

Originally posted by Artfunkel:

legacy format,

I've yet to see Source MDL decompilers with DMX support...

Originally posted by Artfunkel:

Currently the operator only cares about vertex location. It it should be taking into account weightmaps and normals too,

Should? No. Should have a checkbox toggling those things on/off? Yes. I wouldn't want it to always check weights and normals no matter what...

Hm. That sounds interesting. Thank you for responding.