Add controllable lab walking checkpoint with collision and chase camera

This commit is contained in:
UnixNight committed 2026-10-23 23:29:40 -04:00
1 parent 37fa18094f
commit 58424120bb
26 files changed
+1848 -110

No files matched your search

+49 -14
View File
@@ -1,15 +1,52 @@
# Progress — current checkpoint
**Full reconstruction is incomplete.** The current milestone is an evidence-backed
asset recovery toolchain and a native original-scene/animation investigation
runtime with local Linux/Windows packages. No completed playable-scene claim.
asset recovery toolchain and a controllable original lab with local Linux/Windows
packages. This is a movement checkpoint, not a completely reconstructed scene.
## Controllable lab checkpoint
The user confirmed that the previous Windows build loads and renders and asked
to advance. The default now runs walking/backpedaling/turning, ballistic no-gadget
jumping, source-triangle collision, a chase camera, and original idle/run/backpedal/
jump/fall clips. Arrows move, Shift/Insert/numpad0/right mouse jump, R resets, C
pauses for inspection/resumes, F11 fullscreen, Escape quits. The intro is skipped.
Recovered arithmetic and addresses are in `analysis/movement-checkpoint.md`.
Notable corrections: Left precedence; current-yaw target offsets rather than
accumulating destination yaw; Up halves keyboard turn; turning alone decays speed;
no ordinary midair arrow steering; disabled-gadget long hold can repeat on landing;
normal camera eye `(0,180,-350)` and target `(0,99,0)`. Exact original frame order
is unresolved; the transient disabled-gadget state3 transition is collapsed.
Explicit port approximations: fixed60Hz cadence, capsule radius24 and standing
height209.4361, floor-derived model/root separation, static sweep/slide solver and
all-source-triangle mask, camera sphere obstruction, animation state/loop timing.
Collision retains all2869 lab triangles including325 invisible proxy triangles.
Original solver/masks, actor pivot/scale, stairs/dynamic objects and state activation
remain unresolved. At walls the clipped camera can move close to Jimmy.
Verification: 11 collision and13 movement groups pass, including real lab source
geometry, long/high-speed sweeps, held/re-pressed jumping, ten-minute stability,
deterministic replay and60/120/144Hz presentation yielding the same simulation.
A240-step GPU walk/jump replay travels1250.12 units, jumps once, lands, and ends
grounded; maximum rise137.62. This is port behavior, not original fidelity proof.
The Linux SDL window run receives injected movement/jump keys, resizes800x600,
and reports zero Vulkan validation errors on GTX1070. Headless llvmpipe also
reports zero errors. User-confirmed native Windows loading/rendering applies to
the previous build; native Windows movement validation remains outstanding.
Both self-contained packages were rebuilt. The Linux package passes the same
GTX1070 window replay; the Windows package passes240 windowed frames under isolated
Wine64 with SDL keys/jump/resize and identical movement statistics (validation
disabled there). Wine is preliminary compatibility evidence, not native Windows.
One additional inspector-window regression was not executed because automatic
approval review was unavailable; the full headless inspector regressions passed.
## Latest user-reported preview fix
The user ran the Windows build and observed a static Jimmy partially inside the
lab floor. This verifies initial Windows startup/rendering by user report, with
OS/GPU/version/input/audio details unspecified. Updated native Windows testing
remains pending.
OS/GPU/version/input/audio details unspecified. The user subsequently confirmed that the corrected build loads and renders.
Both issues were reproduced from actual assets: jimstop has two byte-identical
vertex poses, and its minimum local Y=-64.6165 plus GAM Y=26.6619 places the soles
@@ -77,17 +114,15 @@ swapchain image count mismatch. Native Windows/VM access has been requested for
reference/fidelity and native port validation. These failures do not establish
original behavior. Static reverse engineering can continue independently.
Original controller, collision resolution, introductory LABEXP cutscene, entity
activation/task/trigger execution, interactions, combat, AI, progression, menus,
mouse behavior and saves remain incomplete. Gravity/impulse integration fragments
are tested, but the player jump state machine adds extra acceleration and is not
implemented as a complete controller. Animation looping/speed are explicit preview
policies. Rendering material/lighting/fog/blend state mapping also remains incomplete.
Original collision resolution, introductory LABEXP cutscene, entity activation/
task/trigger execution, interactions, combat, AI, progression, menus, mouse aiming
and saves remain incomplete. The no-gadget controller checkpoint requires original
runtime comparison. Animation looping/speed and collider/pivot remain approximations.
Rendering material/lighting/fog/blend state mapping also remains incomplete.
Three subagents contributed independent investigation/infrastructure work and then
hit a usage limit. Primary reviewed/integrated their work, corrected texture and
visibility assumptions, finished scripts/tests/packages, and owns the current files.
Do not assume their final reports imply completed gameplay.
Two investigators contributed movement evidence/tests and collision implementation/
tests for this checkpoint. Primary integrated the runtime, input, animation, packages
and verification. Reports distinguish static recovery from runtime checks.
## Continuation