reported earlier Groups with an active 'ComboTask Route' break the 'MissionRestart' event.

[Damned - Gh0st]

Groups with an active 'ComboTask Route' break the 'MissionRestart' event.

 

When assigning 'ComboTask' Routes to groups during the mission, if the 'MissionRestart' event is triggered, the dedicated server becomes unresponsive and does not finish the MissionRestart event.

 

Logs appear as follow:

INFO    Scripting (Main): event:type=mission restart
WARNING TRANSPORT (Main): CREATING PATH MAKES TOO LONG!!!!!
INFO    Dispatcher (Main): Stop
WARNING APP (Main): task "ComboTask" still exists
WARNING APP (Main): task state for "ComboTask" still exists

 

At this point the mission will hang and not continue the MissionRestart Event.

 

Is there a way to clear "ComboTask" tasks and task states?

• Cycling through all groups and assigning an empty combotask/route before the MissionRestart does not prevent the server hang.
• Destroying all units before the MissionRestart does not prevent the server hang.

 

 

I cannot find any documentation on the lines:

WARNING TRANSPORT (Main): CREATING PATH MAKES TOO LONG!!!!!
WARNING APP (Main): task "ComboTask" still exists
WARNING APP (Main): task state for "ComboTask" still exists

 

If groups are not assigned a ComboTask Route during gameplay, the MissionRestart event completes successfully.

 

 

Any guidance on this would be extremely helpful, thanks!

 

---------------------------------------------------------------------------------------------------------

 

Example Mission and Log is attached.

• After 2 minutes, the mission will attempt to restart.
• The bug seems to traced to order of operations for the mission restart functionality. Sometimes it will occur, sometimes it will not.

NOTE: The example mission contains code snippets protected under the GNU General Public License v3.0.

• Contains pre-release code snippets for S.P.E.C.T.R.E. , the machine learning powered dynamic campaign framework.

ComboTaskHang.miz dcs.log

Edited June 29, 2024 by Damned - Gh0st
updated Title

[Gracey]

Can you give a track, miz, or example scripts you are using so we can try and replicate this?

[Damned - Gh0st]

55 minutes ago, Gracey said:

Can you give a track, miz, or example scripts you are using so we can try and replicate this?

Edited the main post to contain an example mission.

 

Replicated the bug in the following environments:

• Single Player
• Local Multiplayer Server
• Dedicated Multiplayer Server

 

Regarding the mission example:

• After 2 minutes, the mission will attempt to restart.
• The bug seems to traced to order of operations for the mission restart functionality. Sometimes it will occur, sometimes it will not.

NOTE: The example mission contains code snippets protected under the GNU General Public License v3.0.

• Contains pre-release code snippets for S.P.E.C.T.R.E. , the machine learning powered dynamic campaign framework.

[Flappie]

Thanks for the heads up. I added your miz file to an earlier internal report about the same issue.

The "Creating path makes too long" is related to vehicles far from roads being told to go somewhere. When the sim takes too much time to determine a path, it says this in the log.

Edited July 4, 2024 by Flappie

[Damned - Gh0st]

On 7/4/2024 at 2:41 PM, Flappie said:

Thanks for the heads up. I added your miz file to an earlier internal report about the same issue.

The "Creating path makes too long" is related to vehicles far from roads being told to go somewhere. When the sim takes too much time to determine a path, it says this in the log.

 

Thank you!

Maybe as some kind of stop-gap, an API function could be added to the wishlist to be able to clear path generation/active combotasks?

At least until the bug is fixed it would allow coders to call it prior to mission restarts to prevent the above bug