Steam Deck OLED Proton logs are game-specific diagnostic files generated by Valve’s Proton compatibility layer when you explicitly enable logging. They can help distinguish a Windows-game launch failure from missing runtime files, graphics translation problems, and launcher errors. The reliable first step is to add PROTON_LOG=1 %command% to one game’s Steam launch options, reproduce the failure, and inspect the resulting steam-APPID.log in the Deck user’s home directory. Logging does not repair a broken game by itself.
What Proton diagnostic logs reveal and cannot prove
Proton is Valve’s compatibility tool for running many Windows games on Linux. Its stack includes Wine plus graphics translation and other components, so a failed launch may involve several layers. The default Proton diagnostic log records Wine and related runtime messages for a specific attempt. It is not a universal SteamOS crash log, network trace, GPU performance benchmark, or guarantee that the first line marked err identifies the root cause.
On the Deck’s default desktop account, the home directory is commonly /home/deck. A Steam game with application ID 123456 would therefore normally write /home/deck/steam-123456.log when logging is enabled. This is an illustrative filename, not a real game or an observed device output. Valve documents the default name as steam-$APPID.log; custom PROTON_LOG_DIR changes its directory, and relaunching the same game can overwrite the earlier log. Copy important files before another test.
Logging is per launch configuration. A native Linux title is not automatically running through Proton, and a non-Steam shortcut or third-party launcher may follow different paths and identifiers. Check which compatibility tool the title is using before expecting the same file or treating a missing log as evidence of an operating-system failure.
The three places people confuse
| Location or output | Purpose | What you should do |
|---|---|---|
~/steam-APPID.log |
Opt-in per-game Proton/Wine diagnostic messages | Read or copy after reproducing the failure |
| Steam client logs under the user’s Steam directory | Steam interface, downloading, and client activity | Consult if Steam itself cannot start the launch |
steamapps/compatdata/APPID |
Proton’s game-specific Windows compatibility prefix | Do not delete just to obtain a log; it can contain saves and settings |
steamapps/shadercache/APPID |
Related cached graphics data | Do not confuse shader data with Proton’s text log |
The directory structure can vary between the internal SSD, microSD game libraries, custom installations and third-party tools. A log stored in the home directory is not proof the game files or prefix share that location.
Enable logging without changing the game’s data
- In Gaming Mode, open Steam > Library, select the affected title and open its gear icon or Properties screen. Locate General > Launch Options; wording can vary slightly with client layout.
- Copy any existing launch option into a separate note first. If the field is empty, enter exactly
PROTON_LOG=1 %command%. - If a game already needs an argument or a wrapper, preserve its functional command rather than blindly replacing it. Environment assignments go before
%command%in the common Steam syntax; game arguments normally follow it. Complex wrappers need case-specific handling. - Confirm the game is configured to use Proton where appropriate. Under Properties > Compatibility, a forced compatibility tool is optional for many supported games; do not turn it on for a native title simply to manufacture a log.
- Start the game once, reproduce the same symptom and close it cleanly if possible. Note the local time and exactly what you saw: splash-screen exit, black window, title-screen crash, or failure after a launcher sign-in.
- Hold the power button and choose Switch to Desktop, open the file manager and navigate to Home. Reveal hidden files only if you are exploring Steam’s configuration folders; the default
steam-APPID.logfile itself is not hidden. - Find a freshly modified
steam-<numeric-id>.log. If you cannot tell which file is relevant, look up the game’s Steam application ID through its official store details or identify the filename created immediately after the test; do not assume another game’s log belongs to the failure. - Copy the text log to a named diagnostic folder with the date and game version. Remove the logging option when finished, especially if the title is creating large files.
If logging succeeds but a game now launches normally, that is a change worth recording, not proof that the logging option fixed it. Repeat once with and once without the option to distinguish coincidence from a reproducible behavior change.
Read the log from the outside in
Start with the newest section and the moment of failure, then work backward. Search for the executable name and broad terms such as err, fail, exception, vulkan, dxvk, and wine. None of these terms alone establishes a diagnosis. A few Wine fixme messages are often informational: they flag incomplete or alternative implementation, not necessarily a fatal error.
If the game launches to audio but has a black window, investigate display or graphics initialization and record whether it is using DXVK/VKD3D; do not assume every Vulkan warning requires reinstalling SteamOS. If it opens a launcher and then exits, examine the last successful launcher phase and check whether authentication, web content, DRM, or a missing dependency is independently implicated. If it crashes after loading a save, compare a new session with a backup of the old save before concluding that the graphics driver is defective.
A useful report includes game title and application ID, SteamOS version and update channel, Proton version, whether the game is on SSD or microSD, launch-option string, reproducible steps, the first visible failure, and a short redacted log extract with context. Attach the full log only where trusted support requests it and review it for usernames, account tokens, home-directory names, and paths first.
What if no steam-APPID.log appears?
Work through causes in order. First, check that launch options were saved for the actual Steam entry you used; duplicate shortcuts can make it easy to edit the wrong item. Next, verify the game is using Proton, not a native Linux build. Check Home for the most recently modified steam-*.log file and remember that PROTON_LOG_DIR may redirect it. If a shell wrapper or third-party launcher is involved, isolate the plain Steam launch and retest without destroying its configuration.
If Steam fails before Proton starts, the Proton environment may never run, so no Proton log is produced. In that case check Steam’s own client behavior, file verification and runtime prerequisites rather than repeatedly pressing Play hoping for a new text file. If a game launches but the log is empty or cut short, record that fact; a hard process termination may prevent the final buffer from being written. Do not declare a missing log a corrupted compatibility prefix.
Use advanced logging sparingly
Valve documents PROTON_LOG_DIR for directing output to a chosen directory. For example, a user who has already created a writable folder inside their home directory can set PROTON_LOG_DIR=/home/deck/proton-debug PROTON_LOG=1 %command%; the directory must exist and permissions must allow writing. Avoid an arbitrary USB drive that may not be mounted at launch. Keep directory names free of spaces in a simple example unless you understand shell quoting.
More verbose Wine debug channels can make files very large and can alter timing. Do not increase verbosity before collecting a simple default log, and avoid posting unredacted multi-megabyte logs publicly. Likewise, compatibility-tool switching can change game behavior or its prefix; save the current Proton selection and existing launch options before testing one change at a time. Reverting a launch option is straightforward; restoring game data lost to deleting compatdata is not.
Free tools for inspecting Proton logs
Steam Library Properties is included at no cost on the Deck and sets the launch option per title. Dolphin File Manager, available in Desktop Mode, locates and copies log files without terminal commands. A plain-text editor such as the default desktop editor or Kate (free if available) can search a log; avoid a word processor that may alter line endings when saving.
A Proton log can overwrite the previous reproduction
Valve’s Proton runtime documentation says PROTON_LOG=1 writes steam-APPID.log to the home directory unless PROTON_LOG_DIR is set, and its sample configuration warns that a subsequent run with the same app ID can overwrite the previous log. After reproducing a failure, copy the log to a separately named evidence file before trying another Proton version or launch option. Record the exact AppID and Proton build next to that copy; then remove the logging launch option when troubleshooting ends. Redact usernames, local paths and account tokens before sending the log to a third party. A missing log may mean the Windows title never reached Proton, not necessarily that the game completed startup successfully.
A sensible next diagnostic step
Collect one log after a reproducible failure, then compare its final messages with the exact visible symptom and current Proton choice. If the failure is not explained, prepare a short, redacted report for the game’s support channel or Valve’s Proton issue tracker and include whether a second Proton version changes it. Leave the prefix and shader-cache trees untouched until evidence identifies a targeted, reversible fix. Steam Deck OLED Proton logs are most valuable as evidence tied to one test, not as a reason to perform a general cleanup.
