You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've stumbled upon a very specific instance where the script breaks, it's fascinating because if I move any of the coordinates just slightly, it works again. See the video below:
visibilityGraphBug.mp4
When we try to find a path between origin and destination, it's unable to find a path (the path leading to nowhere at the beginning of the video is a visual bug indicating "can't find path")
But if we change any of the coordinates in Origin or the Boundary just a bit, it works again.
I've narrowed it down to essentially origin not having any links in its graph-node (because for some reason processPoint() never detects anything as isVisible)
Destination (this doesn't actually matter, but including it for completeness)
[-96.81461334228517, 33.012694092241]
The text was updated successfully, but these errors were encountered:
nemosmithasf
changed the title
Rare Bug: added node has no "edge", resulting in no path
In an unique instance, added node has no links, resulting in no path
Oct 30, 2024
I've stumbled upon a very specific instance where the script breaks, it's fascinating because if I move any of the coordinates just slightly, it works again. See the video below:
visibilityGraphBug.mp4
When we try to find a path between
origin
anddestination
, it's unable to find a path (the path leading to nowhere at the beginning of the video is a visual bug indicating "can't find path")But if we change any of the coordinates in
Origin
or theBoundary
just a bit, it works again.I've narrowed it down to essentially
origin
not having anylinks
in its graph-node (because for some reasonprocessPoint()
never detects anything asisVisible
)Here are the inputs for reproducing:
Origin
[-96.75315856933595, 33.047810073472085]
Boundary
Destination (this doesn't actually matter, but including it for completeness)
[-96.81461334228517, 33.012694092241]
The text was updated successfully, but these errors were encountered: