16 Free ProtonDB and Steam Deck Log Export Tools for October Fest Builds - 2026

Your #playtest thread has twelve messages saying “won’t launch on Deck.” Three are screenshots of a black screen. One is a phone photo of the handheld. Nobody attached Proton logs, MangoHud CSV, or a ProtonDB test note with build_label. Engineering guesses while October fest traffic reproduces the same silent failure on Proton Experimental.

Autumn 2026 tightens Deck Verified expectations and pushes more teams through Proton Experimental previews before reviewers freeze images. Support asks shifted from “did you test glyphs?” to “export the log bundle.” This Listicles & Resource Roundups piece lists sixteen free tools to collect Deck/Proton evidence in one zip—paired with crash symbolicate receipt when the failure is a Windows minidump on desktop, not a Linux-layer Proton fault.

Non-repetition note: 16 Deck glyph and input tools owns Steam Input SVG audits. This URL owns log export + compat research—ProtonDB, MangoHud, Gamescope, Proton compatdata logs, and deck_log_bundle_receipt_v1.json. Forward Help #12 — MangoHud GPU 99% idle despite menu FPS receipt when logs show pegged GPU, not missing glyphs.

Why this matters now (October 2026)

1. Proton Experimental moves faster than fest demo branches—players run newer Proton than you tested.
2. Fest support volume — One zip beats twelve Discord screenshots.
3. Crash correlation — Crash symbolicate receipt covers Windows .dmp; Deck needs Linux-side logs in the same build_label folder.
4. MangoHud false greens — Menu FPS opinion can pass while GPU stays pegged—only logs prove it (case study pattern).
5. Facilitator contracts — Multi-channel template should name log bundle paths, not “send a video.”

Direct answer: Adopt four tools this week—ProtonDB research habit, MangoHud logging, Proton log path copy, and deck_log_bundle_receipt_v1.json—then expand from the table below before promoting October builds.

Who this list is for

Time: ~90 minutes to configure the four-tool stack; 15 minutes per playtest incident afterward.

Beginner path (first playtest export)

1. Pin build_label in game debug overlay or version.txt.
2. Reproduce issue once on Deck (or Linux desktop with Proton).
3. Run Tool 3 (MangoHud) for 5 minutes around the failure.
4. Copy Tool 6 (Proton log) files into release-evidence/deck-logs/YYYY-MM-DD/.
5. Add Tool 2 (ProtonDB) link if your App ID already has reports.
6. Fill Tool 12 (deck_log_bundle_receipt_v1.json); post zip link in #playtest.

Do not paste full compatdata trees into Discord—zip and upload.

Developer path (fest ops stack)

1. Automate MangoHud output_folder per build_label in facilitator README.
2. Add deck_log_bundle_ok column on BUILD_RECEIPT.
3. Fail promotion when receipt missing while platform=deck blockers open in playtest CSV.
4. Cross-check Proton Experimental pin in BUILD_RECEIPT against ProtonDB “experimental” notes.
5. Pair desktop crash symbolicate when the same build_label crashes on Windows too.

Minimum four-tool stack

Add tools 4–11 and 13–16 as co-op, cloud-save, or audio-deck issues appear.

The sixteen tools (free tier focus)

Tool 1 — ProtonDB (community compatibility reports)

URL: ProtonDB
Job: See how other players label Borked / Running / Gold on Deck/Linux—search by Steam App ID.
Beginner: Read top three reports; note Proton version strings players mention.
Dev: Export PDF or save permalink into evidence folder—not a substitute for your own logs.
2026 note: Experimental Proton spikes show up in reports before your fest branch catches up—treat as early warning, not gospel.

Tool 2 — Steam Deck compatibility (Steamworks partner docs)

URL: Steam Deck compatibility documentation
Job: Official Verified / Playable / Unsupported requirements—log export supports cert conversations.
Pair: Deck Verified autumn refresh.

Tool 3 — MangoHud (overlay + CSV logging)

URL: MangoHud GitHub
Job: Log FPS, frametime, GPU%, CPU%, RAM to CSV while reproducing menu idle or gameplay hitch.
Config snippet (save as MangoHud.conf reference):

fps_limit=60
gpu_stats
cpu_stats
frametime
log_duration=900
output_folder=/home/deck/deck-logs

Dev: 15-minute idle menu log is the evidence row for Help #12 (GPU pegged despite FPS cap).
Limit: Overlay on ≠ fix—logs inform engineering.

