Sam

Same thing here, and TWS-A steers the radar cone away from the actual track most of the time.

Can you already tell if notch resistance is going to improve with the new API ?

My understanding is that you can't switch to TWS-M while guiding a Phoenix until it goes active. However, since the correct missile behavior isn't correctly implemented, my guess is that we are stuck in TWS-A far longer than we should. Hopefully, a dev or SME can confirm that.

Most of the time when I crank after missile launch, the AWG-9 loses the current track and quickly creates a new one for the same target, and the same happens if the target starts maneuvring/changing direction. So if the AWG-9 can't correlate them, it's going to be very difficult to hit anything :noexpression: For example, I launch a phoenix on a target flanking right, but while the missile is in the air before 16s TTI, the target makes a sharp turn and is now flanking left. If I understand, with a quick change in direction, the AWG-9 will switch to track hold on the old track flanking right, and create a new track flanking left. In that case, if it can't correlate the 2 tracks, I guess the missile is lost with a simple turn ?

I hope this is true :D

Are you using PD-STT or P-STT ? In PD-STT, the bandit can break lock fairly easily by notching (MLC) or going cold (ZDF), but not in P-STT

Cross control means that you put the stick opposite to the rudder. For example if you want to turn to the right at high alpha, you put left stick and right rudder.

So in the context of DCS, if jamming was properly modeled, not even the 54C could be used against the most modern fighters like the F/A-18C or the F-16 ?

Are we really going to start the whole "the Phoenix wasn't designed to engage fighters" discussion all over again ? :D Btw, do you have any documentation on the performance of the phoenix with its latest upgrades against 20xx era jammers ? I'm always happy to learn :)

I'm not sure if I understand your post correctly. If you are firing an AIM-54 in P-STT, the missile is supposed to be active off the rail (when the new API is implemented), so the target won't be able to notch your radar, but will still be able to notch the missile itself. But I agree with you on the fact that the Phoenix is pretty easy to evade atm. Regarding the new changes on the AIM-120, I feel like it's a lot less sensitive to notching and countermeasures, so hopefully the new Phoenix will be the same in the future.

Modern for me :)

I'm also curious to know. To me it feels like it's a lot less than 150Nm but more like 50 Nm most of the time :)

Thank you sir !

Not sure if it's possible, but that would be great. Or in 2 weeks ? :D

Is it just me, or the Tomcat feels easier to trim after the update ? Spotted this line in the changelog : "Adjusted default starting pitch trim"