Scen#2: Problem with the No fly zone

[nukkxx5058]

Hi, I'm in the second scenario. I want to send a mission to strike the arty near the lake but each time I affect a plane to the mission I get the following message despite teh fact that I'm not trying t o enter the no-nav zones ... Do you have this issue too ?
----
MD.450 Ouragan with loadout 250kg GPB on mission StrikeLake were unable to plot a multi-leg strike course because of No-Navigation Zones. Attempting to find an alternative route

[nukkxx5058]

And the proposed path is totally unrealistic ...

Save>

[nukkxx5058]

Thanks for clarification ...

[rico21]

[:)]

[nukkxx5058]

? what ?

[grond69]

I am by means an expert, but what might be happening is that often the AI will use an off axis approach when planning the path to the IP or the exit path. That path might be too close to the no fly zone.

[ultradave]

I think this is probably the case. (granted I haven't downloaded your save). When I played this I found the AI made some funky flight plans to the targets if I just assigned a strike mission right off the bat. I think it was having trouble with the restricted zones. Things worked more smoothly when I flew the planes manually to an Initial Point that was much closer to the targets, and then assigned them to the mission, or just designated a flight to attack a target.

[nukkxx5058]

ok thanks guys for confirming that you also had the probleme. OK will try your solution to flight closer before assigning the mission.
Thanks

[$trummer]

I had this issue in one playthrough. It affected the routing of a ground-attack a/c that went rogue and was halfway to Damascus before I reined him in.

It's a great scenario, especially for the less experienced player, although it's not without its challenges.