Tool 4 — Gamescope (session logging context)

URL: Gamescope
Job: Understand when SteamOS wraps your game in compositor—explains resolution/FPS caps in logs.
Use when: Fullscreen vs borderless behaves differently on Deck only.

Tool 5 — Proton Experimental (Steam client beta channel)

Job: Match what reviewers and early adopters run—pin version note in BUILD_RECEIPT (proton_pin: experimental-2026-05).
Workflow: Re-test fest build when Steam client updates Proton—log bundle before/after in changelog.

Tool 6 — Proton / Steam log files (compatdata)

Job: After crash or hang, copy logs from Steam library:

Beginner: Zip only files modified today—do not send entire compatdata (GB-scale).
PowerShell on dev PC (find recent logs in copied bundle):

Get-ChildItem -Recurse -File |
  Where-Object { $_.LastWriteTime -gt (Get-Date).AddDays(-1) } |
  Select-Object FullName, Length, LastWriteTime

Tool 7 — journalctl (SteamOS Desktop Mode)

Job: Export kernel/GPU driver messages when game hard-freezes OS.
Command (facilitator on Deck):

journalctl --since "1 hour ago" --no-pager > deck-journal-last-hour.log

Privacy: Scrub usernames before external share.

Tool 8 — OBS Studio (Deck capture via remote play or dock)

URL: obsproject.com
Job: Screen + audio capture when logs are inconclusive—pair with log zip, never replace it.
Pair: OBS Replay Buffer concat blog for desktop playtests.

Tool 9 — Steam support / SteamOS system report (high-level)

Job: Include steam system report or Settings → System → Export when filing Valve/platform tickets.
Use sparingly: Large; redact serials.

Tool 10 — Lutris / SteamTinkerLaunch (optional advanced launch wrappers)

Job: When testers use non-default Proton builds—document exact launch command in receipt.
Risk: Facilitator Proton ≠ consumer Proton—receipt must record launch_method.

Tool 11 — tar / 7-Zip (bundle discipline)

Job: One deck-logs-<build_label>-YYYY-MM-DD.zip per incident.
Naming: Include build_label in filename—partners grep tickets by string.

Tool 12 — deck_log_bundle_receipt_v1.json (promotion gate)

Job: Machine-readable checklist that the zip contains required artifacts.

{
  "schema": "deck_log_bundle_receipt_v1",
  "build_label": "fest-demo-2026-10-rc3",
  "surface": "fest_public",
  "platform": "steam_deck",
  "proton_pin": "experimental-2026-05",
  "bundle_path": "release-evidence/deck-logs/2026-05-27-fest-demo-2026-10-rc3.zip",
  "artifacts": {
    "mangohud_csv": true,
    "proton_steam_log": true,
    "player_log": true,
    "protondb_link_saved": true,
    "journalctl_excerpt": false
  },
  "gates": {
    "L1_build_label_in_overlay": true,
    "L2_bundle_under_50mb": true,
    "L3_no_secrets_in_zip": true,
    "L4_repro_steps_txt": true
  },
  "promotion_allowed": true,
  "human_signoff": { "role": "facilitator", "utc": "2026-05-27T22:00:00Z" }
}

Set promotion_allowed false if MangoHud missing on GPU-idle reports.

Tool 13 — Text REPRO_STEPS.txt (free discipline)

Job: Three lines minimum: build_label, steps, expected vs actual.
Why listed: Logs without repro steps waste engineering time.

Tool 14 — 18 playtest feedback tools (async capture)

Job: Tag CSV rows platform=deck and link zip URL in Tool 12 column.
Distinction: That list owns forms/Discord; this list owns Deck log paths.

Tool 15 — BUILD_RECEIPT + Thursday row review

Job: Add optional columns:

"deck_log_bundle_ok": true,
"deck_log_bundle_receipt_path": "release-evidence/deck-logs/deck_log_bundle_receipt_v1.json",
"proton_pin": "experimental-2026-05"

Diff deck_log_bundle_ok across promotions like other receipt booleans.

Tool 16 — Friday Block 5 (archive weekly)

Job: Move last week’s deck-logs/ zip snapshot into weekly/—prevent accidental overwrite before postmortem.

Facilitator README snippet (copy/paste)

## Deck log export (required on blockers)

