Add hook debug tooling and refine RT3 atlas
This commit is contained in:
parent
860d1aed90
commit
57bf0666e0
38 changed files with 14437 additions and 873 deletions
|
|
@ -129,12 +129,11 @@ What this note is for:
|
|||
- Track-lay and station-placement semantics
|
||||
- Train detail and trainbuy command ownership
|
||||
|
||||
Highest-value open edge:
|
||||
Current bounded conclusion:
|
||||
|
||||
- Whether any later gameplay-owned mode introduces a distinct input or frame owner for ordinary
|
||||
world interaction, or whether the grounded `shell_controller_window_message_dispatch` plus
|
||||
- Current evidence points to one stable reading: no later gameplay-owned mode introduces a distinct
|
||||
outer input or frame owner for ordinary world interaction. The grounded
|
||||
`shell_controller_window_message_dispatch` plus
|
||||
`simulation_frame_accumulate_and_step_world` path remains the sole coordinator after world
|
||||
entry and the first grounded non-camera world-input coordinator. Current evidence now points
|
||||
strongly to the second reading: the shell-fed input and frame path remains the only grounded
|
||||
coordinator after world entry, and no separate outer gameplay loop or gameplay-only input object
|
||||
is grounded in the local corpus.
|
||||
entry and the first grounded non-camera world-input coordinator, and no separate outer
|
||||
gameplay loop or gameplay-only input object is grounded in the local corpus.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue