You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Delayed start for an object does not work unless actionName for an object is prefixed with "start_", e.g. <Action name="2,start_follow_trajectory">
To Reproduce
Steps to reproduce the behavior:
Open a scenariofile with a scenario where an actors movement should be triggered by another actor in the scenario.
Go to ManouverGroup for the triggered actor ID, at the row for <Action name="ActorObjectID,Action">
make sure "Action" does not contain the prefix "start_"
Run scenario with ATOS.
Note that the output will state that no trigger where found for the specified actor, e.g.: [object_control-3] [INFO] [1719314506.627170743] [atos.object_control]: Got trigger start for object 2: 0
Expected behavior
Would like ATOS to be able to handle triggers without a specific prefix, or otherwise output a warning message or something about not handling triggers without "start_" prefix.
Screenshots
Additional context
Same issue occurs if there happens to be a space in between ActorObjectID, and Action, e.g. <Action name="2, start_follow_trajectory">
instead of <Action name="2,start_follow_trajectory">
The text was updated successfully, but these errors were encountered:
ceciliahernqvist
changed the title
ObjectControl: Trigger not found if not prefixed with start_ in xosc file
ObjectControl: Trigger not found if Action not prefixed with start_ in xosc file
Jun 25, 2024
Describe the bug
Delayed start for an object does not work unless actionName for an object is prefixed with "start_", e.g.
<Action name="2,start_follow_trajectory">
To Reproduce
Steps to reproduce the behavior:
<Action name="ActorObjectID,Action">
make sure "Action" does not contain the prefix "start_"
[object_control-3] [INFO] [1719314506.627170743] [atos.object_control]: Got trigger start for object 2: 0
Expected behavior
Would like ATOS to be able to handle triggers without a specific prefix, or otherwise output a warning message or something about not handling triggers without "start_" prefix.
Screenshots
Additional context
Same issue occurs if there happens to be a space in between ActorObjectID, and Action, e.g.
<Action name="2, start_follow_trajectory">
instead of
<Action name="2,start_follow_trajectory">
The text was updated successfully, but these errors were encountered: