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.
Hi
If you think there is a bug with specific machine, please submit bug report in Technical Section.
Hi!
You meets minimum system requirements?
For MAC
Minimum:
OS: Catalina v.10.15 or newer
Processor: Core i5 (Intel Xeon is not supported)
Memory: 6 GB
Video Card: Intel Iris Pro 5200 (Mac), or analog from AMD/Nvidia for Mac (Minimum supported resolution for the game is 720p) with Metal support.
Network: Broadband Internet connection
Hard Drive: 17 GB
Hi
We do not send confirmation, but if you fill all 3 steps listed here, you can be sure we get and saw your video:
STEP 1. Record and put together a video a maximum of 3 minutes length. ATTENTION: The submitted video must be made by you, must be published for the first time, visible and must not violate any copyright laws.
STEP 2. Subscribe to our Youtube channel at: https://www.youtube.com/warthunder.
STEP 3. Upload your video to Youtube and send us a direct link to [email protected]
Be sure to send link to your youtube channel, not file with replay.
Please be sure to check system requirements here: System requirements
Then (from support page)
Error 81110010: Device removed.
This is a troublesome error that is not confined to this game or specific hardware. It is a DirectX error code that indicates a crashing of the driver. Please try these steps to solve the issue:
Turn on vsync
Perform a clean boot before attemting to play the game
Ensure you have power supply capable of meeting the demands of your hardware while it is under heavy gaming load
Perform a clean video driver installation. You can find the latest drivers for nVidia here, and for ATI here.
Set all in game graphics settings to low in order to reduce the stress on your GPU.
Ensure you have hard drive space available for your pagefile. If your pagefile is set to 8GB an...
The bottom line here is the developers wont accept an estimation of the MV. We have had this in so many cases before the subject being reported was only done with estimates included and thus they were rejected based on that.
We will be changing the guidelines for historical reports to now reflect that only sources with a clear cut value of whatever is trying to be reported will be accepted. Since anything less will simply be rejected by the developers. So forwarding on guestimates and estimations is really irrelevant.
Path Length is not equal to a direct penetration figure. We also dont calculate shells in this way: https://warthunder.com/en/news/6010-development-improved-calculation-of-armour-penetration-in-the-game-en
This matter was previously forwarded to the developers.
Missiles in game are created based on a mixture of source material, closely tied to factual data and also developer discretion or balancing choices.
16G is the current overload is based on a combination of sources and the developers decision currently.
We had a response on the developers regarding this source.
The developers require a source in which the initial speed is indicated for as was the case with the Leopard 2A6 and DM53 as this was displayed on the Rheinmetall Website. Thus its possible to get accurate information.
Any conclusions from the above source are only subjective. A source with the specified initial velocity is required. Indirectly cited sources are not considered sufficient by the developers.
This is because if they consider this instance and act only on a rough calculation, It will create a precedent for subsequent similar cases.
Please do not make such false accusations. No law is being broken whatsoever.
You agreed to a legally binding ELUA. Nothing in that was broken on our side.
You were not promised the Harrier would stay at 9.3. You were not promised that its BR would not change.
All vehicles are subject to BR changes at any time, that has always been the case and always will.
They have literally just been moved up. Once we have seen the data from how they do here, then we can decide if it even needs to go up again.
devtrackers.gg
