[ANSWERED] Can't assign group to mission (says problems with No-Navigation zones)

[mazex]

Hi!

Some AI missions that previously worked do not trigger now (since 1.11 at least). They have "lost" their mission they where assigned to and when I try to add them I get the error below about conflicting No-Navigation zones:



Have tried everything. Recreating the units, tagets and missions. And I have no "No-Navigation zones" in the mission so I am getting exausted of ideas?

Anyone that has some idea about this?

Regards /Mazex

[michaelm75au]

Can you attach a save of the problem to help with investigation?

[AlexinCT]

I too have seen this behavior, and after some digging I find that it seems to be tied to having a sea control mission that overlaps targets for any other mission. If you add your units to the sea control mission they will join it and execute, but if you have specific strike mission against units that are in that sea control area, they will not join the strike mission and you get that nav zone issue reported even though you have no nav zones.

[ComDev]

Ouch...

I'd REALLY like to have a savegame showing this.

Thanks!

[mazex]

ORIGINAL: emsoy

Ouch...

I'd REALLY like to have a savegame showing this.

Thanks!

Thanks - I am going crazy over here

The units I am having problem with are the four Su-17 wings starting over Kaliningrad in the air (846 OMSHAP wing 1 to 4). They have missions with corresponding names.

The missions I want them to perform in their Su-17M3:s with ordinary bombs/rockets is attacking Radars and SAM sites. I CAN get it to work this way:

Assign the group of Su-17:s to one of the "846 OMSHAP mission" AS ESCORTS. Then it won't complain about the no-navigation zones and they will actually go there and perform the attack. If I go into the mission they are in a group called escorts in the list, but the planes are not marked as escorts. This works for 3 of the 4 wings. One of them (wing 2) will "accept" to be escorts but they will immediately go into the state "Mission over: RTB" after the mission starts and go back and land.

Look in the two save files. In version 1.0.9 it WORKS if you don't edit the file (as it has done since the beta). In version 1.10 is does not work, but all accept wing 2 can be "forced" by assigning them as escorts...

Have tried with different setting if it was the range/ordnance or similar with SU-24:s instead but I get the same problem... Sigh! I have also tried creating a completely new ground attack mission and assigning a completely fresh Su-17 to that mission and get the same problem (if there was some corruption in the very old missions / units). No luck with that either..

So - as I see it I either misunderstand that FAB:s can't be used for attacking radars / sams (seems odd but), or it is too far? But I have tried a lot of munitions (rockets, fabs, ARM) with no luck. And moved the planes closer with no luck either. So my final guess is that there are some legacy waypoints / areas that are "currupt"?

Attaching version 1.10 (the "problem file" in this post)

[mazex]

And here is version 1.09 that works if you do not touch it...

As said it is the four 846 OMSHAP wings of 6 Su-17 each that are the problems...

[mazex]

And finally a savefile from today where I got the three flights to accept the missions as escorts. Deleted Wing 2 as it refused. But the other ones attack...

[mazex]

And yes, the scenario is bloated as I have been playing around with it. Do not start crying looking at all the events/triggers that could have been done better

That may be the root problem. Messed up zones etc... But there are no "No-Navigation zones" so the error message is confusing.

The reason I started with 1.10 was actually to start cleaning up events/triggers/zones etc. and get more stuff into the scneario as start for doing a part two. But this problem has stopped me from continuing.

[mazex]

ORIGINAL: AlexinCT

I too have seen this behavior, and after some digging I find that it seems to be tied to having a sea control mission that overlaps targets for any other mission. If you add your units to the sea control mission they will join it and execute, but if you have specific strike mission against units that are in that sea control area, they will not join the strike mission and you get that nav zone issue reported even though you have no nav zones.

Thanks Alex, The missions are "normal" land strike missions with rockets/bombs against Radars/SAM:s (with selected targets and no zones) so that seems like some other problem?

But - thinking of I I may try to see if I could do the missions as "zone" land strike missions instead to see if the grumpy Su-17 pilots may accept that instead of flying home for a Vodka when High Command is trying to start WW3

[ComDev]

Hi guys,

Dug to the bottom of this. The problem is that the mission is targeting HAWK sites that aren't visible yet. Thus there are no contact to create a target waypoint from.

I've added additional checks and the player will now receive the following message:

"The mission is only allowed to attack pre-planned targets, however none of the targets are currently visible and the Flightplan Generator can therefore not create a flight plan for the strike mission."

A better way to do this would perhaps be to assign aircraft through a Lua script when the SAM sites are detected?

[mazex]

Nice - thanks a lot for digging into it!

With an error message like that it will be possible to understand why it does not accept it. I will dig into how to do that in Lua instead!