No, QCs are not generated, they have to be written manually. Best thing to do is find a real model from the game engine you're going to use and decompile the model using crowbar. There is a switch in Crowbar that allows it to create a QC based on the model being decompiled. Use that as a guide for creating yours. As for setting the path to the game engine, I know you're interested in goldsrc, but are recompiling for goldsrc (original HL, TFC, Blueshift, etc) or are you actually compiling for the newer engine HLSource?

no, most likely not other than to see what elements are create and brought into blender if you decompile a HL1 type model and what the qc looks like for compiling. When you compile, you would use the HL version of Studiomdl to ensure it compiles for use in Halflife.
Unfortunately, the format/requirements for a SFM model and Halflife model are not the same. So I apologize if I wasted your time posting the response I did.

5 video series on porting GoldSrc Models

https://www.youtube.com/playlist?list=PLZavzoXLqZCrBTDKQ-ywmWx1chsPOEDOI

Now that I see this, I think I know what your problem is....

Your Flexcontroller statemenst are out of order...


Here you have flexcontroller commands

There is no $model statement or flexfile definition

Then you have these local vars defined but then again, what are they defined for?


Finally you have things listed properly here in the qc. You have the $model statement but, this is not for the character's whole head, it's just for the just for the eyelids.

When using SMDs you can only have 1 $model statement and Flexes and controllers can only be defined once.


Now, if you decompiled this model with Crowbar, there may be multiple VTA files, but only 1 will have a large files size, the rest will be much smaller and should be the same filesize. I think it is being caused by the multiple bodygroups. The LARGEST VTA file is the one you want.

Yeah, Sorry Gredwitch, I answer in a lot of different discussion groups. It was late and I only quickly glanced at the logo and the group name and thought it was the main Blender group.
Besides, It could have been that you imported a Valve model and all its associated animations and wanted to go to a different format on export. But you've gotten your answer (by the looks of it) from the dev of this excellent tool.

Copy and paste the qc here

Bulk Export animations for what format? What is it your exporting the animations for? FBX, Valve Model via Blender Source Tools, DAE...

Without knowing what you're trying to export for (ie game engine) then we can't really help.

"ERROR: c:\users\jfour\desktop\decompiled\dmx\jhm.qc(3): - bad command flexcontroller" say that on Line 3 of your qc (.qc(3) <--- Indicates the line the error occurred) you have a bad command flexcontroller... without seeing the actual qc, we really can't help.

QCs have to be written manually for each model you want to compile. There isn't an automaker for creating QCs

(Briefly) The way a Valve Model work from idea to in game is:

1) create model in a 3d editor (Blender)

2) create an armature and assign mesh to it

3) UV unwarp the model and texture it

4) export SMD or DMX source files from blender

5) write the qc that will be used to compile the model into Binary model for use in game

6) click the button that is created when you point blender source tools at where the qc lives and
COMPILE the model into a Valve Binary model.
(A compiled model is made up of 3 to 8 files depending on the game being compiled for, these are the .mdl, .vtx files (the .sw.vtx, .dx80.vtx and .dx90.vtx), the .vvd file and the .phy (collision model) file.)
Only click the compile all button if there are more and one qc in the folder you pointed at and want to compile all qcs in one go.
(But it is always better to compile them one at a time by clicking their individual buttons. This way you catch errors faster and bttr if they occur)

7) Create Valve Material (vmt) and Texture (vtf) files

8) enjoy your model in game

As I said, this is a brief discription of the process. Each game you compile for has its own quips that you have to watch out for.