Preserve retained Jimmy update order on initial story entry
This commit is contained in:
1 parent
4cd62d3627
commit
ea04210f52
24 files changed
+1209
-22
No files matched your search
@@ -1,5 +1,16 @@
|
||||
# Core architecture coverage map
|
||||
|
||||
2026-11-06 TSK-entry correction: [menu/player lifetime](../gameplay/main-menu-player-lifetime.md)
|
||||
establishes backgroundJimmy construction and reuse before the first playable
|
||||
story scene. Input is now after Jimmy for that TSK path, while direct fresh-GAM
|
||||
order remains. This replaces the named assumption that initial story equals fresh
|
||||
registry insertion. First-neutral-tick/300-idle native Vulkan and eight managed
|
||||
Carl trajectories pass; full-suite/platform results are tracked in progress.md.
|
||||
50 more native derived-caller cases and body/transform ownership are documented.
|
||||
Original startup diagnostics now reach background allocation after a recorded
|
||||
repaint intervention, with black frames; no full-original visual/runtime parity
|
||||
or native Windows execution is claimed.
|
||||
|
||||
2026-11-06: [Carl lifecycle trace](../gameplay/jimmy-cutscene-lifecycle.md) adds
|
||||
292 bounded original-code cases and closes local contact/task/animation/STOP and
|
||||
DEFAULT-provider questions. Actual first-resumed-frame state remains unobserved.
|
||||
|
||||
Reference in new issue
Block a user