引用自 Artfunkel：

I'm not sure that I want to venture very far into SFM-specific features though.

It's not Source FilmMaker-specific at all. Maybe unless you take the "FilmMaker" part out. (Yes, it's Source-specific.)
Team Fortress 2's unused(?) "HWM" models also have "preset" files for emotions, phonemes, and visemes, and in fact those are the ones loaded by Source FilmMaker when spawning Source FilmMaker's own "HWM" models, not some Source FilmMaker-specific versions of them.

A preset is basically just an extra slider for the model which affects multiple other sliders, and can be used by probably many versions of the Source Engine.

Oh, ArtFunkel.

Who's ArtFunkle?

Change $ParallaxStrength in the VMTs to 0.
(Also, looking over the VMT, unless you know exactly what the following parameter does and you set it to 0.45 on purpose, change $Dilation to 0.5.)

All I can say is to try pushing the eye co-ordinates (both in $Model and the attachments) further backwards into the head. The shape of the eye mesh shouldn't matter at all.

引用自 ๖ۣۜPhanto：

if I use Absolute, the attachments seem to appear all the way below the model,

Please re-read my comment, then.

Firstly, change $SphereTexKillCombo to 0. I think it basically removes some of the eye rendering if the eye-"ball" doesn't intersect fully with the eye mesh.

Secondly, with such a huge negative Y value in the eye co-ordinates, shouldn't you be using $UpAxis -Y or something? If not, you definitely did something very wrong while getting the eye co-ordinates.

Thirdly, the eye attachments should generally match up with the eye definitions in $Model (except for X axis difference), which is best achieved while using the same co-ordinates as in $Model followed by "Absolute".

What is the entire QC and the entire VMT of one of the eyes?
Also, what orientation does the eye attachment have? (That's very important.)

引用自 Es'Kophan：

Could you go over dmx and source 2, to find if dmx fully compatable with source2 or not?

The Blender Source Tools already has support for DMX for Source 2...

Well, for normal flexes, yes, but StudioMDL seems to complain because there can't both be normal flexes and vertex animation on the same part of the same model.