The Doom experience uses a keyboard and a mouse or trackpad. It also needs enough room for the game and recording controls. These are limitations of this Doom experience and are not related to what Wax supports.
Use a window at least 960 pixels wide and 640 pixels tall.
Click the canvas to lock your mouse, then move with WASD or the arrow keys and look with the mouse. Ctrl to fire, Space to open or use, Shift to walk. Esc releases the pointer.
Desktop only: this demo needs a keyboard and mouse.
Wax can restore any recorded frame and run new code against the state inside it.
Let’s recover data Doom never exposed or logged.
We’ll replay your recording three times. Each run changes one rule:
Wax runs the same code at every frame, turning isolated values into a history of the run. We’ll correlate movement, combat and game state across that history to reveal relationships Doom never tracked.
Doom makes a great Wax demo: everyone knows it, things happen fast, and because the world is software rendered, you can actually watch the past change right in front of you.
We built this tour around Doom, but we didn’t build these capabilities for Doom. Recording, replay, investigation and changing the rules are all just Wax, and they work the same way outside this demo.
The more complex the system, the more interesting that gets. Doom is pretty small, but the software we actually spend our days inside is bigger, messier and much harder to understand. You can explore recordings directly in the Wax Inspector, or use the recording APIs to build these capabilities into your own tools.
These files are not part of Doom. Written after you played, they let Wax scan the replay type-safely for information the game never logged, tracked, or exposed as events.
query fn reads the complete game state at one restored frame and serializes a typed result. An investigation scans those results across the replay and reduces them into findings.
It carries restorable game state, the input tape, and enough context to reconstruct every frame in Wax.