Matrix Games Forums

Hi!

Is there an option to allow some units to ignore no-navigation zone?

For example, to allow strike planes to enter enemy territory, but prevent CAP to fly over it by using the no-navigations zone, in order to avoid defences.

I think you are missing the point of the no-nav zones. The scenario designer most likely didn't want you to do what you are trying. If they wanted you to be able to override it, they most likely would have used an exclusion zone and penalized you for violating entry if you tried to get around it. My best guess.

ORIGINAL: thewood1

I think you are missing the point of the no-nav zones. The scenario designer most likely didn't want you to do what you are trying. If they wanted you to be able to override it, they most likely would have used an exclusion zone and penalized you for violating entry if you tried to get around it. My best guess.

Well, I created the scenario, so I know exactly what the designer wanted me to do [:)]. And that is to forbid my Combat Air Patrol aircraft to fly over enemy defences, while allowing my strike planes to freely venture into enemy territory and do their job.

Normaly I would do this simply by limiting the mission prosecution area, but since it is fixed to a moving unit (i.e. a carrier), it isn't practical.

Thanks anyway.

ORIGINAL: neno

ORIGINAL: thewood1

I think you are missing the point of the no-nav zones. The scenario designer most likely didn't want you to do what you are trying. If they wanted you to be able to override it, they most likely would have used an exclusion zone and penalized you for violating entry if you tried to get around it. My best guess.

Well, I created the scenario, so I know exactly what the designer wanted me to do [:)]. And that is to forbid my Combat Air Patrol aircraft to fly over enemy defences, while allowing my strike planes to freely venture into enemy territory and do their job.

Normaly I would do this simply by limiting the mission prosecution area, but since it is fixed to a moving unit (i.e. a carrier), it isn't practical.

Thanks anyway.

Better to just make your CAP and prosecution zone RPs relative to the carrier so they'll move along with it.

I really don't understand using no nav zones for this. If you wanted CAP , but not strikes to be included, no nav zones are the last thing I would have thought of... mission settings, exclusion zones, zone timings, lua, etc.

ORIGINAL: Kushan04

Better to just make your CAP and prosecution zone RPs relative to the carrier so they'll move along with it.

That's what I did, and that's what's causing me the problem.[:)] As the carrier moves toward the enemy territory, CAP mission zone moves over it, and that's what I want to avoid.

ORIGINAL: thewood1

I really don't understand using no nav zones for this. If you wanted CAP , but not strikes to be included, no nav zones are the last thing I would have thought of... mission settings, exclusion zones, zone timings, lua, etc.

Could you please elaborate?

You can use a mix of relative and absolute reference points in creating patrol/prosecution zones. Make the ones closest to the threat you want the CAP to avoid at all costs absolute.

That method, though simple, isn't without drawbacks. At the start, the patrol/prosecution zone may be too large. Also, the zone may become invalidated if the carrier has to make a radical course change.

Related to that, if its the AI side that I am trying to build out for, I build a few reference point shapes and missions around where I expect the carrier to be. I then activate and de-activate CAP missions. Since it became easier to drop in ref points with lua, I started using that instead. Again, activating and de-activating missions. I have only done it twice; once using each method and they seemed to work with no issues.

One thing I have never tried is activating and deactivating no-nav zones through lua. That might actually be easier.

Thanks for the help guys! So far the mix of fixed and relative points seems like the best workaround.

IMO no-nav zones should be made more flexible, allowing some units to enter. Hopefuly devs are reading this... [:)]