Computer graphics · Voxel rendering
Voxtapen
Situation
Products that show voxel data (visualization, tools, simulators, design software) need a renderer that scales with what is visible, not with every cell in the volume.
What mattered
- Scenes must stay fast as volume size grows
- Draw cost should follow visible surfaces, not the full solid mass
- Teams should keep authoring in familiar voxel formats (including MagicaVoxel .vox)
- The render path must be owned and extensible, not locked inside a general-purpose engine
Problem
Dense voxel scenes are expensive to render when a general graphics stack treats every solid cell as work, even the ones nobody can see.
Approach
Voxtapen is a computer-graphics render engine for voxels: compact world data on the CPU, only outer surfaces prepared for the GPU, and content from tools teams already use, including MagicaVoxel .vox.
What we delivered
Voxtapen as the graphics core: keep the volume compact, turn it into surfaces for display, import real voxel assets, and ship with a maintained viewer and editor path as the product grows.
Outcome
A voxel rendering core you own: large solid scenes that stay practical to display, less waste in memory and draw cost, and a clear path from volume data to the picture on screen.
Stack
- Rust
- WebGPU
Timeline
Active product. Rendering path, MagicaVoxel import, and editor already in owner-accepted releases; still early, but built to prove each step with real runs, not slides.