SFM Compile: The Complete Guide to Source Filmmaker Model Compilation

What Does SFM Compile Mean?

Source Filmmaker is built on Valve's Source engine, the same engine that powers Team Fortress 2, Half-Life 2, and Portal. The Source engine was designed for performance, not editability. It does not load 3D model files in formats like OBJ, FBX, or GLTF. Instead, it reads its own optimized binary formats that have been pre-processed and packed.

SFM compile is the step that creates those binary files. You start with human-readable source assets — geometry exported from Blender, textures saved as PNGs, and a text configuration script — and you run them through a compiler that outputs the engine-ready formats SFM can actually load.

The word compile here means the same thing it does in software development: you are converting source material that humans can write and edit into a processed format that a runtime (in this case the Source engine) can efficiently execute.

Tools You Need Before You Start

The SFM compile pipeline requires a small set of tools. All of them are free. You need all of them installed and configured before you attempt your first compile.

Crowbar is the application most creators interact with directly. It provides a graphical interface over studiomdl.exe, which is Valve's command-line model compiler included in the Source SDK. Think of Crowbar as the dashboard and studiomdl as the engine under the hood.

The File Types in an SFM Compile Pipeline

Before touching any tool, you need to understand what each file type does. The pipeline involves distinct formats, and a compile fails if any one of them is missing, misnamed, or malformed.

Source Files (What You Start With)

Compiled Files (What You End Up With)

Understanding the QC File

The QC file is the blueprint of your compile. It is a plain text document containing a series of commands that the studiomdl compiler reads line by line. Learning to write and read QC files is what separates creators who understand SFM compile from those who just follow steps blindly.

Anatomy of a Basic QC File (Static Prop)

$modelname    "props/my_prop/my_prop.mdl"
$cdmaterials  "models/props/my_prop/"
$body         mybody "my_prop_reference.smd"
$surfaceprop  "metal"
$staticprop
$sequence     "idle" "my_prop_idle.smd" fps 30

$collisionmodel "my_prop_phys.smd" {
    $mass 50
    $concave
}

QC Command Reference

QC File for an Animated Character

$modelname    "characters/hero/hero.mdl"
$cdmaterials  "models/characters/hero/"
$body         mybody "hero_reference.smd"
$surfaceprop  "flesh"

$sequence "idle"   "hero_idle.smd"   fps 30 loop
$sequence "walk"   "hero_walk.smd"   fps 30 loop
$sequence "run"    "hero_run.smd"    fps 40 loop
$sequence "attack" "hero_attack.smd" fps 24

$attachment "eyes" "ValveBiped.Bip01_Head1" 3 4 0 rotate 0 -80 -90

Preparing Textures with VTFEdit

SFM cannot use PNG or JPEG textures directly. Every texture must be converted to VTF format, and each VTF needs an accompanying VMT file that tells the engine how to render it.

Converting a Texture to VTF

1. Open VTFEdit and go to File → Import
2. Select your texture file (PNG or TGA — TGA preferred for quality)
3. Choose compression: DXT1 for opaque textures, DXT5 for transparency
4. Set the output directory to match the $cdmaterials path in your QC file
5. Save as a VTF file

Writing the VMT File

The VMT is a plain text file saved in the same directory as your VTF:

"VertexLitGeneric"
{
    "$basetexture"  "models/props/my_prop/my_prop_diffuse"
    "$model"        "1"
}

The $basetexture path does not include the file extension and is relative to the game's materials folder.

Compiling with Crowbar: Step-by-Step

With your SMD files, QC file, VTF textures, and VMT material files ready, you are ready to run the actual compile.

Initial Crowbar Setup (Do This Once)

1. Download and install Crowbar from the GitHub releases page
2. Open Crowbar and navigate to the Set Up Games tab
3. Add Source Filmmaker as a game target
4. Point Crowbar to your SFM's gameinfo.txt — typically at: steamapps/common/SourceFilmmaker/game/usermod/gameinfo.txt
5. Confirm studiomdl.exe is detected automatically from the Source SDK

Running a Compile

1. Click the Compile tab in Crowbar
2. Under QC File, browse to and select your .qc file
3. Under Output To, select the Game's "models" folder
4. Click Compile
5. Watch the output log carefully — this is where errors appear
6. If the log ends with "Compilation succeeded," your MDL is in place
7. Open SFM → Animation Set Editor → Create Animation Set for New Model → load your MDL

Reading the Crowbar Output Log

Decompiling Existing Models

One of the best ways to learn is to decompile models that already work in SFM and study their structure.

1. In Crowbar, click the Decompile tab
2. Under MDL File, select the compiled .mdl you want to examine
3. Set the output folder to a working directory outside your SFM installation
4. Click Decompile — Crowbar extracts SMD files, the QC script, and texture references

Study the resulting QC file structure. Look at how $body references the mesh SMD, how $sequence entries are named, and how $cdmaterials is formatted. QC files from professionally made models are excellent templates.

Common SFM Compile Errors and How to Fix Them

The majority of compile failures come from a handful of recurring causes.

Workflow Tips for Faster, Cleaner Compiles

project/
  modelsrc/                        ← Source files (SMD, QC, TGA)
    characters/hero/
      hero_reference.smd
      hero_idle.smd
      hero_walk.smd
      hero.qc
  usermod/
    models/characters/hero/        ← Compiled MDL output
    materials/models/characters/hero/  ← VTF and VMT files

Compiling Animated Models and Characters

Rigging Requirements

Source Filmmaker uses Valve's biped skeleton system for humanoid characters, based on the ValveBiped bone naming convention. If porting from another engine, you must retarget or rename bones to match this convention for the character to use existing SFM animation rigs.

Exporting Animation SMDs

In Blender with the Source Tools addon:

1. Select the armature in your scene
2. Set the export action to the specific animation you want
3. Export as SMD
4. Repeat for each animation — each export produces one SMD file

Your QC file then references all of these SMD files in separate $sequence commands.

Flex Controllers and Facial Animation

Facial animation in SFM is driven by flex controllers — morph targets defined in your model. Setting up flexes requires shape keys in Blender exported as DMX rather than SMD, and configured in the QC with $flexcontroller and $flex commands.

Beyond the Basics: Advanced Topics