What? The last time I remember there’s a Magic 2 buff, it’s more of sidegrade, iirc Magic 2 used to have similiar performance with PL-5E-II, now it’s pretty much “Slightly Worser” PL-5EII.
For the gatewidth, yes, it’s to make the lock more reliable, but the funny thing is AAM-3 suffers from the same problem, but at the least AAM-3 have better pull than AIM-9M and also range.
Correct in game there is no method on CAPTOR-M to manually select LPRF. It is only used in PRF automation in STT.
In real life the IRST and radar are simultaneously functional using one-another to verify the legitimacy of contacts, one of the PIRATE papers also mentions that due to PIRATE’s superior measurement of angular velocity the system is able to aide the radar/ATTACK bus in obtaining a more valid target solution. To be absolutely clear: this DOES NOT mean that either system is unable to provide incredibly accurate target detection and track data independently . All contacts are shown on the same scope which seems to be more of a ‘battlespace management system’ than a radar display, also seems to fuse in datalink targets, ground targets and engagement zones of different detected threats.
I believe there’s a marker on the IRL display so the pilot can tell which sensor is detecting what but they do just function together.
In-game I think that’s too thorough, but i’d like the radar display replaced with a Radar+IRST scope which just displays targets, and then add individual radar modes in like a corner that you can cycle through as on the current radar display. IRST does it’s own thing anyway.
Am I tweaking or were you able to manually select prf management yourself a few years ago, I swear they removed that feature for some odd reason (super annoying with planes with hdn radars only)
Yea, had something simulat before the SB got new AI enemys, tried like 50 times to lock the enemy, turned out it was an Bot Me 262, in the end I had to use the BK…
Those damn 262s, No idea how Gaijins expect a Eurofighter Typhoon to catch those :P
I would assume diagrams not to scale? Because I thought pirate was same azimuth as captor (±70)
That’s a confusing topic with plenty of conflicting information.
isnt there there a picture of the DASS page showing the gimbal of the Pirate and the Captor
with the gimbal side to side being 180° for the PIRATE
I mean, you can go look slightly higher.
Its only superior measurement of bearing, radar has superior range measurement. Combining the radars superior range resolution(pale blue area) and the IRSTs superior bearing resolution(dark blue area) gives you the gold area where both overlap. That’s what that graph is depicting.
Yes of course, but I doubt the range data is completely thrown away in the SF process.
Im not saying it tosses the data, it likely retains data that overlaps with other sensors to form the most accurate track it can, I was just saying that the IRST does not have superior capabilities in both range and bearing like it seemed you alluded to. Its superior in bearing, while radar is superior in range, which coincides with the pros and cons of IIR vs radar MAWS as well.
Ahh no I was just saying those are the elements supplied to the SF process.
Whilst your here, Just to confirm, the Squished HUD has been reported right? Seems to be some possible confusion in the R&R at the moment
yes it has 2 times 5 months ago
this is the currently accepted report:
https://community.gaijin.net/issues/p/warthunder/i/c2Z40ouQ7Fzb
Dunno what you mean, its clearly on the list
(Surely didnt added it like 2 minutes ago :)) )
