We constantly strive to evolve and improve War Thunder with every passing update, taking into account your feedback, ideas and suggestions as well as delivering new features, locations, improvements, and of course vehicles to expand the game to new heights. One of the key factors that helps us continue to improve the game for everyone is bug reporting; this helps us to identify and fix any issues that unfortunately may occur. Bug reporting allows us to address and resolve matters that may interrupt or interfere with players' experience or improve the historical parts of the game by making things more accurate and true to life.
Here, we talk a little bit more about the importance of bug reporting, answer some of your key questions, and also provide walkthroughs for all the steps required to correctly create a valid bug report that contributes to helping improve the game.
How to Make a Bug Report
Anyone who has a War Thunder account can make a bug report. Our dedicated website allows anyone to create a full bug or historical report and let us know of any issues you have found.
Once there, you can choose what specific platform, category and game version you want to report the matter too. Every category area has a helpful set of notes detailing what is required for the report to be the most effective. Be sure to check the area specific (or file specific) notes before submitting your report.
In general though, the basic and core parts of a standard or gameplay related bug report are:
- Clear descriptive title of the issue
- Full description and details of the issue
- Steps how to reproduce the issue
In the case of a historical matters, one of the following two points will be required:
- One primary historical source (User/Factory/Repair Manual, Original handbooks etc)
- Two secondary sources (Reference works, museums, Biographies, Books, "expert" opinion publications, websites etc)
Once you have everything ready, you can submit your report and await its review by a Technical Moderator, developer or our QA team, who will first test and reproduce the issue where possible and then either forward the matter on or request any additional information that may be required.
Finding the Client Version
The client version must be added to all reports. It can be found in the top right corner of the screen in any menu, such as the hangar.
Additionally, it can also be seen in the launcher.
Disabling custom content
To make sure the issue is not caused by custom, user-generated content, this content must be disabled before creating a report. We cannot provide support for custom content. Here is a list of possible custom content that can interfere with the game and a link to their wiki page, which helps in disabling the content:
- Sound mods
- Custom localisation
- Custom hangar
- Custom sights
- Custom missions (both usermissions and multiplayer missions from URL)
- User skins
If you have found an issue in the CDK or functions provided by it, please report this in the Community Bug Reporter
Game crashes without error messages
If the game crashes without any error messages, you need to submit a bug report, and also take the following steps:
1. Temporarily disable your antivirus and try to reproduce the issue.
- If the issue persists, please inform us what antivirus you use and what actions in the game lead to the problem.
2. If the issue persists, run the game client with anti-cheat disabled.
- If the issue persists, it’s related to the third-party software. Please disable third-party software one by one (primarily ones that are related to overlays: Nvidia, Discord, Twitch, MSI Afterburner, etc.) and report which software disabling helped.
3. If the issue still persists, reproduce it with the debugger:
- Download and install the debugger; https://learn.microsoft.com/en-gb/windows-hardware/drivers/debugger/
- Run the debugger;
- Run the game client with anti-cheat disabled;
- Wait for the login screen;
- In the debugger, select menu: File -> Attach to Process;
- Enable sorting “By Executable”;
- Select game process “aces.exe” and press Ok;
- In the command line of the debugger (bottom of the window) enter: sxe *
- Press F5;
- Perform actions in the game that lead to closing without errors;
- When an exception occurs, the game will freeze and stop responding, but the command line will become available in the debugger again;
- Enter command in the debugger command line: .dump /m path_to_save_dump; for example: D:\minidumpfile.dmp
- Attach saved dumpfile.
FAQ
- What is a client log (.clog) and how do you obtain it?
- What is a DxDiag log and how do you obtain it?
- What is a launcher log and how do you obtain it?
- What are problem report files and how do you obtain them?
- How do you take screenshots using the in-game functionality?
- What is the performance profiler and how do you use it?
- What is the cache and how do you clear it?
- What is game integrity and how do you verify it?
- Client and Server replays: What is the difference and how do you find them?