[FIXED v1.07] Sea unit attacks neutral (uncommanded)

[VFA41_Lion]

Build 490.

In the scenario Django Wall, I've set up an ASW mission in the reference points on the map and assigned the destroyer, destroyer escort and submarine, as well as the P-3 orion to it. Shortly after starting the game, a neutral bogey is detected coming from Korea and flying across the destroyer's path. For whatever reason, despite being on an anti-submarine mission, the destroyer goes to investigate the contact (I forgot to disable that in the mission, it'd be nice if it was off by default) and then fires a sea sparrow at it. WTF guy?

Uploaded the save moments after it happened, its in the message log.

[Jakob Wedman]

Japan has ROE Engage non-hostile targets=No but Sawayuki (on the ASW mission) has it =Yes.

[VFA41_Lion]

arghhhh whyyyyyyy

[thewood1]

Beat me to it...wtf

[VFA41_Lion]

[s]Well nevermind this report[/s] it'd be nice if the destroyer would stop investigating contacts outside its patrol zone especially as the box is unticked. It'd be even better, when it was ticked, it'd only investigate contacts related to its mission (underwater contacts for ASW, surface for ASuW, air for AAW, etc).

I have a new one from the same scenario. I set 2 F-4s as escorts for any units in the ASW patrol zone (at least I think so, there is nothing indicating whether the game acknowledges it or not). So they take off from Nagasaki, make it to the first reference point... and continue stupidly flying north.

Group_112 just off the south-eastern coast of South Korea.

[Jakob Wedman]

The unit status Halo #3-4 indicates that they are on the ASW Patrol Mission 'ASW', but in the mission editor they are unassigned [&:] If I assign them to the mission 'ASW' (as escorts) they turn south to the patrol area.

[mikmykWS]

ORIGINAL: VFA41_Lion

[s]Well nevermind this report[/s] it'd be nice if the destroyer would stop investigating contacts outside its patrol zone especially as the box is unticked. It'd be even better, when it was ticked, it'd only investigate contacts related to its mission (underwater contacts for ASW, surface for ASuW, air for AAW, etc).

Maybe I'm missing something but where is that happening in this file? The only case where it could happen is if you changed a mission or something like that after it picked up a contact while under a different type or when the box was checked or not. Usually the best method is unassign (so it drops an engaged offensive/defense) and then reassign.

I have a new one from the same scenario. I set 2 F-4s as escorts for any units in the ASW patrol zone (at least I think so, there is nothing indicating whether the game acknowledges it or not). So they take off from Nagasaki, make it to the first reference point... and continue stupidly flying north.

This mission isn't really designed for that. The escort function is designed to be used for other aircraft. An AAW mission would be a better choice.

Sorry this seems to have frustrated you a bit but hope this helps.

Mike

[IWS]

ORIGINAL: Jakob Wedman

Japan has ROE Engage non-hostile targets=No but Sawayuki (on the ASW mission) has it =Yes.

"This business will get out of control. It will get out of control and we'll be lucky to live through it."

[VFA41_Lion]

Maybe I'm missing something but where is that happening in this file? The only case where it could happen is if you changed a mission or something like that after it picked up a contact while under a different type or when the box was checked or not. Usually the best method is unassign (so it drops an engaged offensive/defense) and then reassign.

At 16.30.48 GMT, BOGEY #21 is detected 59 nm northwest of DD 125 Sawayuki. The destroyer continues on its plotted course (230 degrees) as ordered. At approximately 16.41 GMT, as the bogey reaches 27 nm northwest of DD 125 Sawayuki, the destroyer's status changes to 'engaged offensive' and swings around to course 321, to intercept it. Over the next 9 minutes, as the bogey flies behind the destroyer, DD 125 will futilely chase it down. Nothing is changed during this event. Unassigning it from the mission, dropping target, and telling it to disengage does nothing. Only setting the bogey to neutral will get the destroyer to back off.

note: even setting the unit's ROE to not engage non-hostiles does nothing to prevent this behavior.

[mikmykWS]

The mission ROE shoot at non-hostiles is on but turning it off doesn't make a difference.

Ok. I'm going to ask D to take a look as I'm not sure how this unit picked up this state. We appreciate you taking the time to explain this and post your file. Sorry for the bad game behavior.

Thanks!

Mike

[VFA41_Lion]

And thank you for the continuing excellent customer service

[Yokes]

ORIGINAL: IWS

ORIGINAL: Jakob Wedman

Japan has ROE Engage non-hostile targets=No but Sawayuki (on the ASW mission) has it =Yes.

"This business will get out of control. It will get out of control and we'll be lucky to live through it."

Nice Hunt for Red October quote! One of my favorite movies. [:D]

On topic: I have noticed that all ASW patrol missions have the "engage non-hostiles" ROE set to "yes" by default. In my scenarios where neutrals are present, I always manually set it back to "no". It gets a bit tedious.

Yokes

[Yokes]

ORIGINAL: VFA41_Lion

Maybe I'm missing something but where is that happening in this file? The only case where it could happen is if you changed a mission or something like that after it picked up a contact while under a different type or when the box was checked or not. Usually the best method is unassign (so it drops an engaged offensive/defense) and then reassign.

At 16.30.48 GMT, BOGEY #21 is detected 59 nm northwest of DD 125 Sawayuki. The destroyer continues on its plotted course (230 degrees) as ordered. At approximately 16.41 GMT, as the bogey reaches 27 nm northwest of DD 125 Sawayuki, the destroyer's status changes to 'engaged offensive' and swings around to course 321, to intercept it. Over the next 9 minutes, as the bogey flies behind the destroyer, DD 125 will futilely chase it down. Nothing is changed during this event. Unassigning it from the mission, dropping target, and telling it to disengage does nothing. Only setting the bogey to neutral will get the destroyer to back off.

note: even setting the unit's ROE to not engage non-hostiles does nothing to prevent this behavior.

I've noticed this before. I fixed it by removing all the anti-air weapons from the ship. [X(]

It didn't impact the scenario I was using, but I can see how that wouldn't be a reasonable fix for most scenarios.

Yokes

[NakedWeasel]

I've seen this same thing in SA-5s, and in all ballistic missiles. Regardless of ROE/doctrine, the second these weapons see a Side=Hostile, here comes the thunder. Particularly aggravating in scenarios involving strategic nuclear arms. You REALLY have to watch that first step, it can be a REAL doozey. (To the tune of about a billion dead...) [X(]

[mikmykWS]

ORIGINAL: NakedWeasel

I've seen this same thing in SA-5s, and in all ballistic missiles. Regardless of ROE/doctrine, the second these weapons see a Side=Hostile, here comes the thunder. Particularly aggravating in scenarios involving strategic nuclear arms. You REALLY have to watch that first step, it can be a REAL doozey. (To the tune of about a billion dead...) [X(]

Really.

Post a file showing that and we'll take a look[:)]

[IWS]

ORIGINAL: Yokes

ORIGINAL: IWS

ORIGINAL: Jakob Wedman

Japan has ROE Engage non-hostile targets=No but Sawayuki (on the ASW mission) has it =Yes.

"This business will get out of control. It will get out of control and we'll be lucky to live through it."

Nice Hunt for Red October quote! One of my favorite movies. [:D]

On topic: I have noticed that all ASW patrol missions have the "engage non-hostiles" ROE set to "yes" by default. In my scenarios where neutrals are present, I always manually set it back to "no". It gets a bit tedious.

Yokes

It was a tossup between that and "Oh my god, they've got a madman on their hands!"

[NakedWeasel]

Already done in my thread, "Super aggressive SA-5s?" I believe Ragnar said he'd look into it.

[mikmykWS]

Ok