Bug Report: Task Executor Trigger with AStar

Question

question

Alexander Swinarew asked Apr 21, '22 Jason Lightfoot edited Apr 21, '22

Bug Report: Task Executor Trigger with AStar

Hi!

I noticed a strange behaviour today when using task executors and an AStar navigator. I was trying out some triggers on said task executors and used AStar related triggers like OnAStarBlock. After deleting those triggers and resetting the model, the triggers returned. I tried it out in an other new and completely empty model, however the same issue appeared again. All other triggers like OnEntry can be deleted without any problems.

Thanks and best regards

Alex

Software Version:

FlexSim 22.0.0

bug astar trigger

· 1

5 |100000

Attachments: Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Ralf Gruber ♦ commented · Apr 21, 2022 at 03:27 PM

@Phil BoBo

I was able to replicate the problem in 22.0.2 and 22.1.1. Also, there are no picklist options displayed for the A-Star related triggers. Erasing all code for the trigger seems to work, but deleting the trigger brings it back after reset.

Thx

0 ·

Answer 1 · 2022-04-21T15:30:00Z

Jason Lightfoot answered Apr 21, '22 Jason Lightfoot edited Apr 21, '22

Yes - the trigger is not stored on the object, but instead on the traveler node withing the AStar Navigator object which seems to cause the problem.

To remove it you can set the task executor to a different navigator and then back to the Astar.

Thanks for reporting it - its been sent to the developers.

5 |100000

Attachments: Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

question