引用自 Lol3#IC：

I need to use the citizen flexes -

Again, which "the citizen"? If "the citizen" is a character known as "The Citizen" from some game I don't know of, please, explain so. If not, please, explain what "the citizen" actually is.

引用自 Artfunkel：

The tools allow you to specify a path to a DMX as your flex controller source. Not sure if you can extract them to a text file though.

I use one of the "Generate Controllers" text documents as a stand-alone TXT file that I just link to (with the "Open File" thing beside the name of the controller-file to use), if that's what you mean.

引用自 Lol3#IC：

So I can't convert the citizen's flexes into the dmx controller text file?

Which "the citizen"?

引用自 Lol3#IC：

So, how do I convert the code in my .qc file for flexes into the dmx controller file? -

The flex definitions in the SMD QC in comment #3 of this thread is the most basic and pure form of flexes, with no flexes having special attributes (besides the "defaultflex", which you should be able to just ignore in most cases anyway), and every flex slider being assigned to exactly one flex, in no special ways. With exception of "flex decaying" (which defaults to 1.0 with VTA flexes and nothing with DMX flexes), which if you don't know what is you probably don't want and also just causes some issues with Source FilmMaker, that's exactly what you get with the auto-generated "Simple" flexes and exactly what you get by clicking the "Generate Controllers" button for "Advanced" flexes.

TL;DR: In this case, that's what you get if you just click "Generate Controllers" for "Advanced" flexes, as I explained above.

引用自 Lol3#IC：

- Also, how do you open dmxedit? -

It's most likely irrelevant in this case; The Blender Source Tools handle embedding flex data inside of exported DMX files automatically. It reads the flex controller data straight from the text document thing stored in the Blender session (which you can also export as a stand-alone file and reference that way if you want).

引用自 Lol3#IC：

thanks it worked, but now how do I setup flexpairs with DMX?

In Blender, in the "Scene" tab to the right, beneath the "Source Engine Export" list (where you click a button to export SMD/VTA/DMX files) is a list called "Source Engine Exportables". In that group, click on/select the object that has flexes. Now there should be a "Flex Properties" box at the bottom of the "Source Engine Exportables" list thing. Click on "Advanced" in it, then click "Generate Controllers" (the button that has a notepad-like icon to the left of it).
Now, far to the left in the window, where you normally switch from the "3D View" to the "UV/Image Editor" or the other way around, switch to the "Text Editor". Then, beside where you switched to the "Text Editor", much like with the "UV/Image Editor", will be a few drop-up lists of actions as well as a drop-up list of text things you can edit. Choose the "flex_[Stuff]" text thing.
Now you will see a lot of weird stuff... but all you should have to care about are the various "DmeCombinationInputControl"s. There will be a "name" attribute, telling you which flex controller it is, and a "rawControlNames" attribute, telling you which shape key names are used for that flex controller. You don't have to edit those, I'm just letting you know about them so you can find out which "DmeCombinationInputControl" is for which flex.
Now change the "stereo" variable to "1" to make it automatically have independant left and right flex controllers. Example, with the line to change being bolded out and with an underline under what to change:After you've changed the flexes you want to be stereo flexes, feel free to go back to the "3D View" or the "UV/Image Editor" again.
Now back in the "Source Engine Exportables" thing, below the "Generate Controllers" button, there should be a "Stereo Flex Balance" option. You can change that if the stereo split is too wide or too thin, but try leaving it at the default 90% for now and just see how it looks.

Note: DMX considers a flex/shape key called "Smile_Wide" to be used when both "Smile" and "Wide" are in effect, so if you have any non-"corrective" shapes that contain underscores, you have to get rid of the underscores first. Make sure to do that before generating the flex controllers text thing. If it's too late, just generate a new one, and set the flexes you want to be stereo again.

Disclaimer: I may not necessarily be good at explaining things.

引用自 Lol3#IC：

So the Studiomdl is buggy?

Sort of. It sees a bone called "Head" or so, then looks at where "Head" is positioned, then uses that as the position of the bone. The thing just is, the "Head" it sees first is the mesh object itself, not the bone, so it uses the position of the mesh object (which is usually at 0 0 0) for the bone.

In other words, you can fix it by renaming the head mesh object to something like "MeiHead" or so, while keeping the bone's name the same.

引用自 Artfunkel：

From testing the compiler's behaviour, of course. I just made a test plane with 36 bones and it's mashed up too. If you want to upload your blend I'll take a look and see what's different about yours. Perhaps it's a bug that has been fixed in the version of the engine you're compiling for?

Just to be clear, I'm not talking about this specific thing, so while what you said may apply to this specific project for some reason and somehow also your test plane, I don't feel it applies in general somehow.

What I'm not experiencing issues with are edited Team Fortress 2 models (which are often split up into several parts and never need to be "culled" to be exported as DMX) and edited custom My Little Pony models (which are often not split up, and is what I'm talking about in this case). I'm compiling for Source FilmMaker and ocassionally Team Fortress 2, using their respective versions of StudioMDL... but the pony models don't seem to have any vertices with over 5 or 6 linked bones (pre-"cull"), though, and are usually weighted in big regions, rather than lots of bones affecting close and neighbouring vertices (like on a face, such as in this case).

Again, I just personally don't think it affects everything in general, but if it also applies to a test plane you just made, then I'm not really sure anymore...

引用自 Artfunkel：

- I have code in the exporter to cull the excess links and redistribute their weight across the survivors, and I'm sure you've noticed the warnings. But that isn't enough for your "head" mesh because even though the individiual vertices are within the limit, the mesh overall is stil weighted to too many bones. 11 bones, to be precise. Evidently the engine doesn't like this. -

I'm not really sure where you get that information, considering I can have a single DMX mesh that's all connected together, has lots of bones (over 20 bones), and works just fine since there's not any given vertice that uses over 3 bones. Just wanted to let you know.

引用自 Lol3#IC：

- Also I don't understand why I should use head.smd / dmx for the sequence as it is not an animation file.

StudioMDL looks at the various frames of skeletal animation for sequences. A mesh file does contain 1 frame of skeletal animation. You should use it because the model is supposed to just be in the reference pose in that sequence.

For the $Sequence line in the SMD QC, I suggest using head.smd, not anims\ragdoll.smd.
Likewise for $Sequence in the DMX QC, I suggest using head.dmx and not anims\ragdoll.dmx.