Files
Neutron/docs/gameplay/original-startup-diagnostic.md

89 lines
4.8 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Original startup: pending repaint and background Jimmy allocation
2026-11-06. This is a local Wine diagnostic, not an untouched timing or visual
reference. Originals remain unmounted in the execution namespace and unchanged.
`tools/recon/original_startup_probe.c` reuses the observer's exact-subject/live
instruction guards and runs only at the generated wrapper directory
`Z:\work\game`. It samples registry/actor state, loaded modules and owned thread
contexts. Each successful SuspendThread is paired with ResumeThread; all recorded
resumes succeed. Stack words are retained as raw candidates, not a full validated
unwind. Suspension perturbs timing. No game code or actor memory is written.
## Repaint observation and controlled test
Two initial main-thread snapshots contain the guarded OMT window-procedure return
100F1ADA and its consistent local message value0F (WM_PAINT), with internal event7.
Read-only GetUpdateRect later reports the entire1024×768 window pending. Original
DLL source100F1330 converts paint to event7 and calls100F7050; its validation of
engine-owned rectangles includes100F70BA→ValidateRect. The message pump
100F11D0..100F129C drains queued messages before returning to the periodical loop.
These bounded facts explain the diagnostic target; they do not prove all startup
time is spent in a single call or that native Windows has the same failure.
`--acknowledge-repaint` makes one ordinary Win32 ValidateRect(window,NULL) call
after the second sample. The operation is explicit in output and changes only
the OS window update region. It is an intervention, so no result is presented as
an untouched original frame/timing trace.
Matched24s tests use the same standard-resolution executable, generated prefix,
sampling tool and no synthetic keyboard input:
| Condition | Observed result |
|---|---|
|No acknowledgement|16 samples through24.35s: MAIN only, no Jimmy.|
|One acknowledgement at3.10s|Pending full-window region acknowledged. By9.18s, current game table4C444C (Level1D), Jimmy table4A373C, with MAIN still in the registry.|
The HD variant also progresses to the same allocation boundary after the recorded
acknowledgement. Both resolutions remain black with sampled gameplay-viewport
delta0 and raw ownerNULL. No usable Carl, completed New Game, completed PostLoad,
or playable-render reference is established. The source trace of
[menu/player lifetime](main-menu-player-lifetime.md) supplies the subsequent
successful-TSK retention proof; these captures establish the previously unseen
background allocation, not that complete later route.
## Subject and code identity
HDnoCD SHA2568cd5d21997835a40978b8b83e344c97c92217bf6cd6858f7458b76935d64dedb,
standard NoCD SHA2565e1d3bed2d649d16ec62ead02514119a16590380d4d5a6a73103db900a15c62e.
Their only mutual byte differences are resolution-data offsetsF655E,F655F,F6561:
standard640×480 versus HD1920×1080, both16-bit. The Xvfb desktop is1024×768.
This difference prompted the controlled standard-resolution check; switching
resolution alone is not claimed to repair rendering. Neither variant is assumed
equivalent to canonical Neutron.exe.
Standard-subject REA file-header Evidence:
`ev_62814154b8ddc13d5db3c1150082b91f0f7bf1eaccf1bca208b36671a7a1bd81`.
HDnoCD complete instruction Evidence:
`ev_23555fac476985c913a80805a12b25c26c25347c6e8210ee188471dd815c276d`.
Relevant OMT instructions come from retained DLL Evidence
`ev_af082632c98b34ccfcedef01466cafa03365e7fbf482496d01a4cda6d2f8f787`;
that saved disassembly is a prefix, not complete DLL coverage. The relevant
window/message ranges are present. Original file identity is independently
checked by the project inventory and PE mapping.
Artifacts under `artifacts/original-startup-diagnostic/` retain each probe binary,
capture identity, stdout, screenshots, module/stack/state samples and final
standard probe/dependency source. `standard/` is the acknowledged matched run;
`standard-no-ack/` is the control. All actual live anchors pass. Successful capture
requires process exit0 and `ORIGINAL_STARTUP_DIAGNOSTIC_COMPLETE`.
## Reproduction
Build against the source observer in the same tools directory. Reuse only the
existing generated game copy/prefix; never use an original directory as output.
```sh
i686-w64-mingw32-gcc -std=c11 -O2 -Wall -Wextra -Werror \
tools/recon/original_startup_probe.c -lbcrypt -o artifacts/startup-probe.exe
python3 tools/recon/reference_capture.py --asset-probe \
--probe-executable artifacts/startup-probe.exe \
--probe-model=--standard-resolution --probe-arg=--seconds=24 \
--probe-arg=--acknowledge-repaint \
--probe-success ORIGINAL_STARTUP_DIAGNOSTIC_COMPLETE --seconds 30 \
--output artifacts/jimmy-skip-original-sw
```
Omit the acknowledgement argument for the control. Keep each capture in a
separate generated directory or preserve its logs/identity before another run.