I'm working on two versions of the same worldmap. A full 16x16 node version and a cut-down 8x8 node version. Having sunk a fair amount of time partially navmeshing the 8x8 version, I wanted to transfer that work to my 16x16 node version. Accordingly, I used the resize terrain function to extend my 8x8 node version to a 16x16 node version and imported my 16x16 node height map. As you can see from the following screenshot everything looks fine in the editor.
Unfortunately, when I save this result and reload it the navmesh has shifted as shown in the following editor screenshot:
The act of saving appears to relocate the navmesh automatically to the extended maps bottom left corner as opposed to leaving it where I wanted it. Clearly, this invalidates the value of the resize terrain function after constructing a navmesh.
I tried adding new navmesh faces in the hope of inserting something in the bottom left corner to avoid repositioning, but the tools proved unstable working on an unsaved Navmesh.
@Dejan is it possible to either correct editor saves to avoid navmesh relocation after resizing terrain or provide some other means of transferring useable navmesh.bin data from one worldmap to another where they are required at different coordinates? I was torn between posting this as a suggestion or a bug.
Unfortunately, when I save this result and reload it the navmesh has shifted as shown in the following editor screenshot:
The act of saving appears to relocate the navmesh automatically to the extended maps bottom left corner as opposed to leaving it where I wanted it. Clearly, this invalidates the value of the resize terrain function after constructing a navmesh.
I tried adding new navmesh faces in the hope of inserting something in the bottom left corner to avoid repositioning, but the tools proved unstable working on an unsaved Navmesh.
@Dejan is it possible to either correct editor saves to avoid navmesh relocation after resizing terrain or provide some other means of transferring useable navmesh.bin data from one worldmap to another where they are required at different coordinates? I was torn between posting this as a suggestion or a bug.