Eve library

V2 rollback native characterization host

Other

Revision 1

On this page

This is verification setup for the Presentation Center's immutable source pin, not a new V2 product target. It supplies twenty-five Unreal automation cases for prediction, correction/recovery, codec/parity records, handshake/fallback policy, snapshot/history boundaries and presentation interpolation/event records. Their expected outcomes come from source review. Compiling their translation unit does not execute their assertions.

The original attempt is in the native-probe receipt. The unchanged source failed UnrealHeaderTool. A separately labeled diagnostic fixture passed header generation, but dependency compilation failed. The later Linux diagnostic receipt records a further-adapted non-unity module build and execution of all five cases: five passed, zero test errors/warnings, process exit zero. That qualified result does not make the unchanged baseline pass.

The expanded-case receipt records all nineteen cases passing together, with zero test errors/warnings and observed exit zero. Only the host test source changes in that increment; all 319 copied source files and the twelve fixture substitutions remain identical. Its two-action incremental build reuses the previously bound dependency modules.

The connection-quality draft receipt adds QualityValidatorBoundaries: config versus policy alignment, returned decisions versus accepted-state validation, and diagnostic flags versus stamp validation. All twenty cases pass together without another fixture adaptation.

The rollback-session integration receipt adds ConfirmationLifecycle, PackedPlayerKeyBoundary, EarliestCorrectionAndLiveHash, DuplicateConfirmationOrdering and FrozenConfirmationRetryAndReset. All 25 cases pass together with zero test errors/warnings and observed process exit zero. Only the test module is rebuilt; all six dependency modules and three metadata files remain byte-identical. Seven missing engine feature-pack preview images still produce startup errors; these are retained separately from the successful test entries.

Prepare and verify inputs#

From the repository root, use a new or empty output directory outside tracked content. The tool reads Git objects at 1ceae52c7896a59ac74a4429d410f3218f0b91c6, not current product files. It copies 319 regular files from V2Core, V2Input, V2Gameplay, V2Combat, V2Netcode and the V2AdaptiveAI plugin. It preserves file bytes/modes and adds only the four host templates. No full-game target, content assets, pre-build generation commands, network server or provider is launched by preparation.

sh
python tools/presentations/prepare-v2-rollback-probe.py --output /tmp/my-new-v2-probe
python tools/presentations/prepare-v2-rollback-probe.py --output /tmp/my-new-v2-probe --check

Preparation refuses nonempty destinations, symlink paths, unsupported Git entries and template/source collisions. --check recomputes expected inputs from Git and templates; it rejects changed bytes, modes, missing inputs, added Source files and edited manifests. Build products outside Source trees are allowed, but are not verified binaries. Keep compiler/runtime receipts separate from source-manifest.json; the latter records preparation with compiled: false and testsExecuted: false and is never promoted to a result.

For the explicit diagnostic variant, use another fresh directory and pass --mode diagnostic-blueprint-metadata to both commands. This removes BlueprintReadWrite only from the FrameInputHash and FinalInputHash annotations in V2NetcodeTypes.h. Exact-match guards and before/after records bind the adaptation. The uint32 fields and all C++ function bodies remain unchanged. This changes reflected Blueprint visibility: it is not a repair of the immutable baseline or evidence of Blueprint compatibility.

--mode diagnostic-linux-compile is a further, explicitly adapted fixture. It retains those two metadata changes and applies ten exact dependency-expression changes in V2Input and V2Gameplay. The preparation manifest records every original line, before/after expression and reason. All rollback mechanism bytes remain pinned; the diagnostic build is still not an unchanged-pin build.

The seven V2Input edits select the declared size type for FMath::Min, use the engine's indexed touch keys, reference the actual dodge-mode parameter and pass the string view expected by a synchronous copying helper. The three Gameplay edits match TArray::Sort's dereferencing predicate contract for a locally nonnull edge array, supply the enclosing simulation loop's hour, and use the declared weather-rule struct type. They are verification-fixture adaptations, not product repairs or runtime acceptance of those unrelated Gameplay features. Exact-match guards reject missing or duplicated source expressions.

Build admission and evidence limits#

Follow repository resource preflight and process-group supervision before any Unreal command. Use the local Unreal 5.5 installation as ueagent when root is rejected, and make only the owned temporary project accessible to that user. Do not change global engine/user settings or kill another session's processes.

First export the action plan with Build.sh PresentationRollbackEditor Linux Development <absolute-project.uproject> -UsePrecompiled -MaxParallelActions=1 -NoUBA -NoUBALocal -NoXGE -WriteOutdatedActions=<absolute-actions.json>. Header generation still runs before action export and may fail. Review all action outputs and dependencies before permitting compilation; the recorded diagnostic plan had 95 project-local actions, not an engine rebuild.

Do not assume -NoUBA disables its separately configured local executor: Unreal 5.5 exposes -NoUBALocal too. The recorded compiler attempt omitted the latter and used UBA locally, still with one action at a time. It also supplied -StopAfterErrors, which is not the inspected parallel executor's fail-fast configuration. The supervisor was explicitly terminated after compiler errors; exit 143 is a stopped attempt, not the build tool's natural failure result. Future runs must use supported executor configuration and supervise errors as well as memory/disk. Do not automatically launch a full build from this recipe while the documented dependency errors remain unresolved.

The Linux diagnostic route also needs the supported -DisableUnity argument on both action discovery and compilation. The inspected UE 5.5 TargetDescriptor declares that switch explicitly. It separates translation units whose file-local helper names collide when combined; it does not rename those helpers or omit their source files. The exported non-unity action plan contains 321 actions (313 compile, seven link, one metadata), all project-local. Use -UsePrecompiled, both UBA-disable switches and one action at a time as above. Recheck the actual plan and resources on every host; these counts do not authorize an engine rebuild or establish a successful module build.

After a successful, source-bound module build, the runtime suite name is Presentation.V2.Rollback. The recorded UnrealEditor-Cmd invocation uses the actual built project, -unattended -nop4 -NullRHI -nosplash, -DisablePlugins=FastBuildController, "-ExecCmds=Automation RunTests Presentation.V2.Rollback;Quit", "-TestExit=Automation Test Queue Empty", and new absolute -ReportExportPath=<report-directory> / -abslog=<runtime-log> destinations. Require all twenty named cases to be discovered and executed successfully, an observed terminal process result, exact binary/input hashes and complete logs. A missing report, zero discovered tests, a compiled object or matching source manifest cannot substitute for this runtime gate.

The passing run characterizes this isolated host and its declared adaptations. It does not prove the complete V2 target's strict-FP settings, cross-platform determinism, authored assets, socket delivery, DTLS, FEC recovery, match settlement or release acceptance. Bounded malformed-input cases deliberately do not exercise unbounded allocation. Invalid-configuration experiments are labeled as such; they do not establish production reachability. Continue the remaining snapshot sub-state, packed-key, channel and actual integration review identified in the learning map. Presentation records are not proof of rendered UI or sound.