From d2f70296f54e5347117ab2f9725828ac59d9f2a6 Mon Sep 17 00:00:00 2001 From: 28allday Date: Fri, 31 Jul 2026 19:09:52 +0100 Subject: [PATCH] Correct the Shift+F2 claim: the keybind does not work in Game Mode MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The in-game keys table told users Shift+F2 toggles logging mid-game. That holds on the desktop, where the in-game Vulkan layer is the logger, but not in SteamOS Game Mode: there the logger is mangoapp, which ignores the keybind. Verified under nested gamescope — the keypress produced no log at all, while mangohudctl in the same harness started one immediately. Document mangohudctl as the way to start/stop a log by hand in Game Mode. It drives mangoapp over a SysV message queue, so it needs no display, no Wayland socket and no window focus. --- README.md | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index cfb3f30..56bbefb 100755 --- a/README.md +++ b/README.md @@ -203,9 +203,20 @@ In-game keys (set by the script's MangoHud block): | Key | Action | |---|---| -| `Shift+F2` | Toggle logging on/off mid-game | +| `Shift+F2` | Toggle logging on/off mid-game — **desktop only, see below** | | Your existing `toggle_hud` key | Hide the HUD overlay (logging keeps running) | +> **`Shift+F2` does not work in SteamOS Game Mode.** There the logger is +> mangoapp, not the in-game Vulkan layer, and mangoapp ignores the keybind. +> Verified under nested gamescope: the keypress produced no log at all. To +> start/stop a log by hand in Game Mode, use `mangohudctl` (ships with MangoHud), +> which drives mangoapp over a message queue and needs no display or focus: +> +> ```bash +> mangohudctl set log_session true # start +> mangohudctl set log_session false # stop (also writes a _summary.csv) +> ``` + CSV files appear in `~/Downloads/mango-logs/`. Drop them into for graphs, or open in a spreadsheet.