Smin1080p

Ground Forces Armour, 3D and Damage Model Issues - IMPORTANT, read BEFORE posting!

How to post Ground Forces Armour, 3D Visual and Damage Model Issues 

All issues pertaining the incorrect performance data of vehicles

 

Whenever you perceive the data used for one of the vehicles in-game as historically incorrect, please use the guidelines below. This includes incorrect performance, Armour ratings, 3D model as well as armaments and other missing or surplus features.

 

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.

 

Please 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.

 

Important!

Please be aware, for claims about historical inaccuracies with vehicles in-game, it is required that at least one historically valid document is provided supporting any and all claims, if the source is not either a manufacturing document, a pilot or crew manual or any factory sourced documentation then at least two unrelated publications will be required as reference (this may be rescinded depending on the availability or reliability of the source).

 

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.

Also, add the current client version in brackets in front of your post, e.g: "[1.37.45.25]  <Issue>"

 

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 and if you are able to reproduce it.
  2. A detailed description of the issue you have or what you see as being erroneous regarding its representation in-game.
  3. A detailed description of the fix you suggest. Provide sources including reference that underline your position. This is up to the discretion of the Technical Moderator handling the report, however the number of sources required depends on the type of source presented:


OEM Manuals    -  User Manuals / Repair Manuals / Factory Manuals etc (Flight/Pilot/Maintenance Manuals, Engineering Drawings etc) - Historically acknowledged reference sources - single source is required. (Preferred)
Authored works   -  Reference Books on collections of vehicles/aircraft/ships ('coffee table books') Biographies, Specialist Books, "Expert" opinion publications, websites, industry magazines etc - at least two unrelated sources required.*

 

*Please be reminded that Wikipedia or other private Websites are generally not considered as reliable sources.

 

  • Please ensure the references haveReport/Document Type, Report/Document Name, Author, Date, ISBN/ISSN, relevant Pg No's etc - so our Historical consultant can review and check the accuracy of those documents against the substantial Gaijin Historical Database and Reference Sources.
  • Please provide scans of all pages referenced and a scan of the front cover of publication/book.  
  • For Web sources. Please provide the link to the actual relevant section or document.  If this is not possible and only higher links can be referenced then please provide page or title information to locate the relevant reference.
  • Photographs need to be fully referenced.

 

For Performance, Penetration or 3D model issues to better help us resolve these; Please also include the following:

       5.  Please attach screenshot(s) showing the issue, as well as the client replay file and the server Replay.

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

       7.  Attach your system's current Dxdiag Log.

       8.  If possible, link a short video showcasing the issue.  If the issue is interface related - please include video or screenshots of the interface issue.

 

Please Note:  Reports that contain/use ONLY the Protection Analysis tool screenshots as the evidence of an issue will NOT be Approved.  Please ensure that any report has an in-game (Test Drive, Custom, Tournament, Event, Random game) example of the issue as well.  

 

Thank you for your assistance in making our great game better.

 

  • Like 3
  • Thanks 1
  • Upvote 2

Share this post


Link to post
Share on other sites

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

 

VQYcm8R.jpg

 

 

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

 

JywN7VV.jpg

 

DOWNLOAD FROM STEAM

 

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

 

 

s8eKdWM.jpg

 

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

JywN7VV.jpg

  • Like 1
  • Thanks 1

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.

  • Recently Browsing   0 members

    No registered users viewing this page.