- A* version: [5.4.6]
- Unity version: [6000.4]
- In older version of Astar, I could place a nodelink2 a couple of units above or below the navmesh and would work fine. Clamping a nodelink gameobject to a terrain would always work. Now, it seems very finicky and I have to manually experiment with the start and end points to get a proper link. It needs to be very close to the navmesh and sometimes a little above and sometimes a little below.
I switched to using a single graph for the graph mask selection. In this manner, it appears consistent and link can be placed from 1 unit above to 1 unit below the mesh. Using 2 or more graphs in the graph mask makes the placement unpredictable and needs to be very close to the navmesh.
When you place the link’s GameObjects try holding CTRL+SHIFT then left-clicking and dragging the square that shows up at the pivot/center of the selected object and drag. This will push the object to the surface of the mesh under the mouse when moving it.
You may already know of this trick and be using it though, and if so, can you provide some more detailed reproduction steps? I’m seeing how the range has to be within 1 unit but I’m not seeing it be inconsistent. But I’m also very much used to using the CTRL+SHIFT modifier to move objects on a surface, hence why I suggested it.