Jump to content

Orbit (triggered action) doesn't resume route


Go to solution Solved by NineLine,

Recommended Posts

  • ED Team
  • Solution

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

 

 

64Sig.png
Forum RulesMy YouTube • My Discord - NineLine#0440• **How to Report a Bug**

1146563203_makefg(6).png.82dab0a01be3a361522f3fff75916ba4.png  80141746_makefg(1).png.6fa028f2fe35222644e87c786da1fabb.png  28661714_makefg(2).png.b3816386a8f83b0cceab6cb43ae2477e.png  389390805_makefg(3).png.bca83a238dd2aaf235ea3ce2873b55bc.png  216757889_makefg(4).png.35cb826069cdae5c1a164a94deaff377.png  1359338181_makefg(5).png.e6135dea01fa097e5d841ee5fb3c2dc5.png

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...