RiftLift 0.9.2

RiftLift 0.9.2 improves legacy Oculus game compatibility, head tracking, and diagnostic capture.

Highlights:

• Routes games that explicitly request legacy -ovr or -vr_presentation behavior through RiftLift's OpenVR bridge, fixing the backend selection seen in the Stormland report without adding a title-specific routing rule.
• Refreshes OpenVR pose snapshots for explicit-timing clients that use GetPosesForFrame, fixing frozen head tracking while rendering and input continue.
• Prevents XRizer from releasing a swapchain image that was never acquired; this failure was reproduced in an isolated real Monado launch before the fix.
• Caches unavailable play-area bounds so a runtime capability failure cannot flood logs every frame.
• Gives debug launches bounded per-process XRizer logs and includes tracking progress in doctor reports.
• Preserves high-signal errors from the middle of oversized logs, deduplicates repeated failures, and removes Wine module/Vulkan trace channels that previously displaced useful evidence. Separate graphics and loader logs remain enabled.
• Pins setup to the new 0.9.2 XRizer archive, whose embedded build identity is v0.9.2 and whose checksum is verified during installation.

Qualification:

• 123 Python tests passed.
• 93 XRizer unit tests and the integration smoke test passed.
• Python/Rust formatting, compilation, Clippy with warnings denied, shell syntax, package build, installer generation, and checksum verification passed locally.
• Main and tagged GitHub CI passed, including the Windows compatibility bridge build.

Download riftlift-installer.sh for the single-file installer. It installs RiftLift and runs setup automatically. SHA256SUMS covers every published artifact.

RiftLift 0.9.1.1

RiftLift 0.9.1.1 is a hotfix for Oculus API initialization failure -3021 on systems whose host CA bundle does not already contain Meta's legacy signing root.

Fixes:

• Replaces Wine certutil installation, which can silently succeed without changing the certificate store, with a verified Wine registry-store installation.
• Refuses to create the trust marker unless Wine can query the installed certificate entry.
• Makes riftlift doctor inspect the actual Wine root store rather than trusting RiftLift's marker file.
• Adds WinTrust, cryptography, and certificate-chain channels to bounded debug logging.

Validation:

• Reproduced a missing Wine root-store entry while the old marker remained.
• Installed and queried the serialized certificate entry through Wine.
• Verified doctor's passive store detection.
• Successfully rendered Lone Echo after the repair on the same isolated prefix.
• 119 automated tests, formatting, compilation, shell checks, package build, main CI, and all release payload jobs passed.

Download riftlift-installer.sh for the single-file installer. SHA256SUMS covers every published artifact.

RiftLift 0.9.1

RiftLift 0.9.1 fixes clean-prefix runtime initialization and makes diagnostics more decisive.

Highlights:

• Repairs altered or incomplete signed Meta runtime loaders from the pinned package and installs their pinned signing root in the isolated compatibility prefix, fixing Oculus initialization failure -3021.
• Gives Proton a RiftLift-owned OpenVR path registry, so OpenVR games such as Echo VR work on fresh Monado + Envision systems without SteamVR or pre-existing OpenVR configuration.
• Expands doctor checks for signed loaders, trust state, and OpenVR configuration.
• Scans complete retained Proton logs, prioritizes original application/XR failures over noisy Wine teardown, and preserves bounded OpenVR logs without retaining logs indefinitely.
• Records and compares RiftLift, runtime, Proton, Meta package, Envision, Monado, system, and graphics versions at launch time and doctor time.

Qualification:

• Installed the exact candidate into a completely empty isolated RiftLift environment using only install.sh.
• Validated Lone Echo, Oculus First Contact, Vader Immortal Episode I, and Echo VR on one codebase against Monado; Echo VR rendered through the fresh OpenVR path.
• 118 automated tests passed, as did formatting, compilation, shell syntax, package build, main CI, and every release payload job.

Download riftlift-installer.sh for the single-file installer. SHA256SUMS covers every published artifact.

RiftLift 0.9.0.1

RiftLift 0.9.0.1 fixes the System/doctor action disrupting live Envision + Monado sessions.

Changes:

• Doctor no longer starts Envision or probes Vulkan while inspecting a live XR session.
• Envision version detection is passive and reads installed package metadata.
• Doctor records XR processes before and after inspection and reports any process that disappears.
• Envision logs, journal entries, and coredump metadata are included in correlated evidence.
• Four-component patch versions are supported by the one-file installer and release workflow.

Download riftlift-installer.sh, make it executable, and run it. SHA256SUMS covers every release artifact.

RiftLift 0.9.0

RiftLift 0.9.0 is the first stable native-runtime release.

Highlights:

• One-file installer performs installation and compatibility setup in one run.
• Native OpenXR and OpenVR launch paths validated with Oculus First Contact, Lone Echo, Echo VR, and Vader Immortal on a clean Envision + Monado environment.
• GUI Debug logging and substantially expanded riftlift doctor evidence, build identity, version comparison, retention, and cause analysis.
• Automatic Envision profile/runtime discovery without copied launch options.
• Refreshed, simplified documentation and screenshots.

Download riftlift-installer.sh, make it executable, and run it. SHA256SUMS covers every artifact.

RiftLift 0.9.0 alpha 9

Clean first-launch qualification build.

RiftLift 0.9.0 alpha 8

Qualification build for clean Monado and Envision installations.

RiftLift 0.9.0 alpha 7

Highlights

• Adds an easy GUI Debug logging mode with expanded Proton, targeted Wine XR/Steam/Vulkan, DXVK, VKD3D, Vulkan/OpenXR loader, crash, journal, kernel GPU, coredump, Steam/XR, and game-log evidence.
• Makes riftlift doctor lead with likely causes and actionable recommendations while retaining bounded, private diagnostics (approximately 120 MiB maximum; headers and failure tails preserved).
• Records the exact RiftLift, Proton, compatibility runtime, OpenVR runtime, Meta package hashes, Meta client patch, and platform bridge builds for each launch. Doctor reports current installed/expected builds and compares them with the log-producing launch, clearly flagging stale and legacy captures.
• Adds riftlift-installer.sh: one verified file that installs RiftLift, desktop integration, and all pinned runtime components. Future release workflows generate it automatically.
• Refreshes the README screenshots and installation/debugging guidance.

The native compatibility payload is unchanged from alpha 6 and retains its pinned checksum. Download riftlift-installer.sh for the simplest installation.

RiftLift 0.9.0 alpha 6

Alpha 6 makes launch troubleshooting easier from the GUI and addresses the reported interrupted-launch diagnostics. Users can now enable persistent Debug logging from the top bar; RiftLift saves detailed Proton output in bounded diagnostic storage and tells doctor whether the failing launch was captured with debug logging. Doctor now focuses on genuinely recent launches, labels missing outcomes as interrupted, filters known XRizer utility-probe noise, and gives clearer next steps. The GUI also refuses to close while an operation is active, cancelled launches record a useful error name, and OpenVR application identification is limited to the OpenVR backend. README screenshots have been refreshed for the current interface.

RiftLift 0.9.0 alpha 5

Alpha 5 makes RiftLift doctor substantially more useful and trustworthy. RiftLift now saves private, bounded per-launch logs; includes launch and optional Proton error excerpts in diagnostic reports; preserves launch start and finish times; correlates journal evidence with actual RiftLift launches instead of unrelated Steam OpenXR probes; and recommends concrete next steps. Log retention is capped at ten 4 MiB launch logs and three 8 MiB Proton logs. The native compatibility and XRizer payloads are unchanged from alpha 4 and are republished byte-for-byte for a self-contained release.