In the attached model post Collison avoidance the transporter named ACR2 takes random route to reach it's destination instead of shortest route in A Start.
It looks like bug
In the attached model post Collison avoidance the transporter named ACR2 takes random route to reach it's destination instead of shortest route in A Start.
It looks like bug
Not a bug. When ACR1 and 2 meet, ACR2 calculates a new path to circumvent the deadlock. Since the intersection is blocked by ACR1 at that time, the shortest path to the destination leads along the upper path. Aferwards there are no more events that would cause ACR2 to recalculate its path again, so it continues along the alternate route until it reaches its destination.
If you want to achieve a different behaviour, you would have to implement your own deadlock prevention. (Listen to the On AStar Block event and if the Needs Reroute parameter is true, then take the necessary steps to move one of the involved Task Executers out of the way.)
14 People are following this question.
FlexSim can help you understand and improve any system or process. Transform your existing data into accurate predictions.
FlexSim is a fully 3D simulation software environment. FlexSim can be used to simulate any process in any industry.
FlexSim®, FlexSim Healthcare™, Problem Solved.®, the FlexSim logo, the FlexSim X-mark, and the FlexSim Healthcare logo with stylized Caduceus mark are trademarks of FlexSim Software Products, Inc. All rights reserved.
Privacy | Do not sell or share my personal information | Cookie preferences | Report noncompliance | Terms of use | Legal | © Autodesk Inc. All rights reserved