ZachAR3 You will find the source of your issue in the NavigationMesh baking properties or in your source geometry. The speed of the baking depends on your cell size (larger == faster), the sampling mode (watershed has quality but slow, layers bad quality but fast) and the complexity of your source geometry as all the mesh data from the entire source geometry needs to be parsed and loaded for baking. If you have a few hundred cells that sound like to much for runtime baking and if you have a few thousand that sounds like complete overkill and that you need to split your procedual map into multiple navigationregions for runtime baking to avoid lag. There is also the chance that your source geometry is just way to large in size and scaled. The baking creates a voxel representation of your source geometry and if it is to much for the internal data types and memory it can lead to an near endless loop (aka 3 min waiting for a thing that should be done in less than 3 seconds).
