A Players Guide to Bug Reporting for War Thunder

[Jadenbetter-live]

Curious, I might ask big smin or something on it

[Caernarvon02]

@MatrixRupture

This post was flagged by the community and is temporarily hidden.

im not saying anything but that says enough

[Master_Teaz]

yippee reopened

[Nostalgistic]

Oh good. I’m glad this thread is still alive. It will be very useful to review once in a while.

[FlyingOstridge]

This post was flagged by the community and is temporarily hidden.

[Master_Teaz]

nice try mate,

We all know what a real flagged message looks like

[FlyingOstridge]

This post was NOT flagged by the community and is NOT temporarily hidden.

[Caernarvon02]

back to sharing tips on how to work around the awkward brick wall the CBR system can be. gonna keep quiet so i also dont get a “This post was flagged by the community and is temporarily hidden.” again…

Using the file name of the vehicle in the report can stop the devs and mods screwing up which vehicle you mean, its found at the end of the URL on the vehicles wiki page

[FlyingOstridge]

uk_fv4005 implies something the WT community isn’t ready for

[Caernarvon02]

functional HESH or that a minor nation should be allowed to be on par with the whale nations?

[Master_Teaz]

armour scabbing and spall ricochet when

[Caernarvon02]

correct amount of armour defeated too. the L7 105mm hesh is currently behaving like a 76mm hesh from saladin, a shell with less a third of the explosive filler

[Jadenbetter-live]

yes that was included in the very first draft

[Caernarvon02]

i forgor in the time between reading it and the thread being taken down

[Nostalgistic]

@Jadenbetter-live

Aircraft specific rules:

Reminder, making bug reports to correct aircraft’s flight model, such as weight and fuel mass, is not allowed as of now, according to Gunjob and Smin’s official responses in this thread.

MB 326 K Engine

Part of the new feature we announced in the last CM Update was to expand upon the information shown in game. This begins with things like tank shell performance:

Spoiler

[image]

However as we mentioned, we plan to expand this potentially to many other aspects of the game such as elements suggested previously. Subject to change of course. But with the goal of as much information as possible being displayed within the game itself.

@magazine2

We’ll start with the easiest to implement, and then gradually add similar features for other areas. First up will be more detailed data on armor penetration and shell ballistics. Next, we’ll likely try to implement useful information on the properties of guided missiles and aircraft flight models. However, this will take quite some time as we work on designing and implementing a mechanism (as mentioned above), so please don’t expect it in the near future.

However, the developers have mentioned that they are working on creating a future user interface that would display detailed aircraft flight model data. When it’s implemented, this would allow us to submit more FM bug reports.

[Jadenbetter-live]

Didnt know they had said this, will add it now as i had removed it for this version bc i couldnt fit it in

[kleinerPanzer]

Some addenda from my experiences

I know in the past the distinction between “Historical reports” (for technical data about vehicles) and “Bug reports” (technical problems with the game’s code/performance) has been made, although that seems to have been lost in the transition to the CBR site. This list of tips is definitely for ‘historical reports’, though, and not ‘bug reports’.

When reporting errors in a vehicle model, ensure that each error is itemized and well-documented with your photo evidence. Generally, the source of the photos is also required, although I’ve had mixed experiences on whether they need to be from published materials (e.g. books, manuals) or can be sourced from anywhere (i.e. the internet).

[Jadenbetter-live]

I have mentioned stuff for both but there are by far more rules for historical than actual bugs