Because you most likely scaled the model using the armature in Object mode, but did not apply the transforms to all objects in the model after the scaling. The mesh is adopting the new scale of the armature to make it 1 where the scale of the armature is already 1 on compile.

Select all objects in the model, press Ctrl+A - All transforms, Re-export the model and recompile.

Just glad it helped

How Valve Materials and textures work in relation to Blender materials. It's the same for 2.8x and above as it was for Blender 2.79 and below.

https://psteamcommunity.yuanyoumao.com/sharedfiles/filedetails/?id=1528003376

Do a proper unwrap, assign a material, set up BleST properly and the weapon should export your smds..

https://i.imgur.com/mu5hR7T.png

I opened your Blend file and looking at the set up of Blender Source Tools, you haven't set anything up??? There's no Export path, no game engine set up, so I have no idea what you're trying to compile this for. NOR have you set up any materials on the model. You're model is nowhere near ready for export using the blend file you provided.

https://i.imgur.com/4sPIxdi.png

Thanks Artifunkel. I was hoping there could be something done during import (if more than one model existed that used same material names.) I've also passed this as a feature request for Crowbar to Zeq to see if there is something he can do if we strip material paths on decompile.

Moving forward and backwards, in the video, it looks like you may have the jiggle values reversed (result of your bone rotations??) same for the left right.

But, remember that SFM is not going to render the actual jiggle movement when just moving the model around in an edit mode. SFM does not real time render. It's only a 32bit program and it's not fast enough for real time. You may have to actually produce a clip to MP4 and watch that for analysis of how they're actually jiggling.

For body groups (BG) is around 9000 to 11000 verts per BG unless $maxverts xxxxx (where xxxxx is up to 65530) is used in the QC. But I haven't hit the max in a model yet adding BGs.

As for the multimesh SMDs, check your model for doubles (blender m (for merge) -by distance) watch out for sealing the mouth and eyes)

If you have 2 or more of those statements in the QC (you don't) loading the same DMX then each of the statements creates an instance of the bodygroup. One for each statement it encounters. The shapekeys/flexes become confused (and usually don't work at all), because the multiples all have flexes with the same names. It all depends on which bodygroup the game engine thinks is the one that should have shapes/flexes.

Anyway, that is not the case in your case. You have a clean QC.

I would decompile the broken model and bring it back into Blender and have a look at each of the shapes to see if I could discover what is deforming by the key and what isn't.

I'm thinking that you might be right about the orientation of the edited bones.

This is a picture of how bone react to jiggles from the dev wiki You now have the z axis of the bone pointed forwards and backwards instead of along the length of the hair they're deforming.

https://developer.valvesoftware.com/wiki/$jigglebone#/media/File:Jigglebone.png

looking at the GIF I'm going to assume, that the first model in the gif is the original that you decompiled before making the bone changes because it looks nothing like what you got back from the decompile of the changed model you had in Blender and the jiggles look correct (for SFM)?

And the one in the last picture is your the import of decompile after the compile with the changes you made?

Did you reuse the QC from the original decompile and just change the jiggle information?

Also, when you imported the first SMD (step 2), did you have import animations checked on in Blender Source Tools and did it bring in a ref or idle animation? You need to edit from a clean model, no animations.

Between step 3 and 4, I (personally) would select everything (including the armature) in object mode and apply all transforms. (Just in case).