Skip to content

ObjectControl: Trigger not found if Action not prefixed with start_ in xosc file #647

@ceciliahernqvist

Description

@ceciliahernqvist

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:

  1. Open a scenariofile with a scenario where an actors movement should be triggered by another actor in the scenario.
  2. 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_"
  3. Run scenario with ATOS.
  4. 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
Screenshot from 2024-06-25 13-16-30

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">

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingenhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions