I was thinking of Generic Navigation Radar (#1916), which can be found on civilian and commercial ships, but also some military ships. It's on some aircraft, too.

I wonder, why can't the navigation radar be used for surface contacts detection?

The 84L (Block II) has the JDAM and SLAM guidance package that allows it to strike land and mobile targets. In fact, Boeing's ad blurb uses and example of a mobile unit as a target. I'm assuming parked.

https://boeing.mediaroom.com/2001-08-08-Boeing-Harpoon-Block-II-Missile-Successfully-Attacks ...

Harpoons are being fired at Mobile Targets, and there is no WRA doctrine for those targets.

Simple example attached.

Build 1706

Just tested the scenario commented above, removed the 2 sats on the Singapore side and still works.

Did you try this scenario or another one?


Edit: just tried your scenario and adding a Hawk ELINT sat for the blue side indeed works, for the blue and for the red.

This is undocumented?

I added ...

It seems I found the culprit: there needs to be a satellite in the scenario in order for autotrack civilians to work. Any random satellite will do.

thewood1 wrote: Fri Jul 18, 2025 7:18 pm "Operation Ardent Shield 2030"

Its the second line in the message. Community scenario project.

Indeed... my bad.

Interesting... something must be wrong on my side. Which scenario is this, does it come with the sim? If not, where can I get it?

Sure, I just made a quick one, just to test.

That is exactly what I do, but can't see any civilian unit. Does it work for you?

BTW, I have build 1706, but for me it also didn't work on older versions.

If I understand it correctly, the "Can auto-track civilians" option should make all civilian/commercial units visible on the map.

However, I can't get it to work. Am I missing something?

An unit, not assigned to mission, ignores Engage Opportunity=NO doctrine and fires at hostile unit.

I've attached a very simple scenario which demonstrate this behavior. Just start it and wait a few seconds to detect and identify the enemy, and through the OODA.

thewood1 wrote: Mon May 23, 2022 5:56 pm Those are really old builds. From over a couple years ago.

Or are you using CMNAO?

1147.44 was released two months ago.

<r> In CMO, Chinese Type 055 destroyer has 128 VLS cells (2x64), while in reality it has 112 (64 forward, 48 aft).<br/>
<br/>
<URL url="https://www.navalnews.com/naval-news/2021/03/chinas-2nd-type-055-destroyer-lhasa-%E6%8B%89%E8%90%A8-commissioned-with-plan/"><LINK_TEXT text="https://www ...

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... [:)]

<r> <QUOTE><s>[quote]</s>ORIGINAL: Kushan04<br/>
<br/>
Better to just make your CAP and prosecution zone RPs relative to the carrier so they'll move along with it.<br/>

<e>[/quote]</e></QUOTE>
That's what I did, and that's what's causing me the problem.[:)] As the carrier moves toward the ...

<r> <QUOTE><s>[quote]</s>ORIGINAL: thewood1<br/>
<br/>
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 ...

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.

Congratulations!

Vietnam War DLC would be an instant buy for me!