Graph gizmos (surface, connections, etc.) continue to be drawn even if I disable them in Gizmos menu (both gizmos for AstarPath and GridGraph). They only stop drawing if I disable gizmos totally, or if I disable AStarPath object (if I re-enable it, they don’t start drawing until I re-enable them in menu).
I debugged a bit, but it seems that the issue is hidden somewhere very deep, because gizmo groups in DrawingManager are all disabled. It seems like some CommandBuffer never got cleared, or something. Or is this a bug with Unity? But other gizmos behave correctly.
The beheviour still seems inconsistent to me even in that case, e.g. why then disabling/enabling AstarPath object stops gizmos from being drawn? Also, this very, very inconvenient: instead of quickly toggling drawing in Gizmos menu, you have to find AstarPath object in scene hierarchy, find the component, open Graphs section, find the necessary graph and then toggle stuff there. Worse, I think this state is saved in scene, so if you disable drawing surface/outline because YOU don’t need them, they also get disabled for other people (unlike stuff in Gizmos menu, which is per-user) and they will have to re-enable these options, and when THEY save the scene, the settings are changed again.
To summarize, if this is not intentional, then this is a bug, and if it is intentional, then I would propose to change this, because it is very inconvenient in a bigger team.
Also, I still think this is not intentional, because the package does check state of Gizmos inside DrawingManager. It just don’t get applied properly for some reason.
I’d imagine because the AstarPath is still drawing the gizmos, just with ALINE instead. Which is the same as if you had normal gizmos drawn, no?
I would think in such case AstarPath object should remember the state of its gizmos (if it ignores Gizmo settings and uses its own) and resume drawing it when I re-enable it, but it doesn’t. So I “kind of but not really” can get my desired behaviour, just with some additional steps (disable AstarPath in Gizmos menu; toggle AstarPath object off; toggle AstarPath object on). I think that in reality, AstarPath does take the state of Gizmo settings into account, just inconsistently.
I can tag this as a feature request and have @aron_granberg take a look for this part.
I could totally be wrong about how it works Wouldn’t be the first time But yeah I’ll tag him for either context or his thoughts on what to do from here. Thanks for the feedback