War Thunder Dev Tracker

In this case, something from the manufacturers would likely be treated the same as it was with L/55 and DM53. So BAe/Royal Ordinance/RARDE yes. But again, two things to remember:

1) Its needs to be an exact figure listed. Not any kind of calculated answer based on other data.

2) Developers still have the final call on everything. Its not down to me or any Technical Moderator to decide what's "good enough" other than what we have been told by development. Thus far, we have simply been told a source with a direct MV value is required.

A value is given, in conjunction with the other sources that was provided were sufficient for DM53.

Once again, we are going around in circles here.

We have passed on the info we have from the developers. There is nothing more we can do unless a better source is provided for CR2.

Ultimately everything comes down to the developers discretion.

As I have said multiple times now. Any "determined" / calculated / estimated or whatever way you want to call it wont be accepted.

We need a source with a clearly defined MV. I dont know how clearer to put that.

Im sorry to hear about the failings of your car, but we are talking about tanks here and facts posted by the manufacturer are considered primary sources.

We corrected DM53s MV based on several sources but ultimately because a clear MV is given by Rheinmetall (the manufacture of the gun) themselves.

If you believe they are still not correct, please submit a bug report with your replays here. Its getting confusing now as just yesterday you said:

Internal tests showed this resolved the matter, so if this is something new again, then it needs to be reported please.

Developers ultimately have the final call on what is used to create things in game. Flight model developers are not tank weaponry developers. The two are entirely separate.

We are avoiding the point here. You can call it whatever you want. The point is, a source with a clear MV is needed to resolve this matter.

There is indeed no argument to be had here. We cannot change what the developers will accept. We are just here to pass the info on.

Regardless of whatever you want to call it, it does not change the fact the developers wont accept a calculated / estimated / concluded / guess MV. We need an exact source that quotes it, like the one above with L/55 and DM53 otherwise it will just get rejected by the developers.

See above.

There was nothing misunderstood. But the developers have closed the report based on the fact no clear muzzle velocity is stated in the report. I have shown an example above from Rheinmetall on the L/55 and DM53. Thats whats needed here.

Once again, we have not accepted a source displayed penetration as an issue for over a year now. It has to conform to the new method: https://warthunder.com/en/news/6010-development-improved-calculation-of-armour-penetration-in-the-game-en

There is nothing further we can do with this matter unless a source that provides the muzzle velocity is provided. Arguing the point that you disagree with it isn't going to do anything.

Thats exactly the point. The devs wont accept an estimation of muzzle velocity. It needs to be a source that defines it, such as Rheinmetall have done with DM53 on the L/55.

Ja wiem, że śmieszki i w ogóle ale nie wrzucajcie proszę screenów z przekleństwami. Skoro umiecie zedytować na tyle, żeby wrzucić je tutaj pocięte, to zasłońcie też przekleństwa.

Jechałem kilka lat na 21:9 (2560x1080) i z chęcią bym przy tych proporcjach pozostał, ale jak brałem nowy monitor, to na rynku nie było nic ciekawego z 3440×1440 i 144Hz (w rozsądnej cenie), więc przesiadłem się na 2560x1440 w 144Hz.

Żałować nie żałuję, ale trochę brakuje tych dodatkowych boków, szczególnie w WT, gdzie wyglądało to super.

Co masz za grafę? Bo 16:9 1440p to jednak dużo więcej pikseli, niż 21:9 w 1080p.

Mimo wszystko, jeśli teraz używasz 32', to przesiadka na coś mniejszego będzie pewnie bolesna. Bierz też pod uwagę, że większość ludzi częściej zmienia GPU niż monitor, więc zakup czegoś, czego Twoje GPU teraz nie pociągnie w pełni, za rok-dwa może Ci oszczędzić wydatków.

Not much can be done here, sorry guys

For PC
Minimum:

OS: Windows Vista/7/8/10


Processor: Dual-Core 2.2 GHz


Memory: 4GB (Windows Vista/7/8/10)



Video Card: DirectX 10.1 level video card: Intel HD Graphics 5100 / AMD Radeon 77XX / NVIDIA GeForce GTX 660 (The minimum supported resolution for the game is 720p)


Network: Broadband Internet connection


Hard Drive: 17 GB

System Requirements
For PC

Minimum:

OS: Windows Vista/7/8/10


Processor: Dual-Core 2.2 GHz


Memory: 4GB (Windows Vista/7/8/10)


Video Card: DirectX 10.1 level video card: Intel HD Graphics 5100 / AMD Radeon 77XX / NVIDIA GeForce GTX 660 (The minimum supported resolution for the game is 720p)


Network: Broadband Internet connection


Hard Drive: 17 GB

Unfortunately there has to be a standard followed and this is that. In the case of the Leopard 2A6, the muzzle velocity for DM53 is displayed publicly on Rheinmetalls website. The devs do not want to start bending the rules because it creates even more opportunities that people will then expect.

If a source cant be provided, then it wont be changed.

We dont calculate penetration that way and have not for over a year: https://warthunder.com/en/news/6010-development-improved-calculation-of-armour-penetration-in-the-game-en

This is correct. But we also have no need for an all aspect missile like R-60M even in a more balanced state right now as since the fixes, R-60 is working perfectly fine. Coupled with an excellent platform like the MiG-21Bis, balance is actually very close right now vs the F-4E family.

This has nothing to do with FMs.

We are talking specifically here about shell / penetration / performance and armour.

Again, we don't calculate penetration that way (as in a source specifically states penetration). I was talking about the Muzzle velocity matter which is what we are discussing here for CR2.

We have already discussed this with the developers and its not a matter open for debate. The developers ultimately have the final call on things.

I have provided you with an answer already. Only sources with a defined value will be accepted. So unless a source explicitly provides the value on what is trying to be changed, it wont be accepted.

It is not for me or the Tech Mods to decide what is an acceptable source. In the end, we must only adapt the system we have to suit what the developers accept as a valid source.

As I have explained, in the case of the Leopard 2A6 and DM53 for example a clear MV value was provided and this is what's acceptable. The developers wont lower that standard.

It was the case previously, but it no longer is the case now. Unless a source with a clear cut number for whatever is being reported is provided, we cannot accept it since it will just get rejected by the developers.