.kkrieger Chapter I beta

Original .theprodukkt Windows game, Breakpoint 2004. User TG73/74 identified the title.

Recoverable package

Source: https://files.scene.org/view/parties/2004/breakpoint04/96kgame/kkrieger-beta.zip

Download: https://files.scene.org/get:fi-https/parties/2004/breakpoint04/96kgame/kkrieger-beta.zip

Archive: 102042 bytes; SHA-1 f46b0fd0e777c33c79e16cb5453db8b0b4bfb91b; SHA-256 0de0b9abafd78cf7f57fb264c7136ace52b2653f5c675574d0f10eda0a654c9f.

Recover with node tools/fetch-candidate-corpus.js --id=kkrieger-beta. Extraction preserves all three archive members under game/. Preserve the original archive separately for redistribution; Git does not retain ignored binaries.

The archive readme permits spreading the original unmodified archive without charging for the game and requires credit to .theprodukkt for public presentation/publication. This record is not permission to repackage stripped files. The scene.org archive includes its archive notice; it is preserved unchanged.

Compatibility scope and evidence

2026-10-14: fresh pinned download and extraction succeeded on baseline 38ed9da0b plus recovery fix14cc377a7; generated browser companion manifest and executable presence verified. No guest execution or gameplay acceptance yet; no desktop promotion or deployment.

Readme requirements: DirectX9.0b, pixel shaders1.3,512MB RAM. Packed procedural-generation startup may be substantial; no timing measured. Controls: WASD movement,Space jump,left mouse fire,1–5 weapons.

Corpus CLI dry-run currently fails before selection on an unrelated existing Baldur's Gate interactive-demo source assertion (test expects bg-demo/BG Demo.iso, manifest uses Silver Edition ZIP). Neither entry changed here. Resolve separately before using that broad harness.

Separate-box startup check (2026-10-14)

Clean main 9ab60e86c2108a841b437e3aa3bd1b2b4ae031d3 built successfully on temporary Boat bx_tgbme2h7 through the documented exec API. Module SHA256: e6ac188dd8c7b16d04eaa4b74446ab2c4ab211422738709e33cffda5db444e7e. Fresh original package acquisition passed. SSH was not used.

The direct CLI smoke lacked a GPU window and repeatedly reported D3D9 requires a GPU window; it was stopped rather than treated as a game failure. A separate headless Chrome run used the normal browser backend and a temporary in-page app entry pointing at the original executable and its companion files. No guest patch or capability override was applied. The page reported non-isolated threading; SwiftShader was allowed by Chrome's launch flags.

The browser created the kk window, then the guest exited before a visible menu. At the 30-second capture the desktop was blank and the runtime log showed a guest exit at 0x00801924, preceded by 0x0080191f. Exit reason remains undiagnosed; a zero harness exit is not game success. No player input, gameplay, audio or FPS acceptance.

Evidence: scratch/runs/20261014-kkrieger-browser/ contains the probe, build/browser logs, three screenshots, state captures and dashboard result. Existing corpus browser/CLI configuration already supplies a launch route; no duplicate registry entry or desktop promotion was added. Next: a bounded original-browser startup run with named Direct3D9/API failure tracing to identify the early-exit condition.

The subsequent named-API run (scratch/runs/20261014-kkrieger-browser-api/, 21:27 UTC) reached Direct3DCreate9, GetDeviceCaps, CreateDevice, and repeated vertex/pixel shader creation before the same exit. These are call-entry traces, not returned HRESULTs; they do not establish shader support or the exit cause. The first trace attempt used an empty Set with an overridden has, which the host's size guard correctly disabled; the recorded follow-up uses a nonempty Set. Next capture API return/failure results using supported tracing before proposing an emulator change.

Returned texture failure (2026-10-14, 21:50 UTC)

On source 43f04c7c4ac8914c385c37a7be96c7e1b9f61623 with the same canonical module hash above, the supported EIP-return hook records S_OK from caps, device creation, and the sampled first twelve vertex/pixel shader creations. This narrows the failure; it does not qualify all shader execution.

The last-API ring then records three CreateTexture calls for 512×512, Levels=0, Usage=0, Format=63, Pool=1, output 0x7ed20460. A separate 90-second return trace confirms EAX=0x8876086c (D3DERR_INVALIDCALL) at all three return sites 0x80454d, 0x804573, and 0x804595, before the same stop at 0x801924. Earlier calls at these sites returned zero; the failure is not universal texture creation. The original 30-second trace ended during asset generation, before the failing calls, and is retained as a timeout rather than success. No guest memory or capability override was used.

The resource gate in src/09ae-d3d9-resources.wat rejects format63. The host snapshot gate, GPU upload paths, and software snapshot gate likewise lack it. Next implement the actual format storage and sampling contract, with creation, lock/pitch, signed-channel, GPU and software conformance tests, then repeat the original-game run. Simply admitting the enum would expose unsupported sampling. The return trace establishes a concrete API failure before the stop; it does not yet prove that fixing it alone reaches gameplay or why the runtime labels the later stop as a normal exit.

Evidence folders under scratch/runs/: 20261014-kkrieger-browser-returns, 20261014-kkrieger-browser-exit, 20261014-kkrieger-browser-texture-returns, and 20261014-kkrieger-browser-texture-returns-long. The last includes the reviewed blank end screenshot, complete log, probe and exact process receipt.