Missing Textures (Gray Textures)
If you see gray textures or checker patterns in your decompiled map, this is usually because materials are embedded in the BSP file rather than existing in the base game.Cause
This commonly occurs with:- Workshop maps
- Maps using CS:GO’s autocombine prop feature
- Custom maps with embedded content
Solution
-
Extract embedded files during decompilation:
-
Move extracted files to your game directory:
- Copy extracted
materials/folder to[game]/materials/ - Copy extracted
models/folder to[game]/models/
- Copy extracted
-
Smart extraction (default behavior):
This automatically skips VBSP-generated files that are only needed by the engine.
-
Full extraction (extract everything):
Missing Models (Error Models)
Similar to textures, missing models appear as red ERROR placeholders.Solution
Follow the same process as missing textures:models/ folder to your game’s models directory.
Decompilation Fails or Crashes
BSP File Not Found
Error:Could not find bsp file
Solution: Verify the file path is correct and the file exists:
Wrong Game Detection
Issue: BSPSource detects the wrong game for your map. Solution: Override game detection using the--appid flag:
Missing .nmo File (No More Room in Hell)
Warning:Missing .nmo file! If the bsp is for the objective game mode, its objectives will be missing.
Solution: Ensure the .nmo file is in the same directory as the BSP file. This file contains objective data for No More Room in Hell maps.
Decompiled Map Issues
Brush Errors in Hammer
Issue: Brushes appear incorrect or cause errors when loading in Hammer. Solution: Try different brush modes:Thin Brush Issues
Issue: Flat faces create brushes that are too thin. Solution: Adjust brush thickness (default is 1 unit):Instance Entity Rotation Issues
Issue: Instance entity brushes appear rotated incorrectly in Hammer. Solution: Enable rotation fix (enabled by default):Performance Issues
Slow Decompilation
Issue: Decompilation takes too long. Solution: Skip protection checking if decompiling unprotected maps:Large Output Files
Issue: VMF file is too large or has too many entities. Solution: Selectively disable entity types:Command Line Issues
Recursive Decompilation Not Working
Issue: Only decompiling one file instead of all BSPs in a directory. Solution: Use the--recursive flag:
Output Path Issues
Issue: VMF files going to wrong location. Solution: Explicitly specify output path:VMF Format Issues
Hammer Version Compatibility
Issue: VMF doesn’t open correctly in Hammer. Solution: Force a specific VMF format:Debug Mode
If you’re experiencing issues, enable debug mode for detailed output:- Increase verbosity to maximum
- Add additional data to the VMF file
- Show all configuration values
- Display detailed BSP information
Getting Help
If you encounter issues not covered here:- Enable debug mode and review the output
- Check the GitHub Issues page
- Open a new issue with:
- BSPSource version
- Game and map name
- Full command used
- Debug output or error messages