From 2c4581f1228f66cced69d3cf7b0f267fe0776eb4 Mon Sep 17 00:00:00 2001 From: SAPHID Date: Mon, 26 Oct 2026 00:31:56 +0000 Subject: [PATCH] Record v0.4.37 real Frame release smoke --- docs/current-support-matrix.md | 2 +- .../v0437-release-smoke-2026-10-26.md | 24 +++++++++++++++++++ 2 files changed, 25 insertions(+), 1 deletion(-) create mode 100644 docs/evidence/v0437-release-smoke-2026-10-26.md diff --git a/docs/current-support-matrix.md b/docs/current-support-matrix.md index cfb54c3..71e10b9 100644 --- a/docs/current-support-matrix.md +++ b/docs/current-support-matrix.md @@ -4,7 +4,7 @@ Current for Frame Control **v0.4.37**, 26 October 2026. “Real Frame + physical | Feature | Real Frame + physical PC tested | VM only | Untested or limited | Last check and proof | |---|---|---|---|---| -| Core title smoke test | Linux lxso2 installed, launched and removed reserved native/Proton titles on the real Frame; all 13 steps passed | No | Unworn headset; visible rendering and controller input not checked. Other feature paths retain their separate limits below | 25 Oct, v0.4.36 tag `1701e62`, Frame OS 0.5.6 build `20261022.6153909`: [release smoke evidence](evidence/v0436-release-smoke-2026-10-25.md); [earlier detailed results](evidence/round2-smoke-2026-10-25.json) | +| Core title smoke test | Linux lxso2 installed and removed reserved native/Proton titles on the real Frame; all 13 steps passed. ARM64 and Windows titles launched | No | The x86_64 title could not launch because Steam Linux Runtime 4.0 was not installed. The headset was unworn; visible rendering and controller input were not checked. Other feature paths retain their separate limits below | 26 Oct, v0.4.37 tag `5239dae`, Frame OS 0.5.6 build `20261022.6153909`: [release smoke evidence](evidence/v0437-release-smoke-2026-10-26.md); [earlier detailed results](evidence/round2-smoke-2026-10-25.json) | | Windows desktop in the headset | No physical Windows PC test | Windows 11 VM sent a whole desktop to a real Frame; this used an intermediate fix, not the final native DLL | Physical GPU, capture and controller input; individual windows unavailable in bundled DXGI build | 24 Oct, v0.4.10 installer + candidate fix: [VM log](evidence/windows-vm-2026-10-24.md), [PC guide](pc-in-headset.md) | | Linux desktop in the headset | No | No | Native Linux PC capture is disabled; lxso2 lacked a desktop portal and PipeWire session. The separate Steam `-pipewire` helper is not Frame Control's PC capture | 24 Oct, v0.4.17: [host audit](evidence/linux-pc-host-lxso2-2026-10-24.md), [Steam helper PR #163](https://github.com/saphid/frame-control/pull/163) | | Mac desktop in the headset | A physical Mac sent its screen/window to a real Frame | No | Current v0.4.26 Mac installer and worn-headset controller input have not been repeated | 28 Sep, pre-v0.4 / Frame OS 0.4.1: [Mac guide and measurement](streaming.md#b-show-the-macs-desktop-inside-the-frame) | diff --git a/docs/evidence/v0437-release-smoke-2026-10-26.md b/docs/evidence/v0437-release-smoke-2026-10-26.md new file mode 100644 index 0000000..92785be --- /dev/null +++ b/docs/evidence/v0437-release-smoke-2026-10-26.md @@ -0,0 +1,24 @@ +# v0.4.37 release smoke on a real Frame + +On 26 October 2026 at 00:27 UTC, a physical Linux host ran the release +`scripts/frame-smoke.sh` against a real Steam Frame. The smoke scripts were +byte-identical to tag `v0.4.37` (`5239dae1a82c35635ef89f59eac9721c5014e2ed`). +The headset reported Frame OS 0.5.6, build `20261022.6153909`. + +The test acquired `/tmp/frame-test.lock` with a unique owner marker before +reading the headset. SteamVR activity stayed at 3 (standby); initial proximity +raw was 6.3125 and battery was 99%. The test released only its own lock after +cleanup. Battery read 100% afterward. + +All **13 of 13** smoke steps passed. ARM64 and Windows test titles installed, +launched, and were removed. The x86_64 title installed and was removed; its +launch reported that Steam Linux Runtime 4.0 was found but not installed, so +this result does **not** establish x86_64 game execution. Devkit properties and +status reads passed. No key was paired. The final cleanup removed the reserved +test titles and processes. The private result remains under +`/tmp/frame-v0437-smoke-results/`; this summary omits headset identifiers and +device status details. + +Because the headset was in standby, this test did not verify wearer-visible +pixels, physical controller input, a Framey panel, or official Decky plugin +settings in VR. Those checks remain on the [worn checklist](../framey-vr-check.md).