We’ve got a custom movement script that’s a hybrid of a physics based character controller and a navmesh constrained/clamped mover
In order to do the navmesh constraining we use the Linecast api, but we’ve been seeing some random “invisible walls” which usually change position when rebaking with different settings or when the map changes
There’s no “degenerate triangle” warning during baking - we first suspected that, and after changing the settings to eliminate the warning the “invisible wall” was indeed gone, but only through changing the settings and thus “moving” it
I’m kind of at a loss now and pretty certain this has to be a bug/edge case in the linecast or graph generation
I’d be more than happy to send over the graph cache if that helps investigate it aswell
I did try debugging the Linecast call myself, but I don’t fully understand how it’s working so aside from it not hitting any of the edge cases/early returns I couldn’t really see anything
We’re not on 2019.3 yet unfortunately and won’t be for a few more months at the current rate
Are you using any navmesh cutting?
Nope, static pre-built navmesh
The only thing we’re doing is postprocessing the navmesh to delete any unwalkable areas, but disabling the script (by returning at the start of the OnPostScan callback) doesn’t change that area at all - same unconnected “bit”
Yeah, as far as I can tell it is (quick check by putting a plane flat on the ground passes aswell - no hills clipping through only some z-fighting, whole thing appears/disappears)
As in zoom in on the gizmo render? no gaps to be seen
