Slayer is a Go renderer with procedural geometry, volumetric light, astronomical scenes, a Metal backend for macOS, a photographic darkroom and its own music synthesizer. You can make a small picture, build a forest, light a fictional spacecraft or put a moving world to music.
New here? Make your first picture.
Then follow the build guide, or inspect your setup
with ./bootstrap.sh --check.
Models come from the manufactory: dimensions, profiles, branching rules and seeds. We generate the geometry with math. We do not build a world by importing a conventional asset collection.
| You want to… | Start here |
|---|---|
| understand Slayer and make something small | Getting started |
| get the tools and build | Building and bootstrap |
| understand the light in a picture | How light works |
| choose careful science or a fast film | Rendering modes |
| understand the renderer's faster paths | Optimizations |
| choose music or drive lights from a song | Music |
| make a new mathematical model | Making models |
| contribute code and test it | Contributing · Testing |
| understand render scheduling | Azazel |
flowchart LR
A[Mathematical recipes] --> B[Scene and camera]
B --> C[Trace linear light]
C --> D[Develop the picture]
D --> E[Image or film]
F[Score or audio] --> E
F --> B
A set describes the world. A job describes the photograph or film. The renderer follows light; the darkroom chooses how it prints. A score can supply sound alone or cue the scene's lights and motion.
The MCRN Larson is a saucer made from revolved profiles, a glass shell, angularly arranged portholes, material optics and programmed lights. Its landed version adds shared stair geometry and a tripod. It is an authored fictional design, not a claim of spacecraft engineering.
Trees combine seeded branching scaffolds and recursive shoots carrying individual needles. Shared prototypes let a forest reuse geometry while retaining real gaps for rays and light. Detail changes how a specimen is represented, rather than turning every needle into an enormous scaled leaf.
See how both are constructed →
After setup and a Game build, from the checkout root:
game run slayer -- assess jobs/first-picture.yaml
game run slayer -- draw jobs/first-picture.yaml
game run slayer -- draw jobs/first-film.yamlThe starter picture uses the CPU. The short film adds synthesized sound;
movie output needs ffmpeg. Larger scenes have their own data and backend
requirements. This development branch still has private review dependencies
and a local Celestial pin: the build guide explains what must be prepared.
Renderer · Examples · Package map · Job format · Caches · Project notes
For a problem report, include the build revision, exact command, job or minimal scene, expected result and actual error. For a change, start with the contribution guide and a focused test. You can work on one part of Slayer without running every render in the repository.