Another Dev Server, Another Sweeden Bug/Request

[Cewch]

Hey everyone,

I’ve submitted a bug report / feature request asking Gaijin to finally add automatic target tracking (ATT) for air targets to the CV9040 BILL, CV9030 Mk.4, and CV90120.

If you’ve played these vehicles, you already know how frustrating it is that they can’t track helicopters or aircraft — despite being equipped with the Saab UTAAS (Universal Tank and Anti-Aircraft Sight), which was literally designed for engaging aerial targets.

Meanwhile, other modern MBTs and vehicles like the T-72B3, T-80BVM, T-90M, VT4, Type 10, Leclercs, and Merkava Mk.4s have all already received automatic air target tracking in recent updates.
There’s no reason the CV90 family — with its real-world dual-purpose FCS — should be left behind.

This isn’t about buffing; it’s about realism, consistency, and fair implementation.
Gaijin already models ATT across a wide range of vehicles with modern fire control systems — the CV90 series deserves the same attention.

✅ How you can help:

1. View and upvote the bug report: Community Bug Reporting System
2. Leave a comment if you have any credible info, manuals, or sources about the UTAAS system or CV90 variants — it strengthens the case.
3. Share this post with other players, especially those who play Swedish or export CV90 variants.

The more visibility and community backing this gets, the higher the chance it’s reviewed and fixed in a future update.

Summary of what’s being requested:

• Enable Automatic Target Tracking (Air) for:
  • CV9040 BILL
  • CV9030 Mk.4
  • CV90120
• These vehicles use the Saab UTAAS system, which supports anti-air engagement and automatic tracking.
• Aligns with similar updates already applied to many other modern MBTs.

[AlvisWisla]

Strf 9040s don’t use IR tracking systems.
Strf 9040s use a different system that is not a feature in War Thunder at all at this time.

UTAAS sight is not the FCS + sight combination.

So the evidence required is FCS, since everyone knows the sight is capable.

[Fluffy_Bucketles]

Devs have already told us to go rot, at this point just give up on getting them to implement novel fire control functionality that they can’t sell for an arm and a leg.

[Apollo_1641]

They closed it

[Fluffy_Bucketles]

And no one is surprised.

[AspectOfTheRAGE]

CV90’s, specifically UTAAS do not feature actual tracking capabilites, they have something called inertial ““tracking””, which is not identical to actual tracking of via an algorithm that locks onto a contrast in the UV/IR-field. IRST =/= inertial ““tracking””/inertial-lead-calculation

[Vitamin_B12]

Has anyone noticed that the STB of STRF 9040 BILL fails when the speed exceeds 30KM/H? Is it a bug or is it supposed to be like that?

[Apollo_1641]

I’ve never understood what makes the UTAAS “track” different from a so called “real” track, and why Gaijin won’t simply give IRST tracking as a half measure until they can model this properly.

Say if there is a aircraft flying in perpendicular direction, does the gunner have to manally track/hold the sight on the target and then the gun applies lead automatically? If so, why not just give a lead indicator but without the automatic sight following.

[Necronomica]

I’ve posted some TLDR explanations previously:

@Necronomica

This is a laser distance, rotational-speed and trigonometry based tracking, not IR or Video.
The gunner basically lases the distance once, tracks target manually and then lase distance again and then the computer calculates the speed and direction of the object based on distance and turret turn-speed to continuously adjust the aim as if the object is continuing on the same trajectory. If the target turns or changes speed the “tracking” will be off and the shots will miss (if solid shot, proxy will still likely hit depending on circumstances).

@Necronomica

UTAAS is also modular, not all UTAAS are the same or have the same functions, so my previous statement still stands, all CV90’s need all the functions proven per model.

Edit:
Additional info found (https://ndia.dtic.mil/wp-content/uploads/2012/armaments/Wednesday14132odell.pdf )
So the Video tracking module is a separate thing from the UTAAS and that is the part we need evidence for being integrated into every specific CV 90 that has it IRL.

Images

@Necronomica

Yeah, exactly that, so a primitive way of describing it is that the turret traverse and the elevation mechanism then just gets put in “cruise control” where they just keep turning and elevating at that same speed as between the measurements. There is even a mode that works the other way around, if the DV90 drives and the target is still and lases twice the gun keeps aiming at that spot in 3D-space and since the target is still it doesn’t matter if the CV90 driver changes direction or speeds up or slows down because all that info is feed to the fire control system ^^ The system just doesn’t have a way to send that information to the fire control system if the target changes position (without lasing again). Though i think (unconfirmed) that the newer versions have a “pulse” mode that lases distance once every 0.X Seconds to achieve the same function as if it was a optical track (downside being that you are sending out a laser and thus can be detected in contrast to an optical system).

[Apollo_1641]

Aight, I see.

So for basic/early UTAAS the devs could just use the existing track/lead feature but make it not update.

You get one non-updating lead/track vector for each time you lock on.

However, what keeps a user from simply re-lasing the aircraft periodically to update the vector? And how quickly could you do this?

And for later models like you said there is apparently a built in pulse feature for that specific purpose. At that point we’re basically talking about the in-game track-lead system so why not add it.

[Necronomica]

@Apollo_1641

So for basic/early UTAAS the devs could just use the existing track/lead feature but make it not update.

Probably yes, with some tweaks as the current in-game version locks the vehicle even when you’re aiming to the side of the vehicle. the UTAAS has to be on target for it to work (so technically IRL it can lock any point regardless of if it’s a vehicle or not).

@Apollo_1641

However, what keeps a user from simply re-lasing the aircraft periodically to update the vector?

Nothing really, just the fact that they have to hit the vehicle with the lase, if the lase misses then the UTAAS will track whatever is behind the vehicle (or for air not at all).

@Apollo_1641

And how quickly could you do this?

Probably as quickly as the lase takes to perform and calculate, IRL i’m guessing has some sort of small time limit to avoid sending overwhelming amounts of data to the FCS and crashing it or bugging it out, but that is just a guess from my side.

@Apollo_1641

And for later models like you said there is apparently a built in pulse feature for that specific purpose. At that point we’re basically talking about the in-game track-lead system so why not add it.

Yup, the issue with this last part is evidence of it, i’ve only seen people claiming they operate the vehicle and say that it exists. I have not seen any other mention of such a function anywhere else.