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)
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…
Turning off Update Physics fixed this behavior on my end. If that’s not required you can turn that off and you should be good
I am not 100% sure of the intention of that setting in general or in this use case though if it’s something you need for your project let me know and I’ll tag Aron on this to review if it’s possibly a bug or just something I’m not understanding.
I’m in a thread working on something semi-related so my first thought is, as a test, trying shrinking the collider and see if it still happens? If that fixes it you may want to consider using the list of points. If not let me know!
Of the DynamicObstacle I’m mainly wondering if this happens if neighboring nodes are being caught in the update… but then why would that be clearing thier tag specifically Time to open Unity and investigate
Yeah it grabs the bounds from the collider. Just looked through the code and it’s pretty much just the bounds of the collider from what I’m reading. (As well as the bounds of where it was before to rescan and restore those nodes)
So I’m getting a little closer to a workaround/solution.
Turning off “IsTrigger” on the GraphUpdateScene’s collider fixes the update (preserves tags).
I toggled “IsTrigger” DURING playing.
But then, for this to also work when starting the game (and the initial scan):
the collider’s layer must be included in the scan
the collider must not be a Trigger.
=> Which then causes the grid to be ON TOP of the GraphUpdateScene collider:
It’s kind of weird that GraphUpdateScene works at “initial scan” with a Trigger collider, but when updating the graph it no longer works with a Trigger collider?
EDIT: Actually, nevermind this. I can’t find a combination of these settings at edit or play time that will leave the tags alone without putting the grid on top of the marker collider.
(But I am not familiar with the flow of GraphUpdateScene / DynamicObstacle is… Does a DynamicObstacle trigger a complete re-scan? Are GraphUpdateScenes supposed to re-apply their properties after that? Or is DynamicObstacle actually supposed to leave the tags alone ?)
3) Using Points
So I tried using the points array instead of a collider (which is much less convenient for editing in this scenario, but that aside).
So, verdict: I’m stuck! I tried every combination of settings I could think of! I tried toggling IsTriggerafter scanning the grid at runtime, etc. But nothing gives me the desired behavior of just leaving the tags alone!
if it’s something you need for your project let me know and I’ll tag Aron on this to review if it’s possibly a bug or just something I’m not understanding.
I’m mainly wondering if this happens if neighboring nodes are being caught in the update… but then why would that be clearing thier tag specifically 
