windows all Windows Graphic and Graphics Device Guidelines - IMPORTANT, read BEFORE posting!

[Wibox 22,698]

How to post Graphic and Devices Issues
All visual issues including display device, graphics and model errors  

Whenever your are experiencing visual issues within the War Thunder Client (e.g. wrong colors, distorted models) or problems with your video devices, please use the guidelines below.
 
To ensure that we are able to help you as quickly as possible, please be reminded that we can only help you properly when the submitted files and information are complete.

Also, be aware that you should only describe one issue per thread. If you experience multiple issues, please open a new thread for each separately, even when the issues appear to be similar.

 

In addition, please make sure to attach all required files directly to the forums unedited. Externally linked files and compressed files are not accepted.
Thank you for your help!
 

---

If you are using a custom hangar, sound or localisation modification to the client, then please return you client to its 'normal' configuration and test the issue BEFORE submitting a bug report. 

 

Please make sure to summarize the problem in your topic title as short and precise as possible.

 

How to use the Technical Reporting Forum:

To access the Technical Reporting Forum there are two ways.  

1.  Via this link: https://community.gaijin.net/issues/p/warthunder

2.  Using the Game Interface in the Hangar.  Select the Community Tab and then click on Report an issue

 

This will bring you to this screen:

Follow the instructions below.

 

To make the report valid and useful, please add the following files and information to your opening post:
 

1. A detailed description of the issue you have encountered. It is also important that you describe how we can reproduce the issue, if you are able to reproduce it.

 

2. If applicable, the full name of the vehicle affected.

 

3. If applicable, the name of the map as well as the coordinates of the position affected.

 

4. One or multiple attached screenshots showcasing the issue and the client replay and server replay .

 

5. Attach the Client Log  of the session in which the error occurred. If the problem is persistent, attach the latest one available.

 

6. Attach your system's current DxDiag Log .

 
To better help us resolve the issue, please also include the following:
 

7. If possible, link a short video showcasing the issue.

 

If you have an FPS issue:

Can you also play several games using the FPS tool.  Please run the tracert during one of these games and then supply all the files asked for in the template/guidelines.
https://forum.warthunder.com/index.php?/topic/245960-tool-to-use-when-encountering-fps-drops/

 

Can you also do a tracert at the time you experience the issue.
Click the Windows Icon (bottom left hand side of screen) This will display the Menu options.
Choose Run
Type cmd (this will open a command shell window)
Type - tracert warthunder.com
Press Enter
Please screenshot and include the path result.

 

To trace FPS issues we need a sequence of information. We need the FPS tool to be running for 2-3 games(1 if it is a long SB(EC) game), we need the replay files(both client and server).  We need the clog file and when the relevant stutter, or FPS event happens; we need a screenshot of this(PrnSrcn will capture the FPS and other information. F12 will not).  This provides the time and date and location for us to look at.(Have you noticed that the filenames for screenshots are a time and date?) The location is in the meta data.   We also need the tracert to show what your connection was like at the time of the issue. We understand this is a complex process, but the issue is complex.
 

Please provide all the files and information asked for above with your report.  This will speed the resolution process.

[Wibox 22,698]

What is a Client Log and how do you obtain it?
 

 

The Client Log
Client logs (file extension: .clog) are files generated by the War Thunder client and show a reflection of all the actions a user has performed in one secluded game session. As soon as the launcher initializes the start of the game, a new Client Log is being started, which is finalized when the client is closed (the game session ends). Besides recording the actions of the user, it also records the client-side calculations and has a built-in error catching system, that will allow the technical administration to identify game code or synchronization issues efficiently.

Client Logs are being saved once after a game session has ended. If you have an error that is reproducible, you can help increasing the expressiveness of your Client Log by starting a new game session, reproducing the error and then exiting the game manually. This way, the Client Log is very small and the error can be identified more easily.

Please note that for all bug reports, only the Clog File is required. Please do not attach the Clog File that includes the cef extension.

How to obtain your Client Log:

Client Logs are created automatically, so the only thing you need to do is to locate them.

DOWNLOAD FROM GAIJIN ENTERTAINMENT WEBSITE

 

1. If you have downloaded War Thunder from the Gaijin Entertainment website, follow the installation path that you've specified during installation and locate the '.game_logs' folder

 

 

 

2. Identify the Client Log (.clog) file that was created during the session in which you recognized the issue or bug. This is usually the latest file created, so sorting by date is the easiest option.

The files itself are also time-stamped, and follow this scheme: YEAR_MONTH_DAY_HOUR_MINUTE_SECOND_ID.clog

 

3. Attach the Client Log to your bug report

 

 

DOWNLOAD FROM STEAM

 

1. If you have downloaded War Thunder using Steam, follow the standard Steam installation path and locate the '.game_logs' folder

 

 

 

2. Identify the Client Log (.clog) file that was created during the session in which you recognized the issue or bug. This is usually the latest file created, so sorting by date is the easiest option.

 

The files itself are also time-stamped, and follow this scheme: YEAR_MONTH_DAY_HOUR_MINUTE_SECOND_ID.clog

 

3. Attach the Client Log to your bug report

[Wibox 22,698]

What is a DxDiag Log and how do you obtain it?
 
The DxDiag Log
The DxDiag log (file extension: .txt) is a text document that is created by Microsoft's DxDiag diagnostics tool, showing non-personalized information about the hardware and drivers of your system. The DxDiag log file helps our technical administration to identify whether the problem you encounter is happening due to incompatibilities or issues with certain hardware or driver components on your system. It is especially important with display or sound device issues, as it helps to identify the devices and their drivers easily.

 

You can find a more in-detail description (and tutorial) by relliK here.
 
How to obtain your DxDiag Log:
 
Obtaining the DxDiag Log is fast and easy. Just perform the following steps:
 

1. Press 'Windows Key + R' to open Microsoft's Run function

 

2. Type in 'dxdiag' in the input field and click 'OK'

 

 

3. The DxDiag Diagnostic Tool opens in a new window. Wait for it to gather the necessary information.

 

 

4. When you are running a 32-bit (x86) version of Windows, click on "Save All Information..." and specify a directory and name to save the file.

 

5. When you are running a 64-bit (x64) version of Windows, first click on Run 64-bit DxDiag, then click on "Save All Information..." and specify a directory and name to save the file.

 

6. Attach the DxDiag Log to your bug report