Report
Report an issue
One command gathers everything worth knowing about your machine and the last launch, and writes it to a file you can attach. It takes a few seconds and it saves a long back-and-forth.
Nothing installed yet, or stuck partway through? The install guides are the faster route.
1. Run the report
From the folder Revert is installed in. It only reads, it changes nothing, so it is always safe to run.
./revert reportOn Windows, drop the ./ and run revert report.
It prints the report and saves it as revert-report.txt. If the game crashed, launch it once before running this, so the crash is in the log it reads.
What is in it
It is plain text. Read it before you post it if you like, and if there is something in there you would rather not share, delete that line and send the rest.
It collects
- Your OS and version, kernel, and whether this is a Steam Deck
- Your CPU, memory, and free disk space
- Your graphics card and, more importantly, its driver version
- What Vulkan can see (the usual culprit on Linux and Mac)
- Which Wine runtime and DXVK version are in play
- How far the install got: game data, build, controller, toolchain
- The last 200 lines the game printed before it stopped
It never collects
- Anything from inside your game files
- Save games
- Serial numbers or licence keys
- Your home directory path or username, both stripped before the file is written
Your home directory and username are removed before the file is saved, so the result is safe to paste in public.
2. Open an issue
Paste the report in, or drag the saved file onto the box. A GitHub account is needed to post, which is free.
That second one is not a formality. Most of what we know about unusual hardware came from someone who ran it once and said so. If your machine is old, odd, or a distro nobody tests on, a report that it worked is worth as much as one that it did not.
What makes a report useful
Say what you expected
“It closed after five seconds” and “it closed after five seconds, I expected the main menu” are different reports. The second one tells us where to look.
Say what you already tried
If something changed the behaviour, even slightly, that is often the most useful sentence in the whole report.
One issue per issue
Two unrelated problems in one thread means one of them gets forgotten. It is usually the second one.
One thing we cannot help with
This project ships tooling, never game data. We cannot provide THUG2, point you at a copy, or help you find one, and issues asking for it get closed. You need to own the game.
Not sure your hardware is supported in the first place? Check the requirements.