1. Note on-screen `build_label`.
2. MangoHud log 5 min (menu + gameplay).
3. Copy today's Proton/player logs into `deck-logs/<build_label>/`.
4. Write REPRO_STEPS.txt (3 lines).
5. Zip; upload; paste link in playtest CSV.
6. File deck_log_bundle_receipt_v1.json (promotion_allowed only if L1–L4 pass).

Add to multi-channel facilitator contract appendix.

Proof folder layout

release-evidence/deck-logs/
  README.md
  2026-05-27-fest-demo-2026-10-rc3/
    REPRO_STEPS.txt
    mangohud.csv
    player.log
    steam-270880.log
    protondb-permalink.txt
    deck_log_bundle_receipt_v1.json
  weekly/
    2026-W22-snapshot.zip

Tools 1–6 — expanded workflow notes

Tool 1 (ProtonDB): Create protondb-permalink.txt with report URL and date accessed. When reports cite Proton 9 vs 10, add a row to your promotion changelog—fest teams often discover Experimental drift here before internal QA.

Tool 2 (Steamworks Deck docs): Copy the current Verified checklist bullets into release-evidence/deck-logs/README.md. Auditors ask whether you read partner docs; the README proves it.

Tool 3 (MangoHud): Run two captures: (a) idle menu 15 minutes, (b) first combat or stress scene 5 minutes. Filename mangohud-idle.csv vs mangohud-combat.csv—Help #12 cares about idle.

Tool 4 (Gamescope): Note gamescope -W -H or SteamOS defaults in REPRO_STEPS.txt when resolution overrides differ from Windows.

Tool 5 (Proton Experimental): Record client beta channel in Steam → Settings on facilitator Deck; screenshot optional, text mandatory in receipt.

Tool 6 (compatdata logs): Unity games: Player.log path in %USERPROFILE%\\AppData\\LocalLow\\ inside prefix. Godot: user:// mapped under prefix—facilitator README should list engine-specific filenames so beginners do not zip empty folders.

Tools 7–11 — expanded workflow notes

Tool 7 (journalctl): Use only when the game freezes the compositor or kills Wi-Fi—kernel lines explain “Deck rebooted.” Trim to ±10 minutes around repro.

Tool 8 (OBS): Burn-in build_label on overlay if possible—video without label repeats the Discord screenshot failure mode.

Tool 9 (system report): Attach when escalating to Valve or GPU vendor; strip hardware serials. Not for every playtest row.

Tool 10 (launch wrappers): If a facilitator uses SteamTinkerLaunch to force Proton GE, receipt field launch_method: stl and version—your default depot may differ.

Tool 11 (zip): Prefer zip -r deck-logs-rc3-2026-05-27.zip . from inside the dated folder so paths are shallow.

Tools 13–16 — expanded workflow notes

Tool 13: Template:

build_label: fest-demo-2026-10-rc3
steps: Launch → Press Start → Idle menu 15 min
expected: GPU low at menu
actual: Fan loud; MangoHud GPU 99%

Tool 14: Add column deck_log_zip_url to playtest CSV—engineers filter platform=deck without opening Discord.

Tool 15: Thursday row review should show deck_log_bundle_ok flips only when zip + receipt paths change together.

Tool 16: Weekly archive prevents “we overwrote the only MangoHud CSV from Tuesday.”

Bash: validate bundle before upload (CI sketch)

#!/usr/bin/env bash
set -euo pipefail
DIR="${1:?deck log folder}"
test -f "$DIR/REPRO_STEPS.txt"
test -f "$DIR/deck_log_bundle_receipt_v1.json"
jq -e '.promotion_allowed == true and .artifacts.mangohud_csv == true' \
  "$DIR/deck_log_bundle_receipt_v1.json"
echo "deck_log_bundle gate: OK"

Wire after human reviews CSV—automation should not post public zips without redaction review.

Desktop + Deck dual-export night (engineering)

Same build_label on both rows. Refund dashboard tag perf + deck when reviews cite heat—join logs before blaming store copy.

Partner / diligence one-liner

