Creating custom models for Source Filmmaker (SFM) can seem complex at first, especially when dealing with manual model conversions. However, with a strong understanding of how to use SFM’s compiler tools effectively, you can extend existing assets or bring your own models into your projects. Manual model conversion, while technical, opens the door to full creative control and deep customization using Source engine assets.
TL;DR: Manually converting models for SFM involves preparing assets, editing QC scripts, and compiling models using the SFM Compile tool. It requires understanding of Source engine paths and syntax. Tools like Crowbar, Blender, and VTFEdit are essential. While the process is technical, it’s manageable with patience and attention to detail.
Understanding SFM Model Compilation
In Source Filmmaker, model files are used in their compiled binary form (like .mdl, .vvd, and .dx90.vtx). These are generated through a process called model compilation, which takes source files such as SMD or DMX format meshes, and processes them with a QC script using a compiler like Crowbar or Studiomdl.EXE. When a user refers to SFM Compile, they’re typically talking about using Studiomdl in the SFM environment or with its settings for proper compatibility.
What You Need Before You Start
Before diving into manual model conversion, ensure you have the following installed and configured:
- Source Filmmaker (SFM): Installed via Steam.
- Crowbar: A decompiler and compiler tool for Source models.
- Blender (or 3ds Max): For editing or converting your base model to SMD/DMX.
- VTFEdit: To convert textures into Valve’s VTF format.
- Notepad++ or any text editor: To edit QC scripts and configuration files.
Having a clean and organized file structure also helps, especially as your model project grows in size.
Step 1: Prepare Your Model and Textures
To convert a model to be used in SFM, it needs to be exported from your 3D modeling software (like Blender) into the correct format: .SMD (for meshes and animations) or .DMX (preferred for advanced rigs).
- Export the mesh as reference.smd or model_name.dmx
- Export the skeleton (if animated) as skeleton.smd or rig.dmx
- Export idle pose or basic animation if applicable
Next, convert all your model’s textures to the .VTF format using VTFEdit. You’ll also need .VMT files to define material properties. Place these converted textures inside SFM’s materials folder structure.
Step 2: Create and Configure Your QC File
The QC file is a script used during the compilation process. It defines which model files to compile, where to find materials, bone setup, hitboxes, and more. A basic QC file looks like this:
$modelname "custom_models/your_model.mdl"
$bodygroup "main"
{
studio "reference.smd"
}
$cdmaterials "models\custom\your_model"
$surfaceprop "metal"
$sequence idle "idle.smd" loop ACT_IDLE 1
The $modelname and $cdmaterials parameters are especially important. They tell the compiler where to place the final model and where the material files are located.
It’s crucial that the cdmaterials path matches your texture folders inside SFM’s game subdirectories. Consistent file structures reduce the risk of texture or model loading issues inside SFM.
Step 3: Compile the Model Using Crowbar or StudioMDL
With everything prepped—geometry, textures, and a QC file—you can now compile the model into SFM-compatible binaries.
To do this, open Crowbar, and under the “Compile” tab:
- Select the QC file you created.
- Set the game info path to SourceFilmmaker\game\usermod\ (or wherever your working mod directory is).
- Click “Compile.” Review the log for any errors or warnings.
The compiled .mdl, .vvd, and .vtx files will be placed into the appropriate models folder. If the compilation is successful, the model is nearly ready for import into SFM.
Step 4: Load and Test the Model in SFM
Launch Source Filmmaker and open a project or create a new one. Use the Animation Set Editor to add a new model. You should see your compiled model listed based on the $modelname path you defined in the QC file.
If the model loads but appears broken, invisible, or textureless, you may need to revisit either the model’s export or correct paths in the QC or VMT files. Console errors inside SFM can help you trace the problem.
Troubleshooting Common Issues
Manual model conversion can produce multiple kinds of errors. Below are some typical issues and solutions:
- Missing mesh: Check if your reference.smd or dmx is correctly linked in the QC.
- Texture not showing: Ensure the VMT file links correctly to the VTF with full paths matching what’s in cdmaterials.
- Model isn’t appearing in SFM: Check your compile output location. If misplaced, SFM won’t detect it.
- Bones or animation issues: Review bone weights in Blender and ensure they’re exported correctly.
Advanced Tips
Once you’re comfortable with basic conversion, there’s room for enhancement:
- Add flexes: For facial animation, define flex controllers in Blender and export via DMX.
- LOD models: Create optimized versions of your model for performance scaling.
- Animation sequences: Add predefined idle, walk, or attack animations using $sequence commands.
- Attachment points: Use $attachment to define weapon or light positions for rigging.
Model Conversion Workflow Checklist
To assist in consistency, here’s a final checklist you can refer to:
- Model exported (SMD/DMX)
- Textures converted (VTF/VMT)
- QC authored and validated
- Crowbar paths and tools verified
- Compiled output placed correctly in SFM/game/usermod
- Model loads with correct appearance and scale
Conclusion
Using SFM Compile for manual model conversion requires attention to detail, knowledge of Source engine file structure, and proficiency with third-party tools. While the learning curve is steep, the creative control it gives you over characters, props, and animation sequences is nearly limitless. Every step—whether editing a QC file or debugging a missing texture—moves you closer to becoming an proficient Source developer and animator.
Approach model conversion methodically, stay organized, and don’t be afraid to experiment. Every SFM professional started where you are now—with curiosity and a willingness to learn.