Skip to content

Halo CE Steam Frame VR Mod 1.4.2

Choose a tag to compare

@ClassicWasTaken ClassicWasTaken released this 07 Oct 04:06

Download Halo-Steam-Frame-Mod-Setup-1.4.2.exe below. This is the only file you need on Windows 10/11 x64; its runtime and USB tools are included.

This patch includes the tester-confirmed SD-card option and front-facing VR menus, plus the reviewed installer issue fixes.

  • SD card: click Refresh storage on Connect Frame, choose the mounted card, then Install. Install, Repair and Uninstall use the selected drive. The SD copy has its own Steam entry and fresh saves; your internal copy and saves are kept. Use an executable ext4/f2fs card with 12 GiB free. Setup stops if the selected card changes; it does not format cards or silently fall back to internal storage.
  • VR menus: opening a menu places it in front of your current headset pose. It stays steady while open and refreshes on reopening, recentering or tracking restoration.
  • Cancellation and progress: completed cancellations have a cancellation status; cleanup and remote-stop failures still require attention. Password redaction no longer interferes with phase progress (#10, #12).
  • Steam preferences: re-adding the shortcut preserves existing hidden/overlay/controller and devkit choices while retaining the VR library flag (#11).
  • Configuration and recovery: unusual TOML input is rejected clearly without replacing preferences. Interrupted legacy upgrades recover only from corroborated owned backups and hashes, preserving both save generations and custom save locations, including on the selected SD card (#13, #18).
  • SSH and USB: silent exec/SFTP handshakes are bounded and cancellable; continuous or newline-free output cannot grow the unfinished-line buffer indefinitely or starve Cancel. Automatic USB setup prefers the verified bundled ADB tools and rejects damaged bundles (#19, #20, #21).
  • Build provenance: the container image, musl archive, SDL commit, LLVM primary signing identity and bundled Paramiko source archive are pinned. The public EXE has GitHub's signed workflow/source attestation. Signed Ubuntu/LLVM 22 package maintenance updates remain enabled and logged; no hermetic or reproducible-build promise is made (#22 policy).

Existing game: close Halo, select the storage location where it is installed, and choose Repair. Verified maps are reused without another ISO. Xbox-style buttons, standing/snap defaults, tutorial fixes, render-rate aiming/flashlight, stereo sun glow and LAN/online campaign co-op are retained. The engine source remains 2ae0ee4e3e8a4dfdadfd528a5b085ca699fc9ea4, native peer protocol 17. This patch keeps the 1.4 save format; 1.3.5 checkpoints remain incompatible and retained in their original locations.

The tester confirmed the private SD/menu build worked. The new recovery, transport and trust-boundary regressions use synthetic/local fixtures; that confirmation does not establish measured FPS, every hardware recovery scenario or a complete multiplayer matrix.

Thanks to Dime (@dime-online) for the reviewed fixes in PRs 14–17 and 23–25. Their changes are integrated with the SD-card checks and additional recovery/cancellation regressions.

Supply your own authorized original Xbox Halo CE data. No retail game executable, ISO, maps, keys or soundtrack is bundled or downloaded. Halo identification artwork and licensed components retain their notices. This is a community mod, unaffiliated with Microsoft, Bungie or Valve.

SHA256: 6b9c5ef676221fc2d1746be9eec996a506e088205d7249549fcafb49862ebffa

Installer source commit: 358f47a41fcf0d16b005e2ad2b7453b48fcfcb41

Setup · Verify release provenance and read the trust/update policy · Source and credits

To authenticate the download using a trusted GitHub CLI, run:

gh attestation verify Halo-Steam-Frame-Mod-Setup-1.4.2.exe --repo ClassicWasTaken/HaloSteamFrameMod --signer-workflow ClassicWasTaken/HaloSteamFrameMod/.github/workflows/build.yml --source-ref refs/heads/main --source-digest 358f47a41fcf0d16b005e2ad2b7453b48fcfcb41 --deny-self-hosted-runners

The EXE has no Windows Authenticode certificate. Build provenance verifies its authorized repository/workflow origin, not a defense against compromise of that identity or your local user account. Retained SSH host fingerprints still protect the Frame's endpoint identity; verify first-use fingerprints instead of accepting an unexpected key.

GitHub verification passed: Linux and Windows tests, rootless-container checks, the full native ARM64 OpenXR compile/link, and the Windows EXE build/smoke test. The downloaded EXE also passed fresh repository/workflow/source-commit attestation verification.