Attach to Q4 packets (when blog #10 ships): “Deck playtest exports include MangoHud CSV, Proton logs, and deck_log_bundle_receipt_v1.json keyed to build_label—see attached zip index.”

Engine-specific log filenames (Deck via Proton)

Facilitators should paste this table into README—beginners search the wrong folder and declare “no logs exist.”

Privacy and redaction before external share

Keep a REDACTION_NOTES.txt in zip when you strip lines—partners trust edited bundles more than mystery omissions.

Listicle vs listicle (avoid wrong URL)

Routing support to the wrong listicle wastes a fest week.

Autumn cert week calendar (suggested)

Resource queue forward (Help #12 / Resource #9)

This blog pairs Help-Create #12 (MangoHud GPU idle fix) and Resource-Create #9 (Wwise/FMOD refresh includes Deck perf lane). When those ship, reciprocal links should point here for log export steps—not glyph audits.

Incident response playbook (60 minutes)

If ProtonDB shows new Experimental regression same day, freeze promotion even when Windows smoke is green.

Tool selection matrix (symptom → start here)

Worked example (composite)

No invented metrics—pattern teams report during autumn cert prep.

Promotion gate integration

[ ] deck_log_bundle_receipt_v1.json exists for candidate build_label
[ ] MangoHud CSV attached when symptom is perf/power
[ ] REPRO_STEPS.txt present
[ ] build_label matches BUILD_RECEIPT row
[ ] crash_symbolicate_ok evaluated for Windows depot (parallel column)
[ ] Wednesday smoke passed on same build_label

Common mistakes

1. Screenshot-only support — cannot diff Proton versions.
2. Zipping entire compatdata — too large; rejected by partners.
3. Missing build_label — logs become unassignable noise.
4. Confusing glyph bugs with Proton bugs — route to glyph listicle.
5. Promoting on ProtonDB “Gold” — community tier ≠ your build tested.
6. Skipping receipt JSON — zip exists but promotion gate has no boolean.
7. Desktop crash only — still file crash symbolicate receipt.

Key takeaways

1. October 2026 support asks for log bundles first.
2. ProtonDB is research; MangoHud + Proton logs are evidence.
3. deck_log_bundle_receipt_v1.json wires Deck exports to BUILD_RECEIPT.
4. Four-tool minimum stack is enough to start.
5. Glyph listicle complements—does not replace—this export list.
6. Help #12 forward when GPU idle pegged despite FPS cap receipt.
7. Crash symbolicate handles Windows .dmp; this list handles Linux/Deck layers.
8. Facilitator contract should require zip + receipt, not photos.
9. Proton Experimental pin belongs in BUILD_RECEIPT every promotion.
10. Friday Block 5 archives weekly deck-log snapshots.

FAQ

Is ProtonDB enough to pass Deck Verified?

No. It is a signal. You still need your own logs and Steamworks compatibility testing.

How big should the zip be?

Aim under 50 MB per incident (L2 gate)—exclude unrelated titles’ compatdata.

Can we use Sentry on Deck builds?

If you ship Linux symbols—yes, parallel column. This list covers local export when SaaS is not wired.

What if the game is Windows-only depot?

Players still run via Proton on Deck—logs matter. Document platform: windows_via_proton in receipt.

Does this replace MangoHud case study?

No. Case study narrates recovery; this list is tooling.

Forward Help #12?

Yes—when mangohud.csv shows GPU peg at menu idle despite menu FPS receipt.

Should every playtest row include a zip?

Only blockers and perf/deck tags need bundles. Cosmetic UI bugs still deserve build_label in REPRO_STEPS.txt without a 40 MB upload.

Can we automate ProtonDB scraping?

Do not scrape—save permalinks manually. Automation breaks ToS and omits the access date auditors expect in evidence folders.

Standing facilitator line (copy/paste)

“Please upload deck-logs-<build_label>-<date>.zip with MangoHud CSV, today’s Proton/player logs, REPRO_STEPS.txt, and deck_log_bundle_receipt_v1.json. Screenshots alone delay the fix.”

Pin in #playtest before October traffic—saves repeating the sixteen-tool list every incident.

Closing discipline: If you cannot produce Tool 12 JSON tonight, you can still ship Tools 1, 3, and 6—but mark BUILD_RECEIPT deck_log_bundle_ok: false until the receipt exists. Half-export discipline beats pretending logs were too hard for a fest SKU.

Related reading

• Crash symbolicate receipt (one evening)
• 16 Deck glyph and input tools
• Deck Verified autumn 2026 refresh
• MangoHud GPU 99% case study
• Menu FPS opinion
• Wednesday demo smoke
• 18 playtest feedback tools
• Multi-channel facilitator contract
• Top 20 evidence receipts hub
• Outbound: ProtonDB, Steam Deck partner documentation

Next in cluster: 7-day Addressables invalid-key audit challenge (published); Proton Vulkan silent-demo case study (published); blog backlog #5 refund correlation playbook.