Smin1080p

Unfortunately at this time, there is not really anything meaningful that we can actually share that isn't the finer technical details (that we cant share due to their sensitivity) of what the team have been doing around the clock to mitigate, stabilize and resolve the situation fully.

DDoS attacks, particularly ones of the size, scale and persistent nature we have been experiencing are complicated matters to combat and resolve.

We fully appreciate and understand the frustration and want to be clear that when there is a meaningful update to post, we will do so.

We haven't had a single blog yet. I'll let you come to conclusions on the the answer to that.

Regarding the event, it was prolonged as a result as we made clear would be the case:

The team are working as hard as possible to stabilize the situation for all other factors.

The news article detailing exactly what is happening is pinned to the front page of the website for this reason. Detailing also the steps we will take after the situation has fully stabilized.

As the situation has not fully stabilized, the article remains pinned and as mentioned, premium time compensation will be addressed once matters are fully concluded.

Unfortunately there is nothing further to really update with at this time, as it is an ongoing situation.

Its the correct article and the reason why it has been pinned to the front page of the wesbite.

Indeed, this has been a prolonged and ongoing DDoS that has been resolved but new attacks are generated afterwards. As we outlined in the article, steps have and are continuing to be taken and we will post any further updates when there is new news on the matter to share.

Server issues are one matter and when we have those, we are equally clear about server issues. DDoS is a separate matter that any game, no matter its size can succumb too: https://www.eurogamer.net/blizzard-says-overwatch-2-servers-experiencing-mass-ddos-attack

Hello

We have have a pinned news article on the website explaining the current reasoning behind the issues recently, caused by ongoing DDoS attacks:

https://warthunder.com/en/news/7887-ddos-attack-on-the-server-en

Our team are taking every step possible to resolve the situation and if the situation changes, we will provide further updates.

Premium accounts will be extended accordingly after things are stabalized fully:

We fully understand the frustration and are working hard to restore normality.

Thank you for your understanding in the meantime.

Forwarded to the developers for review.

Everyone always asks where dovblog, nobody asks how is dovblog

Hello

The German F-4F early / late never carried AIM-7 sparrows and don't have the capacity to do so. The F-4F was a lower cost variant of the E series specifically for Germany, with the capacity for AIM-7 removed.

We don't plan any in the immediate future as the current ones are more than adequate for gameplay. However as always, suggestions are welcome in the suggestion area.

Thank you all for your feedback.

We have now passed on all feedback for the devs to review

The changes were made based on the exact values the version in game used in its configuration:

The engine speed limit from the factory was introduced in November 1943, and the change of sight from binocular to monocular was at the same time, even a little later.

These features, coupled with others, allow us to identify from what period specifically our Panther is from and thus set its correct engine settings:

Visual Model

Reports that do not follow the template will not be accepted.

Follow the

yellow links for help articles in the knowledgebase.

Required files:

Screenshots taken using the in-game functionality

Sources that meet the requirements

Also did not follow the guidelines.

We are working through custom loadouts sequentially every update.

There's really nothing suspect about it. Nothing on this forum is ever "deleted".

If a report doesn't meet the requirements, it won't be approved. That's made clear when you make the topic, as you have to agree to have read and followed the guidelines in your topic. In the case of the 163 report, it didn't follow the guidelines.

As for Dev server reports, I have explained already here that once a Dev closes, the section is moved to storage. If you require reports to be moved, they can be done on request. I've done that with the Puma report in question.

If we have news to announce on a vehicle, we will make a blog about it when/if it comes to the game. Not announce it here.

There are lots of Jet aircraft from generations already in game that are not yet in game. We don't always add things when they are top of their tree or in the current meta. I'm sure many people would make the same argument for other aircraft too. Unfortunately they can't all come at once.

Feel free to make a suggestion topic, right now we dont have any news to share on this.

No news to share at this time.

AIM-9J was never used by the ASA. They were given to the G and S based on use on both of those aircraft in other European countries and for balance purposes as they were at the time the only top tiers of Italy.

The ASA now has AIM-9L, which is what it actually used. If you can find an example of an ASA using AIM-9J in service with another nation or tested with it, then it can be reported under historical reports and submitted for consideration.