Unity editor Bake functions differently to scripted break.

I’m developing some 2D isometric world generation logic using NavMeshSurface2d and NavMeshModifer scripts. So far, all the tile colliders have worked ok when baked with the script (calling NavMeshSurface2d.BuildNavMesh).

However, when adding a GameObject to the mix which has it’s own polygon collider, the script call to bake the mesh does not include the gameobjects’ colliders. When I generate the world, then press bake from the UI the colliders are baked fine.

Is there a reason it would work from the GUI but not scripted? Could it be a timing issue? Do I need to ‘construct’ the colliders somehow?

[h8man]

@GitFlip ,

You certainly right. I getting more and more question about baking at runtime, so many other users may encounter this. I will add this info to wiki

Wiki updated

Issue ‘resolved’

[GitFlip]

Thanks for the suggestions @h8man.

I decided to take the approach of understanding why the collider is getting updated correctly at a later point and time, and ran into some good documentation about the collider’s bounds not getting updated to match the transform until LateUpdate() is called.

How we were generating things was instantiating the prefab, setting the transform of this new game object, and eventually programmatically baking. This all happened then before LateUpdate() was called and so the collider’s bounds were never updated even though the transform of the game object was.

To remedy this I simply forced the update by calling Physics2D.SyncTransforms() before calling BuildNavMesh().

FYI: https://docs.unity3d.com/ScriptReference/Physics2D.SyncTransforms.html

So I think that this issue can be closed, but maybe this info is worth mentioning somewhere? Not sure if you really need to though as it’s a fundamental part of Unity Physics not NavMeshPlus.

Thanks again!