Skip to content
Frame & FormINTERNATIONAL ACTOR MAGAZINE

Frame & Form

Compile

SFM model compilation is the process of converting exported model data and build instructions into a Source-engine model that Source Filmmaker can load. The exact steps depend on the model source and the tools you use, but most workflows involve source geometry, a QC script, material references, a compiler and a final test inside SFM.

What files are involved?

Many custom-model workflows use SMD or DMX files as intermediate model data. These files describe model geometry, skeletons, animation or related data exported from a 3D application. The QC file tells the compiler how to build the model: it can define the model name, body groups, included geometry, materials, surface properties and other options. The precise commands depend on the model and Source branch.

Understand the basic compile pipeline

  1. Prepare the source model. Check scale, orientation, naming, skeleton and export settings in the authoring tool.
  2. Export the required files. Keep track of which SMD or DMX files represent the body, physics model and animations.
  3. Write or review the QC script. Check file paths and output names carefully. A typo or unexpected folder can make an otherwise valid build fail.
  4. Compile with a compatible tool. Use the compiler expected by your Source workflow. Crowbar is commonly used by the community for Source model workflows; check its documentation and the tool version you installed.
  5. Inspect the output. Confirm that the compiled model and related files are written to the intended game or user-mod directory.
  6. Test in SFM. Load the model, inspect the skeleton and materials, and verify scale, orientation and any body groups.

QC files: what to check first

The QC script is not just a filename list. It is the build recipe. Review the model output path, source file references, material directory, included body or animation data and any commands that set up the model. Do not copy a QC file from a different model without understanding which paths and options are specific to that model.

When a compile fails, read the first meaningful error in the log rather than starting at the final summary. A missing source file, invalid command or incorrect path can cause later errors that are only symptoms. Correct one issue at a time and compile again so the result is easy to interpret.

Materials: keep model and texture debugging separate

Compiled geometry and materials are connected, but they are not the same failure category. A model may load while a material path is wrong. Source material setups often use a VMT material definition and a VTF texture file. Verify that the material name and directory match what the model expects, and that the material file points to the correct texture. See how to fix purple and black SFM textures for a focused checklist.

Folder structure and output paths

Use a predictable folder structure and write down where the source files, compiler output, models and materials belong. Avoid keeping several similarly named copies in unrelated folders. If a model loads in one application but not in SFM, check whether both applications are reading the same output and material directories.

Common compile errors

  • Source file not found: verify the filename, relative path and export location.
  • Compiler cannot parse a command: check spelling and confirm that the command is supported by the tool and game branch.
  • Model compiles but does not appear: inspect the output location, model name and SFM search paths.
  • Model appears with missing textures: verify VMT/VTF files and material paths rather than repeatedly recompiling geometry.
  • Unexpected scale or orientation: review export units, transforms and the source model setup.

How to verify a successful build

A successful compiler message is only one checkpoint. Load the model in Source Filmmaker and inspect it in a test scene. Check whether the model is the right size, faces the expected direction, has the correct materials and exposes the expected body groups or bones. Test a short animation if the model includes a skeleton. Keep the compiler log with the project so future errors can be compared.

Next steps

For first-time users, begin with the Source Filmmaker beginner guide, then use this article as a reference while compiling a single simple model. If your issue is visual rather than a compiler failure, use the guide library and resource hub to narrow down the next step. Always respect the license and permissions attached to third-party models and textures.