Evolva (demo)
Computer Artworks / Interplay, 2000, Direct3D 7 squad action (four
"Genohunters", third person). Candidate evolva-demo, app evolva_demo,
local only.
Source and layout
- archive.org
Evolva_1020,evolvademo.zip(31,649,248 bytes, sha1 40e5cbc407348c8357d97d3e872f1af43fe93276). archive.org sometimes answers with a 170-byte nginx 500 page; the fetcher's sha1 check catches it. - The zip holds
evolvademo.exe, an InstallShield 5 self-extractor. 7z opens it toDisk1\data1.cab. The candidate extracts five file groups withunshield(ortools/is5-extract.js) and merges them intoinstalled/evolva(guestc:\evolva):- Resources (Animations, DMLevels, Informs, Level, Music, Sounds, Textures)
- Program Executable Files (
Evolva.exe) - Program DLLS (
4xm_sdk.dll, the FMV codec, declared indlls) - Language DLL (English) (
EvolvaLang.dll) - Registering DLLs (
ImageLoader.dll)
ImageLoader.dllis the "Media Loader" COM server. WhenCoCreateInstancefails, Evolva callsLoadLibrary("C:\evolva\ImageLoader.dll")andDllRegisterServer, then activates it again through the registry. Without the file it stops on "A file required by Evolva ... (ImageLoader.dll)".- The installer writes
HKLM\Software\Computer Artworks\Evolva Demo\1.0(InstallDir, ResourceDir, SaveDir, DNADir, ScreenShotDir). The game reads one search path per asset class (TextureDir, SoundDir, MusicDir, LevelDir, AnimationDir, InformDir, DMLevelDir, SceneDir, BackdropDir, FMVDir).startupRegistryseeds all of them. The game then callsSearchPathA("C:\evolva;c:\evolva\Textures", ...).
Emulator bugs it found (all fixed)
CoCreateInstance(CLSID_DirectInput)was unknown, andIDirectInput::Initializepopped 20 bytes for its 3 arguments. That corrupted the caller's EBX/ESI/EDI, so the next CreateDevice got a NULL out pointer. Fixed in c9b5904a4.- D3D7
EnumDevicesleftD3DDEVICEDESC7.deviceGUIDzero, so the game threw "D3DMgr: Could not set up preferred device". Fixed in f44edf4e7. SearchPathAtreated a semicolon-separatedlpPathas one directory. No texture, font, sound or movie was found, and every frame was white.- Vertices without a specular colour got specular 0. That covers D3D-lit
D3DVERTEX, and LVERTEX/TLVERTEX FVFs without
D3DFVF_SPECULAR. The specular alpha is the vertex fog factor, so with FOGENABLE on (Evolva sets no fog mode) the whole 3D world drew as the fog colour, 0xff788c78. They now get 0xFF000000 (black, no fog).
Route (headless, --batch-size=100000)
The game cursor is DirectInput relative motion. Absolute clicks don't move it;
use relmousemove. The cursor starts at the screen centre.
- About batch 200: the main menu (New Game 137,143; Options 480,377).
300:relmousemove:-183:-97:10, then click: team select (four animated Genohunters). Confirm checkmark at about 560,435 (1200:relmousemove:423:292:12, click at 1250).- About batch 1600: Mission Briefing "Land 4" (rotating planet). Click the same checkmark again (batch 2400).
- The level loads for about 13,000 batches (white screen). By batch 16,500: gameplay, a Genohunter in the jungle with four squad views and radar.
- Options > Configure Controls has the authoritative chart: W/S (Cursor Up/Down) forwards/backwards, A/D (Cursor Left/Right) strafe, Left Ctrl Walk, Left mouse Fire, Left Shift Beam Up, Right mouse Jump, 1-0 and NumPad 1-0 weapons, mouse wheel next/previous weapon.
Historical limits (2026-10-11)
Movement and fire in the mission (only reaching it), the browser and touch layout in a running mission (the load is long), audio, the 4XM FMVs (the Intro FMV option is off), multiplayer.
2026-10-31: original browser launch stops before the menu
Run scratch/runs/20261031T1656Z-evolva-native-control/ made one ordinary
registered evolva_demo launch. The first concrete failure is the game's
startup dialog: “A file required by Evolva to run properly is missing or has
not been installed correctly (ImageLoader.dll). Please re-install Evolva.”
Reviewed 01-menu-wait.png shows the dialog, and console.jsonl records the
same MessageBox. 02-imageloader-first-failure.png is a later desktop frame
without the dialog painted; it does not demonstrate recovery. No menu or
mission was reached, and no guest movement, look, or fire input was sent.
The historical jungle scene (messageboard entry 22136) remains scene-only
evidence, explicitly without mission input or browser verification.
Cheap preparation found all 1,161 manifest files at their recorded sizes
(47,453,646 bytes), plus the separately registered 4,325,376-byte EXE.
original-inputs.json pins all 1,163 fixture files including the manifest;
their hashes match before and after execution. In particular,
ImageLoader.dll exists (172,032 bytes, SHA-256
b252056a62cd7e3c53e26c9f39e5b6c7acee5d7bd2f35554871efcfa6adb94e5)
and was actually served with HTTP 200 and that hash. The fixture was not
changed, copied, or re-extracted; the upstream archive hash was not rechecked.
The fresh public desktop selection excludes this app. No later gameplay
qualification or runtime rejection was found; the candidate's local-only,
no-redistribution restriction still applies.
The tested module was the existing UT0542/1642Z frozen build, SHA-256
9b4e39a22c9c3abe4608e5f55e2db0eb5818da59cec04bc7b7406a0b8504d1b8,
with its complete 295-file source snapshot and seven compiler files verified
before and after execution. Its recorded source HEAD is a08890203bb22db6,
with the retained predecessor dirty patch and successful build log; it is
not a build of the current documentation HEAD. The frozen app registration
matches the current registration, with no extra arguments or launch patches.
The browser received 105 pinned source/module responses. No build or frozen
hardlink was modified.
The sole runtime lasted 16:59:26–17:00:13 UTC, after the new UT2003 execution
FULLRELEASE at 16:58:19 and an independent entire Chrome/global-crashpad/profile
PID/start gate under inherited lifetime FD9. Chrome 151.0.7922.108 used the
normal WebGL selector, default guest worker, threads, and stable 1024×768
viewport. Isolation was true before any guest input, and all 166 observed
HTTP responses carried COOP same-origin and COEP require-corp.
No render-owner endpoint or graphics device existed at the failure, so
selected WebGL does not establish executed WebGL rendering. The only three
trusted native events were the balanced host Launch click and its mouse move.
Explicit shutdown completed with Chrome/controller/wrapper/monitor exit 0,
no monitor signals, all owned runtime/supervisor identities absent, both
ports closed, profile removed, no held inputs, and full flock available.
Disk remained above the 2.1 GB stop threshold. Boat ID/state/expiry: N/A.
focused-check.json records the identity, HTTP, input, and cleanup checks.
No production change or retry was made in that run. The demonstrated issue was an ordinary
browser startup failure at the ImageLoader load/registration dependency;
the exact failing call and generic root cause were then unresolved.
Movement/look/fire, browser mission gameplay, touch, FPS, audio, multiplayer,
and full-27 coverage remain unqualified.
2026-10-31: worker DLL registry omission repaired; visible menu still blocked
Run scratch/runs/20261031T1707Z-evolva-imageloader-cause/ investigated current
main 9534a8b16, rather than editing or reusing the frozen UT0542 source.
The unchanged diagnostic browser reproduced the dialog (01-diagnostic-startup.png,
reviewed). Its trace proves that LoadLibraryA and GetProcAddress succeed,
and the real DllRegisterServer executes and writes the MediaLoader class
keys. It never reaches the second activation. Original EXE disassembly places
that failure on the negative DllRegisterServer result branch after
0x6ef431, rather than a missing file or export.
ImageLoader's registration routine calls OLEAUT32 ordinal 161, LoadTypeLib,
through IAT RVA 0x1f15c at DLL RVA 0x143a4, with a .tlb fallback at
0x1442f. The built-in handler returns TYPE_E_CANTLOADLIBRARY (0x80029c4a).
This inner HRESULT is a source/disassembly inference, not a captured return-value
trace. The causal host discrepancy is independently reproduced: classic browser
Workers neither imported dll-registry.js nor had its window-only export;
process-boot.js also looked only at window. Their dynamic dependency walker
therefore skipped the registered, ordinal-only OLEAUT32 dependency. Node's
require path retained the registry, explaining the historical CLI difference.
The generic repair imports the existing DLL registry before process boot in
lib/guest-worker.js and exposes/reads it through globalThis in
lib/dll-registry.js and lib/process-boot.js. No registry entries, guest files,
COM results, launch arguments, interpreter handlers, or thread-manager code were
changed. The two whole-file callback census seals were updated after reviewing
this bootstrap-only delta; callback/context ownership assertions remain pending.
test/test-worker-dll-registry.js runs the production browser bootstrap and
dependency walker in a window-less realm, using synthetic PE imports. It fails
on unchanged source because OLEAUT32 and its nested CRT dependency are skipped,
then passes with the repair. It also checks existing-module skipping, system
fallback, fatal missing vendor dependencies, and versioned Worker imports.
The repaired-browser/ subdirectory holds the single bounded original browser
attempt after repair. It actually served the existing 598,288-byte OLEAUT32
(SHA-256 baeb2f7c1b8be56738d34e1d1ddf8e0eebd3a633215dc1575e14656be38b939d),
completed the native type-library registration, and reached the second
MediaLoader CoCreateInstance at return address 0x6ef487; the host reported
COM_RESOLVED_INPROC (2), resolving the real DllGetClassObject for guest-side
activation, rather than an activation HRESULT. Execution proceeds to menu asset
loading. The ImageLoader startup dialog is cleared.
Reviewed 01-repaired-startup.png, 02-menu-wait.png, and
03-native-canvas-focus.png show a white game surface, not a visible menu.
The legacy WebGL endpoint owns an actual 640×480 WebGL2 target, with context
not lost, completed draws, texture uploads, fences/readbacks, and zero reported
GPU errors/fallbacks. Menu texture files were served successfully. The balanced
native focus click reached DirectInput and acquired pointer lock on screen,
but the surface stayed white. No blind menu route, jungle transition, movement,
look, or fire was attempted or qualified. Next investigation must distinguish
GPU pixels, D3DIMGpu.fence/_writeBack, shared DIB/flip ownership, and browser
presentation (lib/d3dim-gpu.js, lib/d3d-render-worker.js, then the presentation
consumer). Draw counters alone do not establish correct visible rendering.
The full flock /tmp/wine-build.lock bash tools/build.sh passed under lifetime
FD9 /tmp/wine-browser.lock; eight focused loader/COM/bootstrap/cache checks
passed. An earlier repaired build stopped at the census review gate before
runtime; that failure is preserved in repair/. The tested current WAT module
is SHA-256 078d81cba6ab755d6a05e5e234a259df9e867ecc8848899705a45739fab0e9a9
(1,898,571 bytes), identical between the diagnostic and repaired JS runs.
Their source manifests identify the exact changed JS bytes; the successful run
verifies 295 source files, seven compiler files, the original 1,163 fixture
pins, and the two existing system DLL pins before and after execution. All
202 HTTP responses carried COOP/COEP; isolation, threads, default guest Worker,
normal WebGL selection, and stable 1024×768/defaultViewport-null configuration
were verified before guest input. All seven native events were trusted and
mouse down/up were balanced. Original ImageLoader bytes retain the hash above.
Both runtimes followed the new SlaveZero terminal no-runtime release and independent whole-Chrome/global-crashpad/profile PID/start gates. The repaired guest ran 17:19:09–17:20:34 UTC; explicit cleanup returned Chrome/controller/ wrapper/monitor 0 without signals. The final PID/start scan found all owned runtime/supervisor identities absent, both ports closed, profile removed, held inputs empty, and lifetime flock available. Minimum monitored free disk was 2,613,260,288 bytes. Boat ID/state/expiry: N/A. No further browser/heavy CLI, public deployment, redistribution, guest overrides, or successor worker was launched. The app remains local-only and excluded from the public desktop; browser menu/jungle gameplay, movement/look/fire, audio, and touch remain open.
2026-10-31: white presentation repaired; collapsed geometry remains
Evidence: scratch/runs/20261031T1733Z-evolva-white-presentation/.
The first diagnostic used the existing GPU readColor() and shared surface
metadata without forcing a draw, flush, or writeback. Actual GPU pixels, its
cached 16-bit DIB, both flip-chain DIBs, and the window's canonical back canvas
were black. The browser screen and _dxFrameLayer were white. The second
capture isolated the divergence: explicitly presented primary slot 12 and back
slot 13 were all zero, while unrelated offscreen slot 15 was all white. Gamma
was unset. lib/host-imports.js rejected the explicit primary because a byte
sampler equated all-zero storage with “never written”, then selected the white
offscreen surface. This was a presentation ownership defect, not evidence of a
GPU fence or DIB writeback defect.
The generic repair keeps a live, explicitly presented primary authoritative,
including all-zero frames. Existing surface retirement (dx_trace kind 22)
already clears its ownership; a recreated surface can use fallback until it
presents. The unused content sampler is removed. The new
test/test-dx-explicit-primary-black.js fails against the old implementation
and passes after correction, covering 8-, 16-, and 32-bit black primaries,
retained writes, clears, retirement/recreation, and replacement presentation.
The older blank-primary test now exercises actual retirement instead of
asserting content-based ownership. The callback census host-imports seal was
reviewed and updated; no callback/context ownership claim was added.
lib/d3dim-gpu.js and lib/d3d-render-worker.js remain unchanged.
One corrected original/default-worker WebGL browser attempt ran
17:41:00–17:42:17 UTC. Reviewed repaired-browser/01-authoritative-primary.png
and 02-projection-boundary.png are black, matching GPU, shared DIB, canonical
canvas, and frame layer. White presentation is fixed; no visible menu, jungle,
movement, look, fire, or gameplay screenshot is qualified. Only trusted,
balanced host Launch input was sent; no blind guest menu route was attempted.
The remaining captured boundary is upstream vertex projection. The last
four-vertex triangle-strip descriptor has TL vertex type 3; all four screen
positions are (0,0), with z=0.5, rhw=1, white diffuse colour, and nonzero
texture coordinates. The queued GPU vertices are likewise collapsed. Decoded
texture caches contain nonzero pixels and many colours. The captured render
workspace has zero viewport rectangle at offset 3088, zero XY scale at 3104,
and zero origin at 3120, despite populated matrices. These are snapshots, not
a captured viewport setter call or HRESULT. The existing bounded draw trace
stopped at an unsupported legacy call with no commands; it does not establish
call ordering. Next work must capture the actual device/viewport API version,
setter arguments and return, selected viewport descriptor, and their path
through src/09ab-handlers-d3dim-core.wat into vertex projection. No viewport
default, guest state edit, or speculative renderer bypass was introduced.
Ten focused presentation/GPU suites and callback census check pass
(focused-tests.log); the causal before-failure and after-pass are preserved.
The corrected full flock /tmp/wine-build.lock bash tools/build.sh passed under
inherited lifetime FD9 /tmp/wine-browser.lock. The exact executed module is
SHA-256 078d81cba6ab755d6a05e5e234a259df9e867ecc8848899705a45739fab0e9a9.
Each browser attempt cached and hashed current checkout source bytes, rather
than serving an old frozen image: 295 source files, seven compiler files,
1,163 original fixture pins plus two system DLL pins matched before and after.
Per-response receipts identify the bytes actually served; all 202/203/203 HTTP
responses carried COOP/COEP. Isolation, normal WebGL, default guest Worker,
1024×768 geometry and defaultViewport-null were checked before input. Large
pixel captures are losslessly stored as .json.gz, with summaries/hash receipts.
All three bounded attempts followed SlaveZero FULLRELEASE 17:29:35 and their own independent whole-Chrome/global-crashpad/profile PID/start gate under FD9. Explicit shutdown returned all runtimes/controllers/wrappers/monitors zero, without monitor signals. Release proofs find every owned runtime/supervisor PID/start absent, both ports closed, profiles absent, held input empty, and lifetime lock available. Lowest monitored free disk across all attempts was 2,354,913,280 bytes. No further browser/heavy CLI is planned in this task. Boat ID/state/expiry: N/A. The candidate remains local-only; no public desktop selection, deployment, redistribution, guest overrides, or audio/worker changes.
2026-10-31: render-target interface repaired; native menu and briefing visible
Evidence: scratch/runs/20261031T1749Z-evolva-viewport-projection/.
Two unchanged diagnostics captured the actual original executable's Device7
path before a production edit. IDirect3D7_CreateDevice returns at 0x602520;
the resulting device has the Device7 vtable. GetRenderTarget returns at
0x640892 with S_OK, but returns the surface's canonical Surface2 wrapper
(vtable 8642908), despite the Device7 output contract requiring Surface7.
The underlying slot 5 already has dimensions 640×480. The next
GetSurfaceDesc, returning at 0x640915, receives a 124-byte
DDSURFACEDESC2 and fails with 0x80070057, leaving the dimensions zero.
The guest ignores this failure and constructs D3DVIEWPORT7 {0,0,0,0,0,1}.
SetViewport, returning at 0x640a9d, receives exactly that descriptor and
returns S_OK; its cached rectangle, XY scale, and origin remain zero. Original
draw input uses XYZ FVF 0x1e2 with nonzero coordinates before emulator
projection. This establishes the upstream cause of the collapsed TL vertices.
The earlier static 0x71bd17 candidate was not the observed setter call.
The generic repair in d3dim_get_render_target returns an interface matching
the visible calling device: Device2 → Surface1, Device3 → Surface4, Device7 →
Surface7. These signatures are also specified in the
Windows SDK header.
It obtains the matching wrapper and reference under LOCK_DX, retains COM
identity and the canonical wrapper's vtable, and clears the output on wrapper
allocation failure. No viewport defaults or projection math changed, and
src/09a8-handlers-directx.wat was not edited.
The valid-use regression test/test-d3dim-viewport-projection.js creates an
actual 640×480 render-target surface, creates a Device7, gets its render target,
queries the descriptor, builds the viewport from the returned dimensions,
and projects opposite XYZ corners. It fails against the unchanged core with
the same 0x80070057 descriptor failure and passes after the repair, projecting
to (0,0) and (640,480). It also covers Device2/3 interface views, descriptor
sizes, stable canonical identity/vtable, acquired and released references,
null output, stdcall cleanup, and a stack guard. The full build passed under
lifetime FD9 /tmp/wine-browser.lock with
flock /tmp/wine-build.lock bash tools/build.sh. Five focused suites passed:
viewport-projection, viewport-query-interface, transform-alias, viewport-clip,
and directdraw-surface3-desc. Parenthesis and diff checks passed.
One repaired original/default-worker normal-WebGL route ran
17:58:29–18:02:12 UTC. The read-only API observer now records Surface7 vtable
8650820, GetSurfaceDesc S_OK with 640×480, and SetViewport S_OK with
{0,0,640,480,0,1} and nonzero XY scale/origin. Personally reviewed screenshots
repaired-browser/01-repaired-menu.png, 05-team-select.png, and
08-native-briefing.png show the textured main menu, four rendered team
characters, and Land 4 mission briefing with a rendered planet. Trusted native
relative mouse movement and clicks reached each screen. These are menu and
briefing evidence, not jungle gameplay screenshots.
The next exact boundary occurs at 18:01:37 UTC after the briefing confirmation:
ini_get_string throws VfsPendingError because
c:\evolva\level\level4.lvl is backed by an async-only VFS provider.
The retained stack is _vfsReadText (lib/storage.js:693) → _iniResolve
(:714) → ini_get_string (:1622) → guest RPC. The render endpoint then
closes and the guest Worker disappears; the next capture command correctly
rejects further input at its Worker gate. The next investigation is the host
INI read/materialization boundary with the original level bytes. No jungle,
movement, look, fire, audio, or touch qualification is claimed. There was no
retry, asset/INI/save edit, guest override, or expansion into storage code.
The repaired module SHA-256 is
bfb6ef7c5a20ce2f439a02c64e2ed94df2543f6ebd7ba03f7b0e0de275a955b6
(1,898,654 bytes). Each runtime served actual current checkout bytes and
verified 362 source files, 866 compiler/tool files, and 1,165 original fixture
pins before and after; response receipts identify the exact served bytes.
All 202/201/289 HTTP responses carried COOP/COEP. Isolation, normal WebGL,
default guest Worker, threads, 1024×768 geometry and defaultViewport-null were
checked before guest input. All 33 native events were trusted; the five mouse
down/up pairs were balanced. Diagnostic observers were read-only and their
hook/result/memory preservation check passed.
All attempts followed the current SlaveZero NEW FULLRELEASE 17:50:44 and an
independent entire-Chrome/global-crashpad/profile PID/start gate under inherited
FD9. Explicit shutdown returned controllers, monitors and wrappers zero without
signals. full-release-proof.json checks all 58 recorded owned identities
absent, the entire Chrome/crashpad set empty, all three ports closed, profiles
removed, held input empty and lifetime lock available. Minimum monitored free
disk was 2,459,082,752 bytes. Boat ID/state/expiry: N/A. No public deployment,
new worker, successor, or further browser/heavy CLI was launched.
2026-10-31: async profile materialization repaired; native jungle control visible
Evidence: scratch/runs/20261031T1817Z-evolva-async-ini/. The previous
18:01:37 failure is repaired at the generic host profile-read boundary. An
async-only VFS profile now records the exact selected entry in the calling
thread's existing pending-I/O slot, materializes it, yields through IO_WAIT,
and retries the original import thunk. Readiness and consumption share one
host RPC. Pending reads publish neither output nor EAX and preserve the full
stdcall frame. Separate status/result cells preserve every signed profile
integer, including 997. Concurrent readers share one in-flight materialization;
retired threads and replaced entries do not revive stale operations. Provider
failures propagate rather than becoming missing-file defaults. Existing INI
path/basename lookup, localStorage priority, byte decoding, case, quotation,
section and integer behavior remain in the existing readers. No preload,
per-game exception, asset edit, or scheduler/RPC change was introduced.
The public string and integer A/W readers, section reader, and StructA reader use this boundary. StructA retains its existing WAT decoder, permissive native nibble mapping and checksum behavior, including decoded output on checksum failure. A review caught its initial separate preflight/read RPCs; the final version reads into a private temporary/result cell in one RPC and frees that allocation before yielding. Its compiled regression replaces a resident file with an async provider after readiness, verifies pending EAX/ESP/output atomicity, then checks successful and failed checksums and exactly-once stack cleanup. This StructA closure followed the sole browser run and is covered by the final compiled regression/full build; it was not rerun in a browser.
test/test-ini-async-vfs.js exercises real async VFS providers and compiled
public A/W import handlers, original thunk retry, unchanged stack guards,
truncation, sections, signed integer results, per-thread waits, shared fill,
thread retirement, provider failure/retry, namespace/write replacement,
persisted overrides and basename fallback. The original c95f363a9 source
fails the same valid-use read with VfsPendingError; repaired source passes.
A separate causal test uses the untouched 254-byte original level4.lvl:
old FAIL, new PASS returning TerrainMesh=Level4-level.msh, one fetch and
unchanged SHA-256
29705723c337c41041344f2e3bd1af4506e03d36da05debd151f3730433c1236.
The original/default-worker normal-WebGL runtime ran 18:33:18–18:40:37 UTC. At 18:35:16.790, the original level read returned pending status 997; at 18:35:16.804 it completed with length 16 and the same ESP 122680152. The Worker survived, subsequent profile reads completed normally, and the jungle became visible. Personally reviewed screenshots show:
13-loading-or-jungle.png: original jungle, controlled green Genohunter, textured ground/rocks/plants, radar and squad views.14-native-forward-held.pngand14-native-forward.png: native W down/up, running stride and advanced position.15-native-look.png: trusted relative mouse input turns the view toward the rock wall.18-native-fire-short-held.pngand20-native-third-fire-held.png: native left fire, raised firing pose and visible discharge after native weapon 3.
This establishes visible native movement/look/fire in the original jungle.
Audio, touch, sustained combat, performance and mission completion remain
unqualified. No further failure or scope expansion occurred in this run.
All 55 native events were trusted; eight mouse pairs and three key pairs were
balanced. The 1024×768 browser used defaultViewport:null, default guest
Worker, threads and normal WebGL, with isolation checked before input. All
1,158 HTTP responses carried COOP/COEP. Exact served receipts and unchanged
before/after pins cover 362 source files, 866 compiler files, 1,165 original
fixture files and 134 served byte identities. The executed module SHA-256 was
3c832ec6f3dc3cf2f907e29de37a0315a1a1cc8d9b5fd17a402eaab3500b2548
(1,898,724 bytes); its exact source delta is retained in build-identity.json.
The run followed current SlaveZero NEWFULLRELEASE and published main, with an
independent entire-Chrome/global-crashpad/profile PID/start gate under
inherited lifetime FD9. Explicit quit reaped controller, monitor, lifetime and
supervisor without signals. full-release-proof.json verifies all 19 recorded
identities absent, the entire browser set empty, ports 37247/37433 closed,
profile gone, held input empty and lock free. Minimum monitored free disk was
2,402,349,056 bytes. Large diagnostic JSON/logs were losslessly gzip-compressed
with roundtrip SHA checks; lossless-evidence-archive.json records recovery.
Boat ID/state/expiry: N/A. No new worker, successor or public deployment.
After the StructA closure, the final causal regression, full flock build and
fifteen existing focused suites all passed again under inherited FD9. These
cover storage/registry, profile quotation/section/struct, lazy VFS entry/miss,
RTF lazy open, Worker imports/RPC exceptions/COM pending slots, viewport
projection/query/clip, transform aliasing and Surface3 descriptors. Build
checks also passed handler stack/epilogue, A/W clone, callback census and test
tier validation. Final module SHA-256:
d39f362187ce89abda47fa53bca6bb6576badd8d21b78e44c6fbad973d1636d8
(1,898,762 bytes), recorded separately in final-verified-build.json.
2026-10-31: sustained native combat, incoming hits and health loss
Evidence: scratch/runs/20261031T1848Z-evolva-native-combat/.
This sole bounded browser run executed the final StructA-closure module
d39f362187ce89abda47fa53bca6bb6576badd8d21b78e44c6fbad973d1636d8
from published main cd5c5fd86d0bdd859d4d4957687f49e378886b05.
The original native menu, team selection and Land4 briefing led back into the
jungle. The unchanged original level profile returned pending 997 and then
length 16 eight milliseconds later, with ESP 122680152 preserved. No further
emulator failure was captured; no production source or fixture was changed.
Cheap preparation read the original mission text, entity placements and EXE control table. The mission asks the player to find the underground entrance and destroy the bio-signature. Native defaults include W/A/S/D movement, relative mouse look, left fire, right jump, number-key weapons, F1–F4 squad selection, T grouping, O objectives and Shift beam-up. These informed trusted input only; original assets, INI, saves, guest memory and clock were preserved.
Personally reviewed screenshots establish the following narrower outcome:
13-native-jungle-check.png,18-advance-toward-opening.pngand19-follow-jungle-channel.png: living squad and sustained native movement along the jungle channel.21-select-ranged-weapon.png: a nearby orange/brown creature, blood at the controlled Genohunter and a red damage overlay in a squad view.35-cross-water-toward-objective.png: incoming flash from the ledge, blood at the controlled character's head and a depleted green health track.38-fire-up-at-ledge-target-held.pngshows further depletion while firing.42-close-fire-on-ledge-held.png: squad views one and four are black and control has transferred to Geno two, consistent with native squad losses. F3 selection and subsequent movement remain functional in45-heavy-control-view.pngand46-heavy-advance-toward-objective.png.52-heavy-fire-at-ground-creature-held.pngand54-heavy-advance-and-fire-held.png: a visible large armored creature and native firing poses.57-heavy-close-attack-held.pngshows close contact, blood and nearly depleted health. By58-heavy-continue-close-combat-held.png, squad view three is black and control has returned to the last Geno two.61-last-geno-return-fire-held.pngand63-last-geno-native-beam-up-approach-held.png: the surviving Geno remains controllable near creatures.65-native-combat-end-state.pngshows the responsive original pause menu after combat; no save/restart was selected.
Read-only PNG measurements corroborate visible health loss. On row 581, green pixels in the same first squad health track decrease 56 → 30 → 21 → 0 across screenshots 13/35/38-held/42-held. The third squad track decreases 31 → 18 → 3 across 45/54-held/57-held before its view goes black in 58-held. These are image measurements, not native numeric health values. Outgoing player hits, enemy kills, DNA pickup, underground transition and objective completion remain unverified. Blood or nearby creature geometry alone does not establish a successful player attack. No audio, touch or performance claim is made. The next control task is a clearly live target with reviewed before/impact/after evidence, then navigation to the original underground entrance; this run establishes no new repair boundary.
The 18:51–19:06 UTC run used the default guest Worker, threads, normal WebGL,
audio and clock, a native 1024×768 window and defaultViewport:null. All 253
native events were trusted, with 17 mouse and 29 key pairs balanced. Before
and after pins match all 362 source, 866 compiler and 1,165 original fixture
files plus the exact module. All 1,158 HTTP responses carry COOP/COEP;
1,130 successful served receipts join pinned hashes (1,106 distinct paths).
The shared-memory observer preservation unit, harness syntax, identity,
input-balance and release checks passed. This findings-only update does not
claim another full build; the final module's full build and fifteen focused
suites are recorded above.
Current SlaveZero release/publication and independent entire-Chrome,
global-crashpad/profile PID/start gates preceded launch under inherited
lifetime FD9. Explicit quit reaped controller, monitor, lifetime and supervisor
with zero exits and no runtime signals. Release evidence verifies all 19
recorded identities absent, the browser set empty, ports 39227/34415 closed,
profile gone, held input empty and lock free. Minimum monitored free disk was
2,316,406,784 bytes. Retired viewport/input-state/console diagnostics were
losslessly gzip-compressed with byte-for-byte roundtrip verification;
lossless-evidence-archive.json records recovery. Boat ID/state/expiry: N/A.
No agent, successor or public deployment was launched.