Usage
Arguments
View name to launch.Available views are defined in
crimson.views.Common views:empty— Empty scenelighting-debug— Lighting system debugsprite-test— Sprite rendering testterrain-test— Terrain rendering test
Options
Window width in pixels.
Window height in pixels.
Target frame rate.
lighting-debug only: Run autodiag and dump screenshots for each shader debug mode.
lighting-debug only: Total autodiag frames when
--dump-shader-debug-views is set.Must be ≥ 30.lighting-debug only: Run automated quality/perf sweep and print best tuning preset.
lighting-debug only: Sampled frames per preset when
--autotune-shadow-defaults is set.Must be ≥ 12.Preserve known original exe bugs/quirks.
Assets root directory.
Available Views
To see all available views:Examples
Empty Scene
Lighting Debug View
Dump All Shader Debug Modes
Autotune Shadow Settings
Sprite Test
Custom Assets
View Context
Views receive aViewContext:
Lighting Debug View
Thelighting-debug view has special diagnostic modes:
Shader Debug Modes
Cycle through shader debug visualizations:- Normals
- Depth
- Shadows
- Ambient occlusion
- Light accumulation
--dump-shader-debug-views to export all modes.
Shadow Autotuning
The--autotune-shadow-defaults flag runs performance benchmarks:
- Tests multiple shadow quality presets
- Measures frame time for each
- Finds best quality/performance balance
- Prints recommended settings
Controls
Common view controls:ESC— Close viewF12— Screenshot
Error Handling
Unknown View
1
Conflicting Flags
1
Wrong View for Flag
1
Use Cases
Renderer Development
Test rendering systems in isolation:Asset Debugging
Verify sprite/texture loading:Performance Tuning
Benchmark render paths:Screenshot Generation
Generate reference images:Creating Custom Views
Views are defined incrimson/views/:
crimson/views/__init__.py:
See Also
- Run Command — Launch full game
- Quest Debug — Debug quest spawns