Museum Relic - F86 - Mission 11

Hi,

I am using the F-86 in the Museum relic campaign, and am up to Mission 11.

I finally finished mission 10. :joystick: YAY!! I nominate that for mission of the year BTW.

I just started mission 11 tonight and I'm not sure if there is a bug or if what I am seeing is part of the mission design. A picture says 1000 words, so, is this meant to happen? This happens very early on during my startup.

I will try not to give anything away, but during the mission, if I follow orders and meet up with the A-10s etc, I seem to be behind the 8 ball, and get blown out of the sky. I arrive late to the party.

One time I haphazardly flew off course and seemed to arrive on target at the time I should have to surprise the enemy and jump them, and still received the orders to do so, I was just in the right place at the right time, but I was not following the set mission plan, ie I did not wait for the A-10s.

I am just wondering if something is not playing out right. I feel like I am cheating if I don't follow the plan, but I feel like I am behind schedule if I do.

No biggie, it's enjoyable either way, and probably more of a challenge when I am being blown out of the sky. I'm just not sure if the mission has some sort of timing issue.

Cheers,

Haha "mission of the year" nomination for #10. :) Thanks

Well ... I ran through Mission 11 for the F-86 and actually had the planes jam up on taxi half way to the runway, not hit the truck and freak out. Guess I'll have to cite that driver and get him outta there.

Now with that taxi issue I saw, that was a problem that plagued me on the MiG-15 side. I fixed that, but at the time of the fix, the NATO aircraft AI were still functioning properly. Looks like I'll just have to carry that same fix over to F-86 side as well.

Thanks for the report! I'll try and submit an update to ED soon.

- Apache600

Hey Apache,

Thanks for the reply. I replayed that mission a few times tonight, and I also noticed what you did with the some aircraft getting stuck on the taxiway. Once the F/A-18 and once the F-16. Both times they got stuck just near the last corner before the hold short point. The "Abort Takeoff" trick didn't seem to work this time. Another time the two F-15s got stuck about half way down the taxiway for no apparent reason. Then they disappeared, and the next minute they were on the runway and taking off :D .

The main difference tonight though was that this time the F-16 just squeezed past the truck with no impact and no explosion. Last night I played through the mission about four times , and every time the collision and explosion happened, but tonight it was just a near miss every time.

All good, I have just been taxiing around the stuck aircraft and continuing on, and then getting blown out of the sky by ground fire at the target :D. Good times!

Cheers,

Really enjoying the campaign, but can't pass this one. After I have the "relic 1, good work today, you can rtb", i do rtb but I don't have the usual ending message telling me that mission has been a success once I park. Retried several times, same result, even having a score >100, and when i hit the green "end mission" button, DCS is freezing...

hmm, odd. Dumb question, but you are going back to Nalchik, correct?

I'll look into it as well, but in the mean time I'd suggest starting the mission again and selecting the "auto-complete" radio option right away. Exiting the mission after that should advance you to the next one.

hmm, odd. Dumb question, but you are going back to Nalchik, correct?

Yes sir, that was my first guess too, so I checked the arrival in the brief.

Will try the auto complete radio item at mission start, couldn't find it at the end of mission (ok , worked, mission 12 now, nice feature thank you!)

BTW that's with the Sabre

Great, glad to hear you advanced on. I'll still look and see what's going on with it. That "auto-complete" feature only exists during the first 30 seconds of each mission. I didn't want the chance for a player having to go to the F10 radio menu to make a call in a mission and then accidentally hitting that.