Document Steam notification compatibility in 0.2.5
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.
Explain manual review of the Gamescope pin
Document Gamescope selection in 0.2.3
Document the verified 0.2.2 desktop update
Clarify update sources and compatibility checks
Document the published 0.2.2 repository transition
Document repair of incomplete installer updates
Explain the repair already available in 0.2.1, remove the obsolete downgrade detour, and clarify when a second installation can place files skipped by older tools.
Document the signed update-source transition mechanism
Document 0.2.1: the mode filter, and only what was measured about the exit crash
Before you start now says to choose 3840x2160 rather than 4096x2160, and distinguishes
a system running this project's Gamescope build, where the wider mode is no longer
offered, from one running the system's own.
The crash when leaving Game Mode no longer calls itself harmless, no longer names the
Vulkan library as unloaded, and no longer says nothing is lost. It records what was read
out of core files and says plainly that the cause and the frequency are not established,
that no dialog appears, and that the command for clearing old dumps was wrong.
Safe Graphics says which case needs a Game Mode restart instead. Updates and recovery
says the update is cancelled if one of this project's parts cannot be restored. How it
works describes all four Gamescope corrections and which two are upstream. The build
guide documents the build root helper.
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.
Name both Steam launchers, separate tested drivers, and document the glitching menus
The documented way to switch the Remote Play receiver off named the Game Mode launcher
alone, so it stopped working on the desktop once the desktop launcher was covered too.
It now names both and carries a command that writes both overrides. The encoder and
notification sections say which launchers they attach to, and why the desktop has to
have LIBVA_DRIVER_NAME removed while Game Mode never sets it.
The driver list explains that a version this project tested and a version NVIDIA merely
documents for your GPU are different claims, and that the list says so when nothing
offered has been tested here.
A new entry covers the Game Mode menus drawing with glitches while a game runs and the
performance overlay is off, with the two display settings that clear it. It states what
is measured and what is not: the same glitching appears with the overlay SteamOS
packages and on an older installer integration, the tested mode was DisplayPort at
2560x1440 and 165 Hz with HDR off, and that same mode is recorded as working with HDR
on.
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.
Document installer 0.1.2 notification fix and upgrade path
Document complete builds and Windows setup
Add installation manual and troubleshooting guides