Technology / The stack
Krump Battles is a standalone Unity executable that has been deployed to public venues and run unattended for hours at a time. Everything below is shipping code, not a proposal.
Stage 01 Capture and segmentation
A krump round is continuous. A game needs discrete, interruptible units. The first stage of the pipeline is the translation between the two: raw motion capture takes are segmented into individual actions, each with a clean entry and exit pose so it can be triggered at any point and blended back to neutral without a pop.
Cleanup work sits here too — foot sliding, jitter and contact correction — because at projection scale the audience is watching a body they recognise, and the errors a small screen forgives become obvious at two metres tall.
| Input | Raw motion capture takes, per dancer |
|---|---|
| Output | Discrete .anim clips: bounce idle, jab, whip, stomp, transitions |
| Volume | 5–6 clean actions per character, across 3 characters |
| Cleanup | Foot contact, jitter, pose correction |
| Constraint | Every clip must loop or resolve back to the bounce |
Stage 02 Retargeting and likeness
Motion captured from one body does not simply play back on another. A heavier dancer moves with different weight distribution than a lighter one, and if the retarget is naive that difference is exactly what gets lost.
Each dancer gets a rig built to their own proportions, with bone mapping and pose correction tuned so their motion still reads as theirs after the transfer. This is the step that makes the roster meaningful: without it, three characters would be three skins over one animation set.
It is also the step that makes the roster a product rather than a set of one-offs. The mapping work is the same shape every time, which is what puts a price and a schedule on adding a fighter.
| Rig | Custom Character Creator 5 avatar, per dancer |
|---|---|
| Mapping | Explicit bone mapping from capture skeleton to CC5 hierarchy |
| Correction | Per-bone pose correction to preserve proportion and weight |
| Likeness | Face, build and battle clothing modelled to the dancer |
| Engine target | Unity, HDRP materials and lighting |
Stage 03 Animator and input
Clips are authored into a Unity Animator controller using blend trees and state machines, then driven by Unity’s Input System so a physical button resolves to a transition in real time.
Moves do not snap. The controller blends out of the bounce into the action and back again, which is what preserves the continuity a dance form depends on and a punch-trading fighter does not need.
Each player’s chosen character and physical joystick are captured at the select screen and carried into the battle scene, so two sticks at one cabinet stay attached to the right fighters.
Arcade, gamepad and keyboard all resolve through a single action map. A new control surface — a floor pad, a camera-based input — is a binding change, not a rewrite.
Stage 04 Render and projection
Most games assume a rectangle in front of one person. This one assumes a concrete surface in front of a crowd, and the render path is built for that from the start.
The scene, the HUD and each player are rendered to separate render textures and composited into mapped quads. That separation is what lets the output be reshaped to fit an irregular surface without re-authoring the scene.
A dedicated masking camera renders flat-colour silhouettes of the players on their own layer. On a projection surface a silhouette holds up where a fully lit model washes out, and it lets a live dancer read against their avatar.
Bloom, chromatic aberration, noise, motion blur and aggressive contrast. These are the art direction, but they are also a practical response to projected output, where contrast is the first thing a room steals from you.
Stage 05 Deployment
The build ships as a standalone Windows executable driving a projector and one or two arcade sticks. At an activation that means hours of continuous operation, handled by people who did not build it, in the dark, in the cold, with a queue waiting.
Three events in, the constraints that actually matter are known: calibration time, input recovery, and readability at distance. Those are the notes driving the next build rather than guesses about them.
| Distribution | Standalone Windows executable |
|---|---|
| Engine | Unity, HDRP render pipeline |
| Display | Projector, mapped to an irregular surface |
| Controls | Arcade joystick pedestal, Xbox controller, keyboard |
| Operation | Runs unattended between rounds; no operator console required |
| Deployed | Three public activations |
Roadmap / Engineering
Sequenced by dependency, not by wish. Each item below unblocks the one after it.