saphid--frame-control/docs/current-support-matrix.md

What we have tested

Current for Frame Control v0.4.34, 25 October 2026. “Real Frame + physical PC” means an actual headset and a non-virtual computer. “VM only” means a Windows virtual machine, sometimes connected to the real Frame. A CI test or a simulated device is not a physical hardware test. The date/version column is the last relevant check, not a promise that every new release was retested on that platform. See each link for the exact procedure and limits.

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.31 candidate source 1255ef2, Frame OS 0.5.6 build 20261022.6153909: sanitized results
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, PC guide
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, Steam helper PR #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
OBS headset source on Linux	Real Frame to OBS 30.0.2 on a Linux host: 187.367 s, 720p30 H.264/AAC stereo, 5,621 frames, no encoder skips; room passthrough appeared in the recording	No	Synthetic tone was measured, not real game audio or audible listening. Default audio led by about 0.43 s in this setup; a measured +480 ms OBS offset removed residual skew at test resolution. Source-image latency was 1.431 s in one trial; other hosts and long sessions are unverified	25 Oct, v0.4.30 package plus PR #219 runtime: validation
OBS headset source on Windows	No physical Windows PC test	Windows 11 VM helper fixture passed, but a native bridge to the real Frame sent no packets	In-app OBS controls remain hidden; native Windows OBS and firewall path are unverified	25 Oct, PR #219: validation, OBS guide
OBS headset source on macOS	No	No	Helper and OBS Media Source not tested on a Mac with a Frame	25 Oct, v0.4.22: OBS PR #174, OBS guide
OBS headset source on a SteamOS / Steam Machine PC	No SteamOS PC or Flatpak OBS runtime test	No SteamOS host VM test	v0.4.27 AppImage launched on Ubuntu x86_64 under Xvfb; the helper sent H.264/AAC from a real Frame to a local UDP receiver. SteamOS read-only root, desktop UI and Flatpak OBS remain unverified	25 Oct, v0.4.27: host test, OBS guide
Wired connection doctor	No physical PC/Frame cable test of the doctor	No	Synthetic route/SSH tests; a separate Mac USB-C address observation does not test the doctor or game stream	25 Oct, v0.4.23: PR #178, wired guide
Windows Wireless Adapter doctor	No physical Steam Wireless Adapter/dropout test	Windows 11 VM ran read-only checks without the adapter or WLAN	Adapter identification, dropouts and recovery on hardware	24–25 Oct, v0.4.20–0.4.25: VM log, doctor guide, comparison PR #184
Linux Wireless Adapter doctor	No Steam Wireless Adapter hardware test	No	Read-only Linux host checks and mocked adapter states; no adapter-specific hardware observation	24 Oct, v0.4.20: PR #165, doctor guide
Switch PC windows	No physical Windows PC test	No real VM-to-Frame Alt+Tab check recorded	Explicit chord is covered by tests; actual window focus, keyboard layouts and controller interaction are unverified	25 Oct, v0.4.24: PR #181, PC guide
Keyboard and trackpad from Frame Control	A Linux PC sent a click and ASCII keys to a temporary focused window on the real Frame	No	Worn-headset interaction, Unicode delivery and pixel-accurate pointing	24 Oct, v0.4.19: received-event log, PR #66
Backup and restore after reset	Same-headset backup, no-op save restore and Return to Game Mode checks	No	Restore after a factory reset, replacement restore and Android data restore have not been tested on a headset. No headset reset was done	24 Oct, v0.4.17: backup guide, Return to Game Mode log
Android game backup import	F-Droid Basic APK with synthetic main and patch OBBs installed, transferred and read back on a real Frame	No	v0.4.30 restricted split-APK backup route has generated-fixture and existing merger tests only; no real split game or RE4 gameplay test	20 Oct OBB headset check; 25 Oct, v0.4.30 split fixtures: OBB device evidence, split PR #206, guide
Passthrough in recordings	Real room pixels in OBS and a production MP4 after safe SteamVR wake	No	Yes for the checked 0.5.6 mirror. Raw cameras are not opened. Other games/modes and Steam clips may differ	25 Oct: validation, recording guide
Open at login	No Frame needed; Linux autostart file toggled on a physical Linux host with an isolated config directory	No	A full login session and physical Windows/macOS host login have not been checked; OS API calls were unit tested	25 Oct, v0.4.26: PR #189
Local Frame Control extensions	Example panel displayed live Frame status in a browser preview; the real Frame served a read-only example in the experimental headset panel	No	No wearer-visible extension view; third-party extensions and physical Windows/macOS extension folders untested	25 Oct, v0.4.29: PR #194, PR #201, extension guide
Experimental Frame Control SteamVR panel	Real Frame OS 0.5.6 installed its user service, registered an overlay, served authenticated live status and a read-only extension, saved a screenshot and short MP4, and removed owned resources	No	Headset was unworn in standby: overlay reported not_visible, stereo capture was dark; wearer-visible pixels and controller input are unverified. The new large read-only status screen has browser layout and packaging checks only	25 Oct, v0.4.29 device check and v0.4.31 status screen: PR #198, PR #201, PR #220, panel guide
Experimental Decky Loader manager	Real Frame OS 0.5.6 ARM64 user-service install, status, update and remove completed; seven official-store plugin backends loaded, and ProtonDB Badges completed managed store install/update/remove	No	v0.4.33 shared transaction lock and stopped-loader plugin removal have Linux and CI tests, but no live recovery test on the Frame. Plugin pages, settings, routes, toasts and controller input in VR remain unverified; some plugins need root, x86_64 binaries or Deck-specific hardware	25 Oct, v0.4.31 hardware and v0.4.33 tests: PR #208, PR #230, PR #234, compatibility table
Experimental Framey VR plugin panels and store	No live real-Frame panel test	No	ProtonDB Badges settings rendered and sent a setting call in local Chromium. Fake Frame tests cover setting read/write through update and reinstall and install/remove two pinned official API v2 archives. Page tests cover the official JSX runtime, disabled controls, text fields, sliders, grouped dropdowns and an author sample bundle. The sample is not published in the store. The 11-archive manifest audit found only ProtonDB Badges API v2 in that set; a hash match and fake Frame install do not prove VR use. Wearer-visible pixels, controller input and live settings persistence remain unverified	25 Oct, v0.4.32–0.4.34: #223, #224, #225, #226, #227, #229, #231, #232, #233, #236, #237, #238, #239, #240, #241, browser/fake Frame evidence, guide

Release notes must preserve these limits until a newer recorded check changes them. When a feature is retested, add its date, exact app/Frame version, host type and proof here. The older v0.3.1 matrix is a historical snapshot and does not describe current coverage.