correct as-is Orbit (triggered action) doesn't resume route

[toutenglisse]

Orbit task through waypoint action does resume route when over, but orbit task through triggered action does not.

.miz attached (2 AI F18, number 1 orbits 1mn at wpt 1 - wpt action - then resumes to wpt 2, number 2 orbits 1mn at wpt 1 - triggered action - then RTB instead of resuming to wpt 2)

Test-orbit-resume-pushtask-vs-wptaction.miz

[NineLine]

Yeah not sure what is up there, I have reported so the team can look, thanks.

[NineLine]

Response from the Team

Quote

 

There are two kind of task adding in triggered actions - SET task and PUSH task.

When PUSH task is used - currently executed task goes down in tasks stack(this mission current task is route so it goes down) and pushed task (this case Orbit) executed. After pushed task finished it is removed from stack, and previous task(this case route) continue execution.

When SET task is used - current task (this mission it was route) replaced by Set task - i.e. previous task removed completely and set task only executed. After new set task finished - ai has no more task left to execute and thus , without tasks ai goes RTB.

So this is not a bug, mission maker should use command that fit what he want to get

 

 

[toutenglisse]

57 minutes ago, NineLine said:

Response from the Team

 

Thanks. Sorry, my bad.