Preserve retained Jimmy update order on initial story entry

This commit is contained in:
UnixNight committed 2026-11-06 17:08:59 -05:00
1 parent 4cd62d3627
commit ea04210f52
24 files changed
+1209 -22

No files matched your search

+14 -12
View File
@@ -38,22 +38,24 @@ other agents' active changes. Keep updates concise, save detailed evidence to di
Use bounded endian-aware parsers, portable paths, clear C#, deterministic tests,
and explicit unmanaged ownership. Build frequently. Update `docs/progress.md`,
`docs/tasks.md`, `docs/decisions.md`, and compatibility evidence before transitions.
Current direction (2026-11-05): user requests decompilation before further
implementation. Keep runtime/package baseline a2e89c6/dae13ac unchanged while
recovering Carl's skip-to-idle lifecycle; current entry reset does not close the
post-skip tilt bug. Trace original state ownership/update order before another
movement reset or scheduler change. See docs/gameplay/jimmy-cutscene-decompilation.md.
Current direction: preserve exact original movement; keep gameplay expansion
paused. The menu/background→successful TSK-load lifetime now establishes retained
Jimmy-before-level-input order on first story entry. Correct that initialization
classification, preserving fresh direct-scene order and all movement/rotation
algorithms. See docs/gameplay/main-menu-player-lifetime.md. The strengthened
Vulkan Carl fixture reproduces the old first-neutral-tick bank and passes after
the correction; broader/native Windows comparison remains separate.
The broader priority remains Jimmy movement stabilization, with gadgets paused. Preserve current movement as baseline; do not substitute
JN-Engine native/Godot movement. Use its original decompiler index only as leads,
verified with REA/authoritative originals. See docs/gameplay/jimmy-movement-stabilization.md.
2026-11-06 continuation: docs/gameplay/jimmy-cutscene-lifecycle.md records292
new bounded original-code cases, mapped DEFAULT recovery and a read-only copied-
original launch/attach observer. No source-supported reset is established; actual
original Carl entry/return state remains the implementation gate. Wine32 observer
attach works but only MAIN/no Jimmy/black frames were observed locally. Preserve
runtime a2e89c6/packages dae13ac and normal landing bank. The user reiterates exact
original behavior; do not substitute a leveling reset or global scheduling change.
2026-11-06 continuation: the earlier292 original component cases plus50 derived-
caller cases and body/visual-sync audit supply no extra reset. Startup diagnostics
now observe backgroundLevel1D/Jimmy allocation after an explicit OS repaint
acknowledgement, with black frames/timing perturbation recorded. Source lifetime,
not those frames, proves the TSK ordering correction. Preserve normal landing
bank; never substitute a leveling reset. Historical runtime/package baseline is
a2e89c6/dae13ac. Read the current progress/compatibility results before packaging.
The prior collision work is resumed where needed for movement; preserve the
35a2a66/0272f7b checkpoints and their source gates before broader body admission.
Controller checkpoint integrates108 native ground/air/facing/jump comparisons;