Exactly :)
Funny how SMT with this module suddenly starts to use single pop CMs from top launchers. Almost as if you could do that in a MiG-29.
1 Like
Almost every jet can pop single countermasures by simply programing the computer, its just Gaijin is too lazy to model for every single aircraft.
1 Like
viggen is also like this
Viggen doesn’t have 60 CMs at 12.7 tho. F-14A and MiG-29 really need single pop CMs for the sake of endurance, you don’t always need to pop 2 flares or chaff.
Eh idk, it would be stuck with spo 15 and 60 cms
Working on a report for early mig-29 to have its notch angles widened (worsened)
From what I understand, it shouldn’t be able to track targets below (relative) ±144ish kph when target above 10km away
Spoiler
Mig-29 has a MLC filter, which from what i understand is a notch filter.
Also was working on a report to make the n019 radar have worse angular limits, but seems like n019e (export) is different from normal n019, and has worse limits than standard n019
Spoiler
from an east german manual
wait wrong table
that one is for the mig23
problem is that export n019e =/= n019, all radars even n019e are copy paste of n019. If I bug report it, it will only affect mig-29s that aren’t russian. Still a good reason to do it but I’ll probably finish writing it up later on. currently working on a r-73 report
first of all i copied th wrong table
also this manual says the mig-29 has a gimbal limit of ±65°
which are the exact same as in these pictures
yeah because germans got export n019e not domestic n019 which seems to have different angular limits. the image im posting is for n019e not n019
https://community.gaijin.net/issues/p/warthunder/i/nD2Ofws6AvHE
export Mig-29 overperforming scan limits
Now currently working on report of min altitude for radar (30m) and max altitude (23 km)