Tool: Wine / Proton Log Explorer

This is an automated archive made by the Lemmit Bot.

The original was posted on /r/linux_gaming by /u/timkurvers on 2024-09-24 18:55:53+00:00.

When a game refuses to run under Wine / Proton, the first (technical) port of call may be to scour the debug log for indicators of the problem. For Proton these logs can be enabled using PROTON_LOG=1 as indicated in the Proton FAQ. Unfortunately for us humans, these Wine debug logs tend to be rather unwieldy.

I originally posted about Wine Log Explorer on r/wine_gaming, but it seems to work well for Proton logs, too. It is a web tool which parses debug log files into interactive tree structures, including the ability to filter by process / thread + searching in free text: see the screenshot below.

It's fully client-side, so no files leave your browser. Hopefully this tool can help clarify why a game behaves or crashes in a certain way, in particular for games that prevent attaching debuggers.

Link:

Project on GitHub:

Feedback, issue reports or code contributions are greatly appreciated!