congestion in load-unload
Accepted solution
Hey @Maria A31, currently there's no built-in way for task executers to avoid collisions while doing offset travel to load/unload items. They will try to avoid each other in A-Star if they're on the network, but it seems your larger operators are on their own system. There's a few options you can try to help the 3D model avoid collisions.
One option is to have a separate queue for each operator (in your case, you'll have 4 separate queues). You can use a dispatcher assign pickup/drop-off for each operator so if one queue is more busy than others they won't idle. You can try attaching them to the A-Star system so they can avoid each other while travelling.
Another option is to restrict the number of operators that can load from the queue. By wrapping the Load Task with an Acquire and Release activity, only 1 operator can load at a time. This will bottleneck performance though. Something similar to this would be to put barriers around the queues so then operators can only load/unload from certain locations.
If you want the Operators to follow a specific path, you could treat them as AGV's and give them their own AGV paths to follow. In the following model, I replaced your nodes with control points and and made each path into a loop so the rotation orientation will be correct.
Here's the documentation on dividers and barriers in A* navigation.
I made some small changes to show how the 4 different queues could operate. All I did was add the queues and change this table you had that specified the Buffer to drop off to.
And it turned out like this:
