User confirmed Fluffy was updated and approved using5.7.4. Published HydraUnrealEngine v1.3.1 (source daf40bf) to accept5.7.3 or5.7.4 with v26 clang20.1.8; other engine versions remain rejected. CI35093251402 passed tests/vet, race tests, Windows compilation and publication. Released executable downloaded/hash-verified on Fluffy: SHA256 96b07f5c05636d5e55addd13bd9bd92e0c3a385fb5abb73500faa7c68bf6e018.
PASS: released HydraUnrealEngine v1.3.1, UE 5.7.4, Development,
with the platform flag omitted (default Both). Template source is committed
0b660515d3c914828e616864634718693a12b332. The isolated job on Fluffy ran from
12:11:52 to 12:17:39 UTC, about 5m47s, with existing engine/shader caches.
Editor/game compilation, Windows and native Linux cooks, packaging and both
uploads succeeded, exit0. No --no-compile or --skip-preflight bypass was used.
| Target | ZIP bytes | Public artifact |
|---|---|---|
| Win64 | 328801705 | Download |
| Linux | 373176680 | Download |
Win64 ZIP SHA256: 8bf61c0c49892ccb74c6645ef7b52cfa386ed727f591efd9c4892dfc8b527770.
Linux ZIP SHA256: e8072c2221f0087edf486ae1a7e3fdb841da8454622b668eb04eda9a616a10dd.
Both complete public downloads were verified independently on pi004 and match
their checksums. The Windows game is an
x86-64 PE executable; Linux is native x86-64 ELF. Executable hashes match the
build host. ZIP entries are relative and target-specific. Linux run.sh and the
native game retain executable permissions; the launcher hash matches the
checkout. Its deployment manifest reports UE5.7.4/native/linux-amd64/flat and
xr_verified=false, with all 15 project/Source/Config hashes matching committed
source. All 16 staged source files, including the launcher, were unchanged
before and after both builds.
The first attempt built/uploaded both targets but exposed a source-integrity
problem: Epic's default-enabled AndroidFileServer editor module generated
settings and rewrote DefaultEngine.ini during cooking. Verified this behavior
in the installed plugin source, disabled that unused plugin explicitly in the
template, committed/pushed 0b66051, then repeated the full workflow from a
fresh source copy. The artifacts above are from the corrected run; earlier
trial uploads are superseded. The packaging tool still labels manifest hashes
as captured after cooking; this validation additionally compared them with the
committed input independently.
Evidence on Fluffy:
C:\Builds\HydraUnrealToolValidation\20260916-dual-clean
(result.json, package.log, source manifest, verified-artifacts.json and both
output archives). Both completed validation scheduled tasks were removed;
evidence and builds remain. Local ignored evidence is under the template's
Saved/Validation/20260916-dual/; orchestration/download records are in
/tmp/hydragon-dual-20260916/clean/. The independent verifier and its downloaded
archives are retained on pi004 under /tmp/hydra-dual-check-20260916/.
This proves the default two-target packaging and delivery workflow on the
approved UE5.7.4 host. It does not install/promote these builds or validate
their flat/headset rendering. The previously deployed MSI1060 baseline is UE5.7.3 build2; this validation did
not replace it. User sessions, runtime configuration and Perforce were unchanged.
WiVRn #741 and the original Blueprint-only/OpenXR case #636 remain separate.
HydraMancer v0.3.3 is deployed at https://hydramancer.experiencenet.com/experience . CI35093398451 passed binary and amd64/arm64 OCI jobs; reviewed HydraSkin dry run and applied update on pi004 in12s. Runtime/image matchv0.3.3; recorded image digest equals registry index sha256:ae91167d4c909061d549c201f3c1cac79197ef9b7cd6c01365ffa0fafe440e34 . State/proxy preserved; auto-update off. Public/mesh health and default plus legacy platform routes passed default-Both and approved5.7.3/5.7.4 checks; mobile page inspected.
Final source/docs are committed and pushed:
The independent archive verification ran on pi004 after the local workspace ran out of disk; both whole public downloads, binary hashes/formats and Linux metadata/permissions passed, verifier exit0. Removed its completed transient unit. Both Fluffy validation tasks were removed; evidence retained. No venue artifact promotion, engine installation, user-session interruption or headset-runtime change was performed. #636 and #741 remain open.
Original acceptance scope follows.
User requested real dual-platform validation on 2026-09-16 and confirmed Fluffy was updated: UE5.7.4 is approved. Verify published tool from clean committed HydraUnrealTemplate source in an isolated folder, default Both, Development and delivery. Require successful editor/game builds, Windows and native Linux cooks, separate uploaded artifacts, downloaded SHA256 checks, native ELF/Windows PE and launch/manifest/source-hash/package-permission checks. Preserve venue installations and user sessions; runtime/headset acceptance is separate (#741). Add narrowly scoped5.7.4 support while retaining5.7.3 and rejecting other versions. Record evidence and limitations in issue/runbooks; publish any necessary tool/guide corrections and commit/push docs.