Well that is certainly odd. If you have Source FilmMaker installed, what happens when you try adding override materials to the model, and checking the model in the Element Viewer? And if not, a screenshot of the "Model" tab in the model viewer might be helpful instead.

Try copy-pasting all the contents of the console into something such as Notepadd++ (or even just Notepad), then do a search for "megacoffeetable" and/or "material", and see if you can find a material/texture error like that.

Artfunkel lähetti viestin:

That should be OK then. HLMV can tell you the path of the material it's trying to load on the model tab. What's it saying?

It's (probably) saying "Failed to load this or that material" in the "loaded materials" list in the bottom-right, or the name of the expected material in the material list in the bottom-left.

Either way, the console in a true Source game/engine (Team Fortress 2, Source FilmMaker, Garry's Mod...) would output "couldn't load material X" or "couldn't load texture X", so checking the model in Source itself might be a better idea than just the model viewer.

Of which I'll be doing the latter... but that doesn't mean it's less annoying, though. Alrighty.

...Oh. I had just copied one of the flex controller blocks to add a new shape key, but I forgot to change the element id of the new copy.

Edit: Human error

How to reproduce:
Load Blend session which has allowed exporting earlier
Export
Marvel at the error I have no clue what means[sta.sh]

Hot-fix requested. This error was the reason I updated to Blender 2.74 and Blender Source Tools 2.5.0 (after some hours of work in 2.72b with Blender Source Tools 2.4.1), but apparently, updating didn't fix it.

Upon copy-pasting (Ctrl+C > Ctrl+V, not Ctrl+D) a mesh linked to a Blender Source Tools sphere armature and pasting it, one gets: The mesh one copied (expected and wanted), the armature (expected and wanted), and smd_bone_vis.001 (unexpected and HIGHLY unwanted), which is a mesh of the ball thing used for sphere armatures when importing stuff using the Blender Source Tools. Happens in a 64-bit Blender 2.74 Zip install over a 2.72b install using Blender Source Tools 2.5.0 on a 64-bit Windows 7, didn't happen in said 2.72b install with Blender Source Tools 2.4.1. smd_bone_vis.001 spawns with an origin point of 0 0 0.

Steps to reproduce:
Import SMD or DMX mesh, leave import settings at default
Select a mesh object
Ctrl+C
Ctrl+V

Edit: Also, yes, this also happens when copying a mesh from a Blend session saved in 2.72b, which is how I found out about it.

Not really, partly since I still use Blender 2.72b as of yet, partly since I don't have any sessions with that bug saved. Edit: But try enabling auto-smooth, mark something as sharp, then disable auto-smooth. In Blender, the disabling should work properly, but as far as I'm concerned, the Blender Source Tools still load those sharp edges (in 2.4.1 at least).

Besides... The flex controller names in Source are different from the flex blendshape names in DMX files (or VTA, if you decompile stuff).

No.