Files
EscapistsReintroduced/docs/evidence/cessna-boarding-2026-10-13/README.md
T
jakub 6a667d8deb Capture current mission, AI, map and administration development
Include the current addon, terrain integrations, tools, regression tests and recorded development evidence.
2026-10-13 22:52:53 +02:00

80 lines
4.6 KiB
Markdown
Raw 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.
# Cessna boarding repair — native check, 13 October 2026
The final isolated Everon Workbench fixture completed **19 assertions with no
script/runtime failures**. The native compiler accepted the production controller,
and all four boarding cases completed. This is not a clean whole-engine run:
22 resource, world-config and platform errors remain in
[the complete report](run-04/report.json). They are retained unchanged; the strict
native reporter consequently exits with failure.
The tested production file is
`addons/core/Scripts/Game/ERR/10_AI/ERR_PlaneFlight.c`, SHA-256
`14fa2328e1d31cf59fb89cbb53ba33224be6cfcdd2813525fa9585f8b2e237c7`.
The frozen fixture, source manifest, installed-addon hashes and stopped runner
record are retained under [run-04](run-04/runner.json). The runner confirmed both
source and external inputs unchanged and completed cleanup of its private prefix.
It used a hidden, muted Workbench (engine build 192142), a disposable profile and
the installed Cessna/PFC addons. No live server, installed addon or user profile
was modified.
## Observed cases
Times below are Prague local time on 13 October. See
[the concise native events](run-04/native-summary.log) and
[the full console log](run-04/console.log).
- **15:00:06:** both original US/West crew were in their exact assigned seats,
each AI agent active at LOD 0. The fixture had advanced the mission to its
escaped phase before preparing the aircraft.
- **15:00:28:** the aircraft completed a native ground departure from the
production runway survey's Everon position `<4788.55,28.4125,11278.9>`, heading
0. The native controller reached its airborne criteria after travelling about
476 metres; aircraft movement was not injected.
- **15:00:29, 15:00:35 and 15:00:40:** the fixture deliberately dismounted the
original pilot through the native compartment API after each real seating.
The production code made exactly three boarding attempts, at least five
seconds apart. It then reached its original 45-second preparation deadline,
withheld flight service and cleaned the failed aircraft and crew.
- **15:01:15–15:01:21:** changing the original pilot's faction during held
preparation released control before another retry. The aircraft and both crew
survived, the original input rates were restored, and `CancelSetup` preserved
the captured aircraft.
- **15:01:22–15:02:06:** killing the original pilot during held preparation
produced ordinary preparation failure and cleanup. It was not misclassified
as capture, and no replacement pilot was created.
The fixture uses a subclass only to observe native state, inject deliberate
native dismount/death/faction transitions and hold two cases before engine start.
The production crew ownership, seating, retry, timeout, cleanup, flight and
release methods execute unchanged. Its current flight is installed in the
production plane service so normal crew seat locks apply.
## Scope and failed setup retained
The original server incident was on **ChernarusMinusBeta**, while this check runs
on Everon. It confirms the repaired native boarding paths; it is not an exact
terrain/server reproduction, multiplayer takeover test, long patrol test or
performance qualification. The phase transition and fault injections are
explicit fixture inputs; no remote human connected.
[Run 03](run-03/report.json) initially copied the Chernarus departure's absolute
altitude into Everon. That point was roughly 317 metres above the local ground.
Although native West crew seating was observed, its airborne event resulted from
an airborne spawn/fall and does **not** qualify takeoff. The retry case failed when
the falling fixture aircraft was destroyed. Its raw logs and exact fixture are
preserved. Run 04 fixes only the fixture location by using the production runway
survey; the final production controller hash is the same in both runs.
The strict run-04 errors include four RHS/WCS localization GUIDs, a Cessna orphan
material metafile, unknown world configuration fields/class, Steam statistics,
and six Eden world GUID entries. No such error is removed or reclassified by this
check. Separate repository-wide validation also stops at the previously unchanged
`ERRM_AtlasLeaf.et` root-entity-ID check; focused boarding regressions are recorded
by the implementation task.
`isolated-runner.py <new-alphanumeric-suffix>` reproduces this local setup when
the installed dependencies, idle `/tmp/erri-headless-compat`, Proton and Workbench
are available. It adds the two optional addon dependencies only to a frozen test
copy and leaves the production dependency list unchanged. A new suffix is required
for every attempt; it refuses an existing game or busy test prefix.