Understanding ME : Last Waypoint (bug?)

[CougarFFW04]

Hi everybody,

 

 

Does the "last waypoint" stopping condition really work ?:huh: Please let me explain (see picture) :

 

In this simple mission a red Mig29 flight is heading towards its WPT2 (white flight path) while a Blue F16 flight is heading towards its respective WPT4 (blue flight path) close to the Mig29 WPT4.

 

Red WPT2 is assigned the enroute task "Engage targets" with a 8 nm radius and a stopping condition setted at WPT3 (as illustrated in the picture). So I would NOT expect that something happening at their WPT4 would trigger any Mig29 reaction when they are orbiting WPT2 (as the WPT2-WPT4 distance is much more than the 8nm engagement radius).

 

Howerver, as soon as the Blue flight approaches the red WPT4, the Mig29 immediatly react and rush to engage the F16...

 

Can someone explain if I do not undertsand the ME logic or if that might be a bug ?

 

I have also another question about task chaining:

 

Let'say that I set 2 tasks at a WPT:

A) enroute task (let'say "enage target")

B) regular task (let's say "orbiting waypoint")

 

Is there any difference if I order them as 1-A) 2-B) or 1B) 2-A)

 

Thanks

 

 

[feefifofum]

Ordered B-A they will not break their orbit unless directly threatened; ordered A-B they will break their orbit to attack the target if it is detected.

 

The stop waypoint should prevent executing the specific engage tasking, but they will still attack a unit that poses a direct threat.

 

By default REACTION TO THREAT is set to ALLOW ABORT MISSION. Adjusting this option can further affect behavior in a number of ways. Experimenting with ROE and REACTION TO THREAT should produce the desired result.

[CougarFFW04]

Hi feefifofum

 

Ordered B-A they will not break their orbit unless directly threatened; ordered A-B they will break their orbit to attack the target if it is detected.

What I was thinking. Good that you confirm. Thanks :thumbup:

 

The stop waypoint should prevent executing the specific engage tasking, but they will still attack a unit that poses a direct threat.

So still not clear why they rush to the F16 as they were far enough and not threatened...

So still an open issue if the "last waypoint" option is bugged or not :joystick:

 

By default REACTION TO THREAT is set to ALLOW ABORT MISSION. Adjusting this option can further affect behavior in a number of ways. Experimenting with ROE and REACTION TO THREAT should produce the desired result.

Will experiment. Thanks :smilewink:

[feefifofum]

Hi feefifofum

So still not clear why they rush to the F16 as they were far enough and not threatened...

So still an open issue if the "last waypoint" option is bugged or not :joystick:

 

Too subjective for me to make a call...for your answer, remove the SEARCH THEN ENGAGE tasking entirely and see if they still go after the F-16s; if so, the issue likely stems from REACTION TO THREAT; if not, there is a problem with the last waypoint stop condition. May also need to investigate whether that means they stop at WP3 or stop once they arrive at WP4.

[CougarFFW04]

Hi,

 

Too subjective for me to make a call...for your answer, remove the SEARCH THEN ENGAGE tasking entirely and see if they still go after the F-16s; if so, the issue likely stems from REACTION TO THREAT; if not, there is a problem with the last waypoint stop condition.

Will try with a basic mission and report back.

 

May also need to investigate whether that means they stop at WP3 or stop once they arrive at WP4.

Can't be IMO. That would be no sens as at WPT i you cannot select i as the "last waypont" but only WPT > i+1