Record the HDMI check on the same monitor
Keep the 0.2.4 documentation to what was measured
Restart as the verified way out, the cable and VRR described by what was observed, HDR advice that matches a restarted session, and the update path for tools before 0.2.2.
Document the 0.2.4 changes
Update source in the diagnostic report, the 4K fix where this project's Gamescope is selected, and why a switch into Game Mode could leave the notification workaround unapplied before 0.2.4.
Document Gamescope selection in 0.2.3
Audit the whole manual against the code and the issue trackers
Every page was read against the code that ships today and against every open and
closed issue on the tracker, and each finding was checked by a second reader
whose job was to refute it.
The largest correction is that the manual did not know releases 0.1.9 and 0.2.0
exist. It still said the cause of the corrupted Game Mode menus was unknown and
offered the three workarounds as the remedy, and it said in three places that an
update cannot deliver Gamescope. It now describes the fault as fixed in 0.2.0,
names the cause, and gives the order a system on 0.1.8 or older has to follow.
Three pages sent the reader to release 0.1.7 to get the source. That tag carries
two of the three Gamescope patches, so anyone following those instructions built
an image without the menu fix. They now point at Releases in general, the same
form the README already uses, so they do not go stale again. Complete build also
links to the section that gets the repository, which it never did.
Troubleshooting is grouped into eight topics with an index at the top. Section
titles are unchanged, so links into them still resolve. _Sidebar.md is new, so
the pages are no longer listed alphabetically, and Home reads in the order a
person actually works, with How it works last.
Also corrected, each against the code it describes: the installer no longer
hides disks with mounted partitions, the base only build leaves out the
corrected Gamescope and cannot be sent it afterwards, tools older than 0.1.8
refuse any release naming a file they do not know, and returning to the SteamOS
Gamescope build is a deliberate rule rather than a fault.
Three commands this manual tells the reader to run were executed on a test
machine before it was written.
Add the Desktop Mode findings, the 32-bit overlay symptom, and point at 0.1.7
Four entries from measurements on 2026-09-26: Remote Play receiving in Desktop
Mode, where Steam's client falls back to a decode path costing 153 ms per frame
and the answer is to switch hardware decoding off or receive in Game Mode;
outgoing capture pinned at 25 frames per second by how Steam drives the screencast
portal rather than by any limit of the portal; the Gamescope crash on leaving Game
Mode, which reproduces on Valve's own build and is reported upstream; and the
32-bit overlay dependency, whose symptom is a SIGSEGV that points nowhere near a
performance overlay.
Stop naming one recovery release as required, and point at 0.1.6
Valve publishes one current recovery image and replaces it over time. The build
pages said 3.8.14 was required, and the Bazzite page told the reader to stop if
Valve offered anything else. The builder now records the release it finds and
warns when it is not one this project has validated, so the pages say that
instead, and explain that the checksum shown belongs to the 3.8.14 file.
How it works describes the Gamescope artifact at the version it is actually built
from and says the selection follows the installed package rather than a SteamOS
point release, which is what the code has done since 0.1.6.
The download pointers move from release 0.1.5 to 0.1.6.
Describe the partial output name, the resolver check and the preflight option
Document building on Bazzite and release 0.1.4 build instructions
Document casefold workspace and release 0.1.3 build instructions
Document installer 0.1.2 notification fix and upgrade path
Use release 0.1.1 for installation and complete builds
Add installation manual and troubleshooting guides