- A* version: 5.3.3
- Unity version: 6000.0.36f1
When I have two overlapping — or just adjacent — GraphUpdateScene
objects, I get inconsistent results on re-scanning the graph. It’s as if they alternate their influence and break the other object around the edges. Here are some screenshots of the setup and results:
(this is all scanning in editor)
As you can see, on each scan, a different grid node is set as walkable/not walkable
(this alternates on each Scan)
Below is the setup on the GraphUpdateScene component.
(These objects have trigger BoxColliders that are not included in the graph scanning)
Is there a way to fix this?
AN ALTERNATE SOLUTION: SCAN FOR TRIGGERS
If I could make the GridGraph
scan include triggers, I would not need the GraphUpdateScene
objects! I could just put these trigger volumes on the ‘Obstacles’ layers in the GridGraph
, which seems intuitive and easy as well!
But since the GridGraph
obstacle scan doesn’t include triggers, I need the GraphUpdateScene…