Zaphael

Update It appears the chaff is the problem. I tried cranking against an Su-27 that I loaded with zero chaff. The F-14 radar and the phoenix was able to track and kill. So it seems that the problem is how the chaff works and its effectiveness. Strangely, the F-14's TID is part of the problem. When the Su-27 used chaff, it generated a false track that the Phoenix homes after.

Less than 2 G? From what I observed, it does not appear to be a G effect. I hardly pull Gs for the test. I Shoot the missile and gently bank away while reducing throttle to bring the target left or right. The Phoenix appears to work if the nose position is pointed directly at the target. But after offsetting it away, it sort of goes stupid. I want to test next to see whether it is something TWS Auto that's doing that breaks it.

The Phoenix A60, and C47 are both behaving weirdly from my single player / single target test TWS auto launch. Any cranking maneuver to support the Phoenixes causes the missiles to become "Chaff-seekers". I suspect the pitbull code causes the Phoenixes to become chaff-seekers as well. The missile can track the aircraft and suddenly make an abrupt turn towards chaff. However, if the Tomcat, maintains nose-hot within 10 to 20 Degree azimuth of the target (i.e. no cranking), the missile chases the target effectively. Usually results in a kill. This is rather strange since Jester now cranks the radar automatically if the Tomcat cranks away. Why would the nose position of the Tomcat matter so much? The summary is that the Phoenixes now behave like an odd-SARH missile, that pitbulls destroy evil bundles of chaff. I suspect this was not what the devs intended.

In my defence, I was defending against a missile shot. It was a brief spike nonetheless. So, is there any way to configure the gyros to be non damageable from Over-G? Truth is, as realistic as it is (much appreciate the realism), but us sim jockeys cannot feel the jet to avoid accidentally spiking the Gs. So this "realism" without some form of feedback does detract from the experience.

This happened twice in a row. Once without pulling much G as I was pretty much in altitude hold doing an orbit for about 20 minutes. The second time was after spiking to 11Gs trying to break into a missile. Long and short, is the slanted HUD pitch ladder due to over-G effects on the INS or Gyros? It seems like the pitch ladder would gradually recover after flying straight and level for a while, but the FPM would remain inaccurate. Is there a way to reset the gyros or INS? Or is there an option to limit Over-G damage to them via options?

Try hitting the PLM whenever Jester switches to RWS or you need to reset the scan azimuth back to centre. Jester would kinda reset himself to TWS-Auto and reacquire the contacts. I noticed the AWG-9 tends to give Jester problems when I'm flying too high in relation to the target. I would have to drop altitude to gain solid radar hits for the TWS Phoenix shots.

Normal behaviour for the cat. Its got lots of lift which wings fully forward. Just gotta trim your jet, and keep trimming your jet. Making large power inputs will require more trim corrections. When landing, you need to use your DLCs to negate the lift and adjust your glide slope. Otherwise the cat does not want to drop altitude. Thats why they put the DLCs.