Files
Neutron/docs/gameplay/jimmy-cutscene-port-trace.md
T

5.6 KiB
Raw Blame History

Post-cutscene tilt: existing-port trace

2026-11-05. User confirms ordinary landing tilt also occurs in the original, but Jimmy must remain upright after a cutscene. The earlier camera-entry fix does not cover that resumed-idle boundary. Gameplay implementation is on hold while the full original lifecycle is investigated.

Scope and reproduction

This is port runtime evidence, not execution of original functions or a decompilation claim. Baseline is a2e89c6, with unchanged production sources. The read-only diagnostic at tools/recon/cutscene-handoff-trace/ compiles the existing Assets/Game sources into its own managed executable. It creates the same synthetic flat-floor player as DirectorTests and runs either a synthetic CAM or the actual supplied lab neutron1a MCA chain with a deterministic two-second-per-speech clock. There is no GPU, SDL, full original scene collision, or original executable execution in this diagnostic.

All48 cases complete successfully:

Input/player order Cases Retilt after300 neutral ticks
Input before player update (fresh order) 24 24, approximately ±10 degrees
Input after player update (retained order) 24 0

Each order covers both camera types, Left/Right bank, natural completion/Skip/ explicit DEFAULT, and jump/movement held or released during control lock. Each case creates eight real controlled banked-jump ticks, triggers the camera, waits until the body is grounded while control remains NULL, completes the camera, then supplies neutral input for300 ticks. Held input during the lock does not change the result because input/controller phases remain gated there.

The native camera source recovery belongs to camera orientation ownership, not this managed probe. Its original addresses are not substituted for port execution.

First stale writer

Representative actual lab MCA case: fresh order, Left bank, natural completion, released controls during the scene:

Boundary Current Euler Destination Euler Mode / turn
Before trigger (343.17676,1.3944445,357.05692) (-40,1.2,-11.666668) 1 /11.666668
After camera preparation (0,1.3944445,0) (0,1.3944445,0) 1 /11.666668
Grounded during scene and after control returns (0,1.3944445,0) (0,1.3944445,0) 1 /11.666668
First neutral input publishes (0,1.3944445,0) (0,1.3944445,-10.000001) 1 /10.000001
End of first resumed player tick (0,1.3944445,360) (0,1.3944445,-10.000001) 0 /0
End of300 neutral ticks (0,1.3944445,350.00018) (0,1.3944445,-10.000001) 0 /0

The first old-angle write is the resumed input phase, observed through the existing InputActions event after StepInput publishes its target. It is not an old current-Euler vector restored by the director. The director grants control with the player still upright and facing clean.

In LabSimulation.Step, line279 dispatches fresh input before the player update at line290. StepInput selects the air branch using the retained mode1 at lines481–507, decays the old keyboard turn, and publishes the negative turn as destination roll. Only later does the supported/released StepPlayer reset mode/turn at lines555–560. Neutral mode0 input then retains the stale destination because it has no accepted heading update (lines487–491). Consequently the independent facing phase converges to that bank indefinitely. The first resumed tick's intermediate360-degree representation is preserved in the trace; the next tick visibly rotates toward the retained target.

With retained input-after-player ordering, StepPlayer resets mode/turn before input dispatch. That input sees mode0 and retains the already upright target; the bank never returns. This is a diagnostic distinction, not evidence that all scenes should be forced into retained ordering.

Evidence files and commands

artifacts/jimmy-cutscene-return/port-trace/observations.json retains the48 full cases and selected boundary snapshots, including current/target/dirty, mode, turn, speed, support, raw owner, current camera, root, controller and physics counts. summary.json records per-order outcomes, baseline commit, source/harness SHA256 identities and the observation-file hash. run.log records successful completion. All are local generated outputs.

From GamePort:

source scripts/env.sh
dotnet run --project tools/recon/cutscene-handoff-trace/CutsceneHandoffTrace.csproj \
  -p:NuGetAudit=false -- ../Original \
  artifacts/jimmy-cutscene-return/port-trace/observations.json

No runtime, regression test, build script, original file or packaged binary is changed. Parent owns integration and any eventual implementation decision.

Implication and unresolved original questions

The confirmed port cause is a stale air turn/movement mode surviving camera preparation, then being consumed by the first fresh neutral input. An additional upright Euler write on DEFAULT alone would not explain or remove this first writer unless its timing/state ownership also changed. The correct original boundary must be established before implementing a reset or scheduling change.

Remaining questions belong to the independent original investigations: whether source control return lets the player update run before input in that same registry pass; whether camera activation/cleanup changes turn/mode through an unrecovered callback; and whether the actual trigger/registry ordering differs from the port's post-player interaction phase. This diagnostic does not answer those questions or certify that the original returns with the same retained state. Ordinary landing-idle tilt remains a separate confirmed behavior.