Aero cover remains on the missile until a predetermined range (not the seeker max range) to improve aerodynamics and down range performance
Aero cover remains on missile until the primary radar loses or is about to lose the lock (ie: datalink as far as possible for maximum aerodynamic performance
Aero cover is jettisoned as max seeker range but datalink is maintained until target lost or missile impact (max guidance strength, the target would effectively be trying to defeat a IIR/ARH dual-mode seeker)
We have to remember that the IRIS-T SLM is stated to have 40km effective range irl. Assuming that to be the case, a 25km lock (stated range limit of the air launched IRIS-T, and therefore what im using as the estimate for the seekers max lock range) is well after the missile has stopped burning, and only occurs once the missile has climbed into thinner air where the drag would be highest
Sounds like the TRML-4D is too susceptible to chaff, and the IRIS-T remains too susceptible to flares :/
holy AoA on this thing is wild Maybe that’s the whole issue maybe they don’t want the missile spinning out if it hits 40G instantly That would explain why it can pull AoA but doesn’t seem to pull the G it should
Another certified War Thunder classic that seems to happen to the SLM is the track moving to any munitions dropped by the targeted aircraft. It’s something that also happens to the Pantsir, and seems to be a downside of TWS type track radars in War Thunder.
That also looks like a consequence from the hardcoded “vertical-to-horizontal-to-loft/target approach”. After reaching horizontal flight it tries to correct its flight path which wasn’t correct to begin with by all means nessecary.
The wing area multiplier being dropped is an odd decision from gaijin, and at least for the baseline IRIS-T, its fin AOA is much too low, so its not a stretch to imagine the SLM is in the same boat.
Baseline IRIS-T fin AOA is limited to 25.68deg in-game vs 38deg irl, roughly 67.6% of its IRL capabilities. This has been bug reported: Community Bug Reporting System
I also have a sneaking suspicion the fin distance from the center of mass might be wrong. Currently, distFromCmToStab is set to 0.2 (I assume meters?). This makes little sense, as the warhead, seeker, electronics, etc… are all located in the front of the missile, which should theoretically skew the weight towards the front, but even ignoring this bit of logic and assuming the CM is at the geometric center of the missile, the distance of the force vector imparted by the fins should be roughly 1.7m, which would give the fins significantly more leverage to act on the missile.
I made a report on the radar update rate, this is similar to another report that got passed as suggestion, this should serve as additional material to implement the needed radar mechanics for a <1s update rate
Gonna post this response here too but I just looked into the code and the TRML-4D isnt being treated like an ESA in-game. Its missing the blob of code that defines ESA’s in WT.
This is the one taken from the Rafales RBE2-AA:
What it does is it runs an invisible scan in the background of ur regular scanning that updates all targets within the electronic scan limits of the radar at a super high speed. So for the Rafale, it does it every 0.04s. Its why they have much more stable locks and its how they’re able to track targets outside their current search volume. The TRML-4D is completely missing this.
Depends on their speed and alt and range and all that. IIR should be able to pick up a target although I would be skeptical of it picking up a fast target that has low heat signature.
Unless you meant I should make a seperate report that specifies its missing the ESA functions entirely in-game? Cuz though its correct to say the update rate is too high rn, its kind of missing the crux of the issue, which is that its supposed to be an AESA radar, but is currently modelled as a pure mech scan radar…
i can give you good answer because im not an expert on this but it has pov of 0.25 should lock on after DL give it information and guide it all way via radar"
It only scans a 110 deg arc centered on the radars current direction. Should work in both modes though.
Its not something you select in-game, its basically a background process. Its why so few people seem to understand how to properly use the Rafales radar for example, because unless you know what its doing and how it works, there’s literally no real visual indicators its doing anything.
To explain the Type 81’s, what its doing is scanning 28 2.5deg bars that are 110deg wide, centered on the current radars centerpoint, and it does it every 0.04sec. Everything it passes over in that scan that already has a trackfile has their trackfile updated.
This is why the update rate and lock stability is incredibly high on ESA’s in-game, and its why it can continue to track targets that have left the current scan zone (the scan zone being what you see/define, its the area where you can pick up new targets).
Its basically gaijins form of the radar assigning individual beams to update multiple targets simultaneously.
