Personal theory : the lack of dual plane maneuvering in game is probably what causes this
Aster 30 is advertised as ranging from 3km to 120km of range in game Aster can hit well under that short range limit. Also for the trajectory yeah its indeed weird how they made this since the missile booster has thrust vectoring and should be able to go directly in the direction of the target instead going up down right or left before actually moving.
Watching this video it seems like an IRL Aster makes more of a right angle turn when intercepting lower altitude threats. Currently the dev server Aster makes more of a giant loop and ends up coming top down on close targets in test drive.
Not sure what that is an indicator of or how/if it could be adjusted.
I have not had it hit my helicopter at low altitude. Y’know, where you’d expect it to miss. The same case for flying attackers against it. It is not as much a threat as you seem inclined to paint it.
Would be nice for SEAD armament to deal with it, but simultaneously, it isn’t the most threatening.
I had no idea if it was close to irl or a game limitation so you probably answered that!
I was not aware of that limit. I hope they wont add that limit, however it would be realistic so not really a complaint just a wish.
I also hope they add MiCA VL for shorter range, maybe as a second missile option later on, as the fact that mica vl use the same launcher platform
SAMP/T radar has a detection limit bug // Gaijin.net // Issues
SAMP/T Arabel radar has a 20km detection limit bug in-game even though files say it should detect aircrafts much further away, which is weird.
This limit was reported, so probably only a matter of time before it comes.
Aster 30 Incorrect Minimum Interception Range // Gaijin.net // Issues
But there’s a chance that this minimum range limit would make it perform better at longer ranges since it would likely result in a higher loft.
Heli maybe was flying at 120km/h, but it wasn’t flying straight at the missiles, further diminishing closure rate. ARH missile seekers in look-up scenarios (seeker points above horizon) should turn off doppler filter to continue tracking notching targets, which in turn makes them chaff vulnerable. However angle gating should kinda-sorta counteract that, acting basically like tracking suspension - missile switches to inertial when seeker sees more than one contact, resuming search (and track if found) after chaff leaves seeker view.
It seems weird that the SAM radar can track a target (heli) that a radar missile cannot track in the same situation, ignoring multipath and chaffing.
If only they could model the blade return
As if radar on the vehicle and radar on the missile aren’t made equal, with radar on the missiles universally having rather wide notch margin.
You could rewatch that particular replay and observe from missile PoV, what was closure rate of the heli. My somewhat educated guess would say notch window for, amusingly, both aviation and missile radars being 20m/s. Reason being: hovering Harrier AV-8B, with decent MPRF capable radar - AN/APG-65Q - switches out of PD to Pulse when tracking test flight Migs when closure rate, both negative and positive falls between -20m/s and +20m/s in look down scenarios. In the same scenario, TWS loses track when closure speed falls within -30m/s and +30m/s
In datamine for the radar, nested within “mprfTrack”>“dopplerSpeed” you have field “width=20”. For “mprfSearch”>“dopplerSpeed” on other hand you have value of “width=30”. Might be accident, might not, unless you grab Snail Dev and shake answers out of him we won’t really know.
All ARH missile seekers have identical “dopplerSpeed” group, with “width=20” present as well, though there’s also “refWidth=80”. How that one works, I have no idea. Now going back to the replay with Mi-28, sure as hell closure rate was not 80m/s, as that would require said heli to haul ass at 290km/h directly towards missile. Which leaves whether heli had closure rate of above or below 20m/s (72km/h) from missile PoV.
The screenshot i posted did show a heli flying in a diagonal way towards me, however, missiles still went for chaff on helos going straight towards me, faster than this one and also in the same altitude range
All missile, or rather, Doppler filter cares is closure speed relative to the ground
And 120km/h and flying diagonally, means likely wasn’t closing fast enough to maintain Doppler filter → it gets turned off → missile becomes chaff vulnerable.
is radar still limited to 20 km?
If only they could model the blade return
They could - they just don’t want to, as it would stop Russian helis from flying high and slow like they all do now
Meanwhile Buk with 25 meters proxy (suuure) and 45kg tnt will be able to kill or cripple all helis high or low with 1 missile :)
Once again the game mechanics and their ‘limitations’ are extremely convenient, pure coincidence of course
unsurprising considering the current context
SAMP/T finally gets a bit of recognition though, so that’s always nice
It was still tight and the signs were totally unclear, with for example the defense minister wanting more US stuff, so no it’s more of a good surprise, but hopefully it will help more sales of that system in the rest of Europe and in the world.
which is better tho ? patriot or samp/t ?