Evidence and history - volcmen/forza-motorsport-linux GitHub Wiki
Home · Play and verify · How it works
Use this page to check what a claim means and find the record behind it. The installation instructions live in Install; archived plans are historical material, not steps to execute.
What was tested
| Release or experiment | Evidence | What it establishes |
|---|---|---|
| Physical Arch desktop, legacy-v0.1, 2026-10-17 | Native Steam launches and Hakone benchmark | Existing custom GE-Proton11-3-FM on RTX 4080 SUPER: two launches, profile/menu loading, valid 3440×1440 benchmark with 60 FPS achieved and zero stutters, and clean exits. Current source diagnostics and a separate launcher lifecycle check passed. The complete preview-2 composed runtime was not installed or tested on this host. |
| v0.3.0-preview.2 maintenance qualification | Local installation, recovery and runtime checks | Fresh tool/user installation using an existing real Steam prefix, rollback after game remount, correct disk-space refusal and retry, 26 runtime API and 18 storage checks. The real game loaded its profile and event, then stalled before completing a lap. Physical Deck and native Windows/controller identity remain unverified. |
| SteamOS Venus presentation and Free Play, 2026-10-16 | Controlled graphics comparison and real game results | Disabling both generations of present-id/wait extensions completed the scratch D3D12 probe lifecycle and enabled repeat menu/profile loading. A short Brands Hatch Free Play drive with keyboard input and normal exit passed. Hakone benchmark loading remained unresolved; no completed race, measured performance, or physical Deck result. |
| SteamOS real-account test, 2026-10-15 | Account persistence, official game verification, and earlier launch failures | Microsoft sign-in and wallet persistence across reboot passed; Steam verified the isolated game copy. Earlier launches stalled before the menu. Later presentation results are recorded separately above. |
| v0.3.0-preview.1 composed preview | Build/source identities and installed SteamOS qualification | Prepare/Finish/Doctor/rollback passed in a disposable VM, with synthetic game/private-DLL fixtures; 26 API and 18 storage checks passed through the installed launcher. Login page and overlay rendered. No real account/game handoff or physical Deck result. |
| Historical maintainer custom setup | Original v0.2 wording and fresh-install findings | The existing custom FM setup worked on one desktop. The old statement does not establish that fresh bootstrap from the stock GE download works. |
| SteamOS 3.8.14 investigation, 2026-10-15 | Installed QEMU guest and dependency checks | Read-only diagnostics and 15 behavior tests passed; released GUI applications have missing libraries. No Steam Deck gameplay or completed installation claim. |
| Initial custom Proton candidate, 2026-10-15 | Source, SDK, artifact, and regression record | Full build completed; 26 API checks passed in the SDK container and installed SteamOS guest. Later preview qualification is recorded separately above; gameplay remains unverified. |
| v0.2.0 bundle | Build and download record | Reproducible compilation, public download verification, and the checks detailed in that record. Its pending-gameplay wording predates the later maintainer confirmation. |
| v0.1 / legacy-v0.1 | Live validation, 2026-09-02 | Two launches without reboot, online profile/content, controller navigation/driving/hotplug, AP702 absence, explicit Xbox Invite/Join with Windows, keyboard/controller picker input, and clean shutdown on one system. |
| Newer WineGDK/Xodus experiment | Historical verification | Rejected live despite successful hermetic source tests. Not an installation alternative. |
| Incoming invite notifications | Recorded limitation | Not supported. Explicit Invite/Join is a separate capability. |
No row guarantees compatibility on another machine or after an upstream update. The v0.1 matrix must not be relabeled as a v0.2 result. Your installation still needs its own game-session check.
Runtime versions
The experimental preview uses composed-preview-v1, with Wine
3ecd0e8a9b8e7e0a754b09595d1aa70c9b1e1301
and Xodus
850ec9477e00117960ca09ad38c6154acc56c16d.
This retains the legacy protocol generation, adds the async correction and
dependency/security changes, and limits runtime installation to user files.
The complete-tool manifest
and user-bundle manifest
bind its exact artifacts. It does not select the rejected newer protocol experiment.
The older v0.2 bootstrap remains on legacy-v0.1, with these historical inputs:
| Component | Reviewed source revision |
|---|---|
| Legacy Xodus | 7b236772297b3475ea4f3cb830feb5b224f3064a |
| Legacy XGameRuntime | a1548b1cf57371715d10b608bc81a77a188e40d4 |
| Wine controller change | ddd302d97c6008d79ea4f3e3ad56014cb548e514 |
| Wine storage change | a7719bd8d0719e5ea6061387db020fa6a6b39d27 |
REJECTED LIVE: WineGDK d96a768e25f632b04a457e4cb9f585e89ef5d095 with
Xodus ee9db0f68122a9731b9b66cc24767693d1737f5c. The observed combinations
produced protocol rejection, flicker, or exit after the logo. Do not install this
pair as an alternative. This verdict applies to those exact revisions.
Machine-readable authorities stay with the code:
- Bootstrap trust manifest: release download, bundle checksum, builder and source identities.
- Runtime profiles: installer profile constraints.
- Supported builds: accepted originals and exact patch bytes/hashes.
- v0.1 publication manifest: v0.1 source and live-claim evidence; not a v0.2 acceptance record.
Build and source records
These records retain their original dates and verdicts. A baseline or source-test result is not a current installation recommendation.
| Record | Scope |
|---|---|
| v0.1 Xodus | Legacy source/build evidence |
| v0.1 XGameRuntime | Legacy out-of-tree build evidence |
| v0.1 live validation | Exact installed artifacts and dated observations |
| Bootstrap build | v0.2 reproducibility and download evidence |
| Wine baseline | Historical source-test baseline |
| Xodus baseline | Historical Xodus source-test baseline |
| XGameRuntime baseline | Historical newer-runtime hermetic tests |
Verify repository changes
From a development checkout with the development tools installed:
uv sync --locked --group dev
just verify
The gate runs Python and shell behavior tests, unit syntax verification, ShellCheck, shfmt, Ruff, REUSE licensing, publication/privacy policy, and whitespace checks. Use shfmt 3.14.0, matching CI's checksum-verified release. See the checked-in gate and CI setup for its host-tool requirements. These tests use synthetic or temporary roots; they do not prove gameplay, account sign-in, networking, or invite delivery.
Repository checks cover publication evidence and the README’s wiki entry point.
When editing wiki pages, also check the rendered links, section anchors, and
release boundaries above. Edit guidance using GitHub’s Edit button on the relevant wiki page, or clone
https://github.com/volcmen/forza-motorsport-linux.wiki.git and push changes to
its default branch. Keep manifests and raw
evidence authoritative for exact identities. Do not rewrite old observations as
new validation results.
Security and maintenance
The community feedback review, 2026-10-17 records the live Reddit replies, GitHub reports, upstream threading comparison, preview-aware diagnostics, game-filesystem space correction, and formatter fix.
Read the maintenance and security review, 2026-10-15 for the contributor review, dependency CVEs, CodeQL changes, validation, and scope. The security audit, 2026-09-05 retains its original findings and evidence. The original repository/Python audit is supplemented by the preview Xodus dependency review. The RSA timing advisory remains in the graph, with private signing moved to OpenSSL; a compile-time maintenance advisory also remains. GLib has a tested source backport. These scoped reviews do not certify every Proton, OS, or Microsoft binary as vulnerability-free.
Changes to main require a pull request and passing verify and CodeQL checks.
Versioned release tags are protected against rewriting and deletion. Dependabot
proposes dependency updates for review; secret scanning and push protection are enabled.
For a suspected vulnerability, follow the security policy and report it privately. For ordinary fixes and improvements, see Contributing.
Releases and archive
The documentation before this wiki is preserved at commit
bf12d7e7f22c8ebb910f68162af1caf0e00b0a5c. These links are pinned to that
snapshot, so moving the current documentation does not erase the record.
| Record | How to read it |
|---|---|
| v0.2.0 release · original local notes | Bootstrap release and its historical pre-gameplay wording |
| v0.1.0 release · release evidence | Source-only release with the dated accepted matrix |
| Verification ledger | Historical counts, source gates, and exact-build claims |
| Upstream publication ledger | Recorded public branches, issue comments, and draft PR URLs |
| Upstream draft texts | Historical text prepared for those publications |
| Plans · designs | Original proposals, superseded work, and design history; not current instructions |
| Detailed architecture | Original transaction/protocol design; its older live-status wording is superseded by the table above |
| Original documentation tree | Full pre-wiki archive, including old setup and troubleshooting pages |
The archive retains all original files and identities. The seven local evidence
records were moved from docs/evidence; only the Wine baseline's navigation link
was updated. Old immutable URLs continue to refer to the original paths.