Dethkarz demo (Beam Software / Melbourne House, Infogrames 1998, Direct3D)

App id dethkarz_demo, candidate dethkarz-demo (registered 2026-10-11, w5). Evidence: scratch/runs/20261011T0750Z-dethkarz_demo-race-w5/.

Source and licence

Layout the game needs

Startup driver dialog

Headless route (CLI, --batch-size=200000)

  1. Pick Direct3D with mouse down and up:
    • combo arrow at (494,198), batches 300/303;
    • "Microsoft Direct3D" item at (300,236), batches 320/323;
    • OK at (243,288), batches 340/343.
  2. Title "PRESS ENTER" by batch 1000. Send Enter (keydown plus di-keydown:13) at batches 1000, 1150, 1300, 1450, 1600 and 1750:
    • Game Select → Arcade;
    • Car Select (Hyperon Alpha "Arrow"; Begin Race);
    • Metro City (Medium) loading;
    • grid.
  3. Camera flyby until "GO" at about batch 3200.
  4. Up (di-keydown:38 plus keydown) held from before GO does nothing. Release it and press it again after GO (batches 3240/3250).
    • The car reaches 111 km/h in gear 2 by batch 3400.
    • It reaches 219 km/h in gear 3 and position 19/20 by batch 3700.

Route script: route.sh in the evidence folder. With threads off the run is about 36 s of wall time for 3900 batches.

Phone route (WebKit, iPhone 15 landscape, Threads on)

Native Shift firing response (2026-11-01)

Evidence: scratch/runs/20261101-dethkarz-native-fire-control/ (including run2/). Visible firing is confirmed with ordinary Shift input in the original local Direct3D Arcade race. The requested narrower claim of DirectInput keyboard consumption is not established: the observed Shift reader is GetAsyncKeyState, while the traced DirectInput state reads are for the mouse.

Identity and bounds: predecessor MDK2's fresh terminal artifacts and explicit 09:57:24 UTC runtime/source/build release were verified before the 09:58:14 gate; actual baseline f0eda338f29a84929075fc90d26c4b4465ee2356. Original Dethkarz.exe SHA-256 2a18a5cff1807b457a6e043e0c4e18368c66a598819927bc6f54ba5e18b8de41, manifest SHA-256 94b221e38cf7022177ebc514628186462d8fe15baa4e16a091c6d9225f3d248d; all 15 files in the original candidate tree and 4444 source/build identity entries matched before/after. Reused accepted module dd43e4a6624d2449d7133b731d687c32530f7fcf0041a69ba71a09f78c09aaf4: 4392 accepted inputs and 141 retained actual build reads matched, with no rebuild or tracked code/helper/configuration change. Each original recorded 128 actual file-read identities, all matching local bytes, including the EXE, manifest, GOB, Direct3D DLL and sound archive. Discovery also read the Glide DLL; the selected renderer was Direct3D, not the Glide detail path.

Retained observer helpers passed actual synchronous and asynchronous WASM execution with whole 512 MB shared-memory hashes unchanged, host/native clock identity unchanged, and emitted late event 10001 retained in a 64-event tail. Observation covers synchronous whole-file reads and completed descriptor reads up to 24 MiB; async/stream/mmap and loader-internal reads are not covered. Read records flush at process exit. A WASM compilation/hash observation does not prove compiler source reads. Input-state still reports guest-post-queue and button-count coverage as unknown and has no exact event correlation.

Both originals exited 0 after 192.197 s and 80.305 s; minimum free disk was 2,216,583,168 and 2,159,755,264 bytes respectively. Local native only; box ID/state/expiry N/A. No impact, damage, combat outcome, charged-shot mechanics, FPS, audio, browser/GPU, or broader playability qualification is claimed.

Bounded visible-combat attempt (2026-11-01)

Evidence: scratch/runs/20261101-dethkarz-visible-combat/ (including run2/). No visible opponent impact, damage or combat outcome was established in two original-game runs. This is a failed combat attempt, not another firing-only acceptance. The first gameplay obstacle was retaining an opponent in the car's firing line while accelerating and steering: reviewed bolts passed beside the moving targets. A later unexplained driver termination ended the final run before the next approach could execute.

Consumption and identity checks: both runs record actual Shift GetAsyncKeyState(0x10) calls returning to 0x4a819d, with values 0 / 0x8001 / 0x8000 / 0 across press/hold/release, plus consumed Shift WM edges and released key-state snapshots. Actual DirectInput state reads remain 16-byte mouse reads (15 in the first traced windows, 43 in the second); these do not establish DirectInput keyboard-specific Shift consumption. input-consumption.json retains the actual calls and WM snapshots. Known queues empty at the captured releases; guest post queue, button count and exact event correlation remain unknown.

Gate: Incoming 01a196bc-fc1d-7863-8087-8a0327166bb6 fresh launcher final.txt/result.json and its explicit 11:08:26 UTC runtime/source/build release preceded the 11:09:08 UTC gate. Requested baseline was 86bf6a3a; actual main at gate was 09e52ce62b9f55eba6d7b3a182cb2c6bc9a115c2. The 25-minute deadline was 11:34:08 UTC; runtime ended before it. Local native box ID/state/expiry N/A; own process shutdown was delegated.

All 4444 source/build identity entries and all 15 original files/manifest match before/after. Full before/after original archives were member-hash verified, including the original force profiles; no external control config was introduced. EXE SHA-256 remains 2a18a5cff1807b457a6e043e0c4e18368c66a598819927bc6f54ba5e18b8de41; manifest remains 94b221e38cf7022177ebc514628186462d8fe15baa4e16a091c6d9225f3d248d. Accepted canonical dd43e4a was reused only after all 4392 accepted inputs and 141 retained actual build reads matched. Each runtime retained 128 actual file-read identities matching local bytes, including EXE, manifest, GOB and Direct3D DLL. Discovery also reads the Glide DLL; the selected renderer is stock Microsoft Direct3D, not the Glide detail path. Actual runtime module compilation matched the canonical hash; compilation does not prove compiler source reads.

The exact retained observers passed real synchronous/asynchronous WASM execution, whole 512 MB memory hashes unchanged, clock identities unchanged, and late event 10001 retention. Coverage remains synchronous whole-file reads and completed closed descriptor reads up to 24 MiB; async/stream/mmap and loader-internal reads are gaps, with exit-only flushing. Manifest check and scratch evidence verification passed. No rebuild was performed for this documentation-only result. First original: 198.679 s, exit 0, minimum free disk 2,512,642,048 bytes. Second startup was 2,512,535,552 bytes; a later sample was 2,487,459,840 bytes. Both drivers sampled the >2,000,000,000-byte guard while alive, but the second's minimum receipt was lost with its driver; no stronger continuous minimum is claimed. No separate startup/RAM gate or foreign cleanup was used. Own runtime/driver PIDs and groups 3561681/3561680/3565454/3565451 are absent; no watcher was created and no new wa-child-* temporary files remain. Combat stays open; no FPS, audio, full-playthrough or broader qualification is claimed. Single assignment stops.

Open