SuperKermit

Keep in mind that the F-15A started being implemented already in 1976 taking over the A2A role of the F-4 in US service. So why spend money on something you don’t need?

That was exactly my thought!

I wonder if those 6g on left hand part of the chart are a structural or aerodynamic limitation.

Is that behaviour supposed to be fixed now? I have experienced the same issue more than once in MP.

I see, thx for the clarification! But the Corail pod is not a CT exclusive feature, right? It could be used by the CE/EE as well, right?

Thx for the update! Patience is hard though What would the F1CT/CR bring functionality wise? 4 Sidewinders was only CG, right?

Has there been any word by Aerges if they will add the Corail pod to the official module? I would love to have it in MP!

I wonder if the red circle is correct. Doesn’t the Magic have that auto-lock feature where the seeker is scanning in a 20 or 5 degree pattern? And those 5 degrees should pretty much cover the HUD FOV.

I am a bit confused by the functionality of the 300-600m gun range button with the different IR missiles. What I (think I have) learned: AIM-9B: no function AIM-9P, J: uncage (once a lock-on is achieved), only as long as the button is pressed AIM-9JULI: SEAM? R.550: boresight mode with reduced 5° FOV (from 20°) as long as the button is pressed R.530F IR: no clue. What does it do? Is that correct? Could anybody please elaborate on the 530F IR?

Aerges please add specific keybinds for selector switches such as IDN Mode Selector or Radar Function Selector, etc. Currently there are only options for turning the knob left/right. It would be very helpful to be able to directly select e.g. the radar modes (H.A, I.A, etc.) or the IDN modes (TT, TE, VT, AR). Many button boxes (e.g. VKB SEM or STECS) have mode selector switches which could then be bound to the functions mentioned above. On the other hand some switches like the Stores Jettison Select Switch only have bindings for their positions (up, middle, down). Here it would be great to have bindings to move them up/down, or - even better - toggle switches. The up/down keybinds could then be used with K-switches. Generally, having more options to add keybinds would greatly improve the usability for existing button boxes and HOTAS setups.

As a new F1 pilot I would like to chime in - please add more toggle options!

Is there a drag/weight penalty with the fairing?

Wow, thanks for the quick reaction! However, what I meant is something like in my screenshot. Reason is that it is already hard to match the sound with the corresponding airframe. But knowing which radar type is in that fighter is even one step harder - and frankly not that relevant IMHO. Please excuse, my first post was not very clear in that regard.

You're the man! That quiz is really helpful! But if I may make a suggestion, it would be to include the airframe of the respective radar in the provided answers - that's the information which is the most important for me as a pilot in the end.

Does anybody know, what this HUD symbol stands for?