nice try mate,
We all know what a real flagged message looks like
This post was NOT flagged by the community and is NOT temporarily hidden.
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
1 Like
uk_fv4005 implies something the WT community isn’t ready for
functional HESH or that a minor nation should be allowed to be on par with the whale nations?
1 Like
armour scabbing and spall ricochet when
2 Likes
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
yes that was included in the very first draft
2 Likes
i forgor in the time between reading it and the thread being taken down
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.
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.
1 Like
Didnt know they had said this, will add it now as i had removed it for this version bc i couldnt fit it in
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).
1 Like
I have mentioned stuff for both but there are by far more rules for historical than actual bugs
Quite a nice layout, agree with all points.
- 1
Oh don’t worry, found out what was going on with the AH-1G/Tzefa A/Tzefa B sight, reported it ( AH-1G/Tzefa A/Tzefa B pilot gun sight missing FFAR sight // Gaijin.net // Issues) and it got “If you believe that some of characteristics are wrong, you have to provide sources. We can’t accept report without them. All sources must be presented as source title, cover, and page with data.” and instantly locked… Or how I reported WITH ACTUAL PHOTOS on how the T72s commander’s cupola is modeled improperly ( T-72 series missing commander’s copula armor // Gaijin.net // Issues) and it just gets closed with “It’s not a bug”. I have a strong feeling the Bug Reporting Moderators don’t ACTUALLY care about our reports. Just like how I have had the Tzefa A hydraulic arm bug reported for over half a year, nada. Another person reports it yesterday and it is accepted day 1 (not even joking. That literally just happened and mine was a “duplicate”).
me who has been waiting for almost the entire Tech Manager team to respond to my message as I slowly added them over the past month and a half|
Can I get a response to that? I’ve had multiple bug reports blown off even though I’ve given literal tech manual sources with screenshots, unedited in game screenshots from the War Thunder screen shot file for others, etc and been told to effectively bugger off and now been banned from the report website twice because… reasons?
You were probably spamming the big report site…
probably?
theres 4 of the same report
apart from the first report, the other 3 have the same denial reason from the BRM
completely understandable why he’s been barred from further reports
2 Likes
Tbf, would help if they would stop closing it out with “not enough information” as I have the literal flight manual Cobra pilots used and closing it out instantly, it would probably help. Not my fault they keep closing them out.
The one that Master_Teaz included about the ADATS states “Unfortunately you have not included all necessary data. Without it, it is impossible to resolve the issue.
If you’ll encounter the issue again, please make a new report. The report should include description of the issue, steps to reproduce, unedited screenshots made by game, log and replay file. Screenshot should be made during the bug or immediately after it occurs”, which is funny because I included exactly that and the .clog file for said replay.
Not as if it isn’t literally the same sight but sighted for the rocket IAW the ballistic table (which is stated in the TM that I referenced in the reports) that’s literally right under the pilot’s reflex sight… Sorry that they don’t want to fix things unless it’s dealing with Russia.
EDIT (addition): Convenient you didn’t add where I state that the impact zeroing point would be changed upon that but it would have to either be predetermined (so the DEVs choose whatever the setting is and therefore what it looks like) or that it would auto adjust (which would vary on engagement parameters).
