The atgm behavior is bugged as hell, i made a bug report months ago but got no response. If fixed it would be pretty good afv imo (and no the cannon feeds from 24 round magazine that is manually fed, like all other cv9040 variants) Community Bug Reporting System
Yeah the ATGM is pretty weird and last time i played it still felt relatively bugged soo perhaps they haven’t fixed the problem yet. Tho for the main gun i alway’s thought it was supposed to be belt FED, but i guess not.
That’s not a bug, the launcher doesn’t have elevation control
2 Likes
The missile launcher doesn’t have elevation control because it doesn’t need it, like the LOSAT the missile should follow where the gunner is pointing immediately after launch, but it only does this if the aim point is right next to where the launcher is pointing, which makes no sense, the atgm guidance has nothing to do with where the launcher is pointing (many atgms work that way already in the game, like the already mentioned LOSAT, swingfire and others)
Its a SACLOS atgm, it has to be physically seen by the launcher optics so its position can be tracked by the IR flare/beacon on its tail. If its outside the sight FOV, the launcher has no idea where it is and what commands to upload via the wire.
Stuff like the Swingfire uses a custom SACLOS control loop to steer the missile down into the sight FOV before guidance can start.
Losing guidance outside the FOV isn’t a bug. You’d have to find evidence to prove that the BILL has a custom control loop like the Swingfire, but a more complex one since it can be above or below the sight FOV when fired.
1 Like
You said it yourself, the launcher OPTICS need to see the missile, not the fixed metallic box that holds the missile. In game the optic needs to be very closely aligned with the launcher, not the actual atgm optic that has 38 degrees of fov, much larger than other SACLOS atgm vehicles that can launch much outside of their launcher traverse limits like the Rakjpz 2, HOT and Shturm etc.
The launcher optics is either the gunner or commander sight.
If you’re on a backwards slope, the optics are pointing forward at the target, but the missile is launching upwards, outside the sight FOV.
1 Like
Then how do other SACLOS atgm vehicles, with much lower fov optics (other than the swingfire)manage to guide the missile just fine at those slopes? i submitted a bunch of test videos with the bug report, you can go in the test drive and see it for yourself
Those are hidden in the bug report
This issue contains information visible only to the author and employees
1 Like
Yeah i know i just meant that i tested it a lot and the BILL behavior is clearly not consistent and clearly bugged
Its not a bug.
For an extreme example, look at the BMP-2M. The sight has such a high max elevation compared to the launchers, so the missiles can’t be guided above a certain elevation angle.
1 Like
How is that relevant to what we are talking about? Again, on the BILL, a SACLOS missile, a slight slop makes the missile refuse to guide towards the aim point, while other SACLOS vehicles, with much worse optics, can pick the missile up just fine, launcher elevation has nothing to do with any of this. This is cleanly a bug, i dont know what you are trying to argue here?
The BILL is just the most noticeable because the launcher can’t be elevated.
You can also recreate tracking loss in other vehicles like the Shturm by launching and quickly moving the sight to the side away from the missile. The missile loses tracking when its outside the FOV.
1 Like
Its not “the most noticeable” it is clearly wrong because the missile is clearly visible in the sight yet it doesn’t react, while no other SACLOS atgm acts this way, no other SACLOS atgm needs to align with the LAUNCHER not the SIGHT. you lost tracking on the Shturm because you moved the sight and lost the atgm, that is how it should work on all SACLOS atgms yet it doesn’t work like that on the BILL. Again, it’s clearly inconsistent with literally every other SACLOS atgm vehicle and is clearly bugged.
Its working fine for me on the BILL. I can get guidance from a bit outside the sight FOV, same as every other one.
I’m pretty sure War Thunder uses a slightly bigger FOV for missile tracking than the sight FOV. Probably because an IR flare/beacon has enough glare in an IR sensor to track a bit outside that.
1 Like
At this angle for example, it launches completely outside the visible sight but guides back into it.
Too much extra angle and it can’t.
1 Like
Have you even looked at the sight position and its fov??
and again i did ton of testing that i sent with the bug report, i wont bother with this anymore you clearly dont have a clue…
Don’t bother then, but its still not a bug
1 Like
It’s a very niche vehicle that probably doesn’t deserve the 10.3 br rating. Since you usually have to put yourself in harm’s way to make use of the launcher I’d rather take the extra pen of the C variant.
That is not the FOV of the commanders sight, it’s narrower than that. Additionally, the commanders sight is pointed in the same direction as the gunners sight automatically when in gunners sight (in game, not IRL). So the Commanders sight is going to be aiming down in that image. Not only that, the commander sight itself isn’t what needs to see the missile, it’s an IR seeker that is pointed in the same direction as the commander sight that might have a narrower view compared to the commanders sight.
The entire reason the CV9040/56 project was canceled as due to sightline issues leading to issues controlling the missile. (https://www.youtube.com/watch?v=T7JADkIB_Zw)
A tip for playing it in game is using the commanders sight and “commander aim mode” to guide the missile, just aim the commander sight up a bit so that the IR seeker sees the missile and then you can guide it back down and to the target.
2 Likes