There's a big problem with the way Gaijin introduces new features

Should Gaijin expand features in a timely manner resolving bug reports quickly rather than leaving it unresolved for months and years on end?

  • Yes
  • No
0 voters

There’s a big problem with the way that Gaijin introduces new features. Often times Gaijin introduces a new feature into a major patch that is often first found on certain vehicles and not on other vehicles. This then leads to users reporting the missing feature or mechanic for their favorite tech tree/vehicles.

The issue? These bug reports sit for months and years on end as accepted without anything being resolved as a result of these reports, leading to players having to play against vehicles that use these features knowing that their own vehicle of choice does not have said new features.

There’s three recent features that could be examined:

  • Spall liner being introduced into the game on the T-90M, but vehicles reported for spall liners being under investigation for years still.

Leopard C2A1 MEXAS missing spall liner // Gaijin.net // Issues
KF41 Lack Spall liner // Gaijin.net // Issues
Puma IFVs missing Spall Liners // Gaijin.net // Issues

  • Internal ESM being introduced onto top-tier Chinese and Russian vehicles such as Su-30SM2, J-15T, and etc but remaining under investigation for several months still on other aircraft.

Tornado IDS SLE Missing build in ELS/ESM // Gaijin.net // Issues
JAS-39E missing ESM functionality // Gaijin.net // Issues

  • Fuel tanks being added as a feature which stops being expanded for existing vehicles for nearly a year, while new vehicles continue to get this feature.

So there’s a disparity in treatment regarding vehicles that gets these features upon the feature’s introduction versus vehicles that later on get reported and accepted. It leaves a frustrating situation for players when newly introduced features do not get expanded to more vehicles in a timely manner. If you guys have any other examples you could point to, that would be appreciated.

29 Likes

Features should be brought to the game with an established default set of parameters (which are shared with the playerbase) to platforms that are known to have the features. This allows for greater refinement over longer periods whilst not neglecting the presence of a system/feature for the same stretch of time. It should only be required to establish a baseline “it exists” to then begin the process of refinement.

This might upset some folk if discovered parameters require dropping values from default values, but it’s still a sight better than what we have. It should also be acted on pretty immediately to add these default depictions of features to vehicles as their presence is learned/reported.

3 Likes

I think there is a big part you’re missing from this topic is the fact that their is massive backlog when it comes to Bug reports and with the newer tanks and aircraft there is some reports that are based on what people think it should be than what it actual is which doesn’t help things, not evening including where there is real documents to go off but due to the fact these tank’s and aircraft are newer a lot of documents are hard to get hold of and harder yet if they’re safe to use etc.

6 Likes

This is a very real thing yes, and luckily we have technical moderators as well as bug-reporting managers that help filter appropriate reports for developers. I should clarify in my post that I meant accepted reports meaning that the reports’ sources have been considered valid enough to be forwarded to developers.

11 Likes

Features are added just to create hype for a specific update then forgotten

16 Likes

I fear features could come with vehicle additions as a way to create hype as you said, since there’s monetization possibilities behind vehicle additions but there’s nothing much to be monetized by adding features/mechanics to older vehicles unfortunately.

2 Likes

Spall liners were a great example
They came alongside a very mediocre tank (T-90M) to generate hype about it, despite it being functionally inferior to the BVM which has already been in the game for so many years

And it worked

2 Likes

Is the backlog so large that they can’t action my 8 year old reports? These were accepted on the old forum, and redone then accepted again on the new site even these are years old.

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

The MIM-72E and MIM-72G are still bugged after two years, the missile being smokeless is a big benefit for the vehicle’s efficiency and the fact it’s currently produces as much smoke as an ICBM makes the Chaparral much worse than it should be.

3 Likes

Feel free to drop the links to the reports if you’d like.

this report got fixed 4 years after being accepted

1 Like

now if only the J 32B could recieve the A 32A’s attack rockets, like it was able to carry in real life.

https://community.gaijin.net/issues/p/warthunder/i/PW8tAm7AKXr7

Accepted 2 years ago.

1 Like

then there is also the issue that the J 34 STILL has not been fixed since it was released.

https://community.gaijin.net/issues/p/warthunder/i/r1D5eI9F6qdl

1 Like

Even if someone else is the owner, would that solve the problem if the developers are still more intimately familiar with Russian equipment and vehicles?

I think it’s just a case of multiple factors playing a part:

  • A good portion of the developers being more knowledgeable on Russian vehicles/equipment than non-Russian ones.

  • Prioritizing features on new vehicles to provide selling points.

  • Little to no incentive to backfill features on older content that can’t be marketed effectively.

1 Like

The problem here is that Gaijin probably doesn’t have a team dedicated to historical inaccuracies, thing that is really needed when you have such a number of vehicles that you have ingame and features that are introduced retroactively.
The state of the game gets worse patch after patch due to vehicles left to rot.
I get that the economy model of the game is based on the FOMO of the latest addition but there are reports that are really old and still quite decisive.
ex.
The Leopard 2A7HU still suffers from a bug that compromises it’s armor, this same bug was already fixed years ago on the 2A7V.
https://community.gaijin.net/issues/p/warthunder/i/wpUGIu5Hk23Q
We have an M47 that’s not even the italian one:
https://forum.warthunder.com/t/italian-m47-105-55-actually-an-israeli-m47-how-to-fix-it/
Mind you that I’ve personally reported it on the older forums so many years ago.

These are only few examples, the point is that the more we go forward, more are present in the infinite backlog.
Either Gaijin devs pause new content(not happening due to the economic model) or they create a team dedicated to ironing out bugs 24/7, maybe starting from those in the old forums.

3 Likes

(the AESA typhoons can’t even carry SPICE 250s, only the Tranche 5 modification can. The Tranche variants we have ingame are 2, 3 and 4.)

1 Like

The AESA Typhoon was an attempt to give EU nations an AESA radar equipped Typhoon.
In reality no one has one in service and only protos exist so we ended up with a “fantasy” one.
I hope they revisit them once each nation puts one in service.
The Spice was just an attempt to give them a chance to compete with russian CAS ig.
I wouldn’t mind going the more sensible route and switch the Spice with the HOSBO for the time being.

Anything but giving Brimstones mmw 🫩