Skip to content
Frame & FormINTERNATIONAL ACTOR MAGAZINE

SFM Compile

SFM Compile Explained: Models, QC Files and the Source Workflow

By Frame & Form Editorial Team · · Updated October 10, 2026

SFM model compilation converts exported model data and build instructions into a Source-engine model that Source Filmmaker can load. It is easiest to debug when you treat the process as a pipeline: prepare source files, write or review the QC script, compile, verify output paths and test the model in SFM. A successful compiler message is important, but the in-app test is the final check.

Source files: SMD and DMX

Custom-model workflows often use SMD or DMX files exported from a 3D application. Depending on the project, these files may describe a body mesh, skeleton, physics model or animation. Check the export settings before compiling: a wrong scale, orientation, skeleton or filename can create problems that look like compiler errors later.

The QC file is the build recipe

A QC script tells the compiler what to build and where to find the input data. It can define model output names, source files, body groups, materials and other model settings. Commands and options vary with the Source branch and model type, so do not copy a QC file from an unrelated asset without checking every path and directive.

Before compiling, confirm that each referenced source file exists and that the model and material names are consistent. Keep the QC file alongside the project files so you can understand the build later. If the compiler reports a missing file, correct that reference first instead of changing multiple unrelated settings.

The basic SFM compile workflow

  1. Prepare the model: check geometry, scale, orientation, skeleton and naming in the authoring tool.
  2. Export source data: keep the body, physics and animation files organized and clearly named.
  3. Review the QC script: verify file paths, output names and material references.
  4. Use a compatible compiler: follow the workflow and tool version required by the asset or Source branch. Crowbar is commonly used for community Source model workflows; consult the relevant documentation for your setup.
  5. Read the compile log: start with the first meaningful error and address one root cause at a time.
  6. Check output folders: verify that the model and related files were written where SFM can discover them.
  7. Load the model in SFM: inspect its size, orientation, materials, bones and body groups.

Materials and texture paths

Model compilation and material loading are related but separate. A model can load with correct geometry and still show missing textures if its material references cannot be resolved. Source materials commonly use VMT definitions that point to VTF texture files. Verify that the expected material files exist and that the path in the material definition matches the folder structure.

Do not recompile geometry every time you see a purple-and-black checkerboard. First check the material path and the VMT/VTF files. Our purple texture troubleshooting guide walks through this diagnosis separately.

Common compile errors and what to check

  • Input file not found: check spelling, folder names, export locations and relative paths.
  • Unknown or invalid command: check command spelling and compatibility with the compiler and game branch.
  • Model compiles but is absent in SFM: verify the output directory, model name and SFM search paths.
  • Wrong scale or orientation: inspect export units, transforms and the original model setup.
  • Missing textures: verify material definitions and texture files instead of assuming the compile failed.
  • Broken rig or animation: check the exported skeleton and whether the required source data was included.

Make troubleshooting repeatable

Change one thing at a time and keep the compile log for each attempt. Record the exact error, the file you changed and the result. This creates evidence about what fixed the problem and makes it easier to undo an unsuccessful experiment. Avoid keeping several conflicting copies of the same model in different folders because SFM may load a different copy than the one you just changed.

Verify the model inside Source Filmmaker

Open a clean test session and load the compiled model. Confirm that it is visible, faces the correct direction, has the intended scale and uses the right materials. Inspect its skeleton and body groups if applicable. If the model has animation, test a short movement before using it in a larger scene.

For beginners

If you are new to the software, begin with the beginner’s guide to Source Filmmaker before working with custom model source files. If your goal is simply to add an existing model, read how to install custom models first. Browse the resource hub for related tool and asset references, and check third-party licenses before redistributing or commercializing any model or texture.