5e EVC Chappy

Got a 502 Bad Gateway error. Thanks,

null

Yes, I did.

OK, serious question. Did anyone ever succeed this mission? I've flown difficult missions before, but I'm truly lost with this one. None of the strategiy I tried worked. Ended up being shot down every single time.

I concur. The bug is still there apparently. I flew the mission twice yesterday with two different approaches and after reviewing the TACVIEW tape Woody was incredibly slow and couldn't keep up, like M0.38! So he never fires his HARMs even if I ordered him to. All my JSOWs ended up being shot down by either the SA-15 in the valley or the SA-10. This mission is really challenging. Something I've never seen before.

This is awesome! Congrats!

Really looking forward to the F/A-18C Aggressors Air Combat Maneuvering with the new AI logic. Will be interesting for sure. Glad to know MF is still working on it.

I experienced also a big frame drop while on the ground at Incirlik. I do not use the WINWING app or script. I haven't tested since I upgraded to a 3090, but my guess is more likely a CPU bottleneck

In no particular order: Raven One Raven One Dominant Fury Bold Cheetah Operation Cerberus North

Just flew mission 8 I can confirm the TGP not lining up with the coords given bug is still there. Not sure where the TGP is lining up but there's nothing there. Will wait for a fix before continuing..

On the ground I still got a lot of stutters. But as soon as takeoff it basically disappears. Even in VR. The Syria map is very demanding on computer. I heard the Channel map is even worse. But I don't own it.

Did you put your INS switch to IFA after aligment? I had a similar issue in other campaign. I had the switch on NAV instead of IFA. INS switch must be on IFA if a GPS is available (any mission set during 1986 or later should have it) or at NAV if no GPS is available.

Most probably yes. I must have missed it obviously.

I couldn't find it either. Never used it. I had to look in Chuck's guide. I guess it's this one: I took too much time and eventually failed the mission. Although it's kind of frustrating because the mission went well, I think it's a nice addition to realism and immersion.

Reboot/Repair didn't fix it. Any clue? Thanks.