Search Issue Tracker
By Design
Votes
1
Found in
5.0.0b14
Issue ID
650696
Regression
No
[Navmesh] Adding new obstacles causes whole navmesh to recompute
Steps to repro:
1. Open the attached project and the scene
2. The scene has some navmesh agents and falling objects which cause the navmesh to recompute
3. Press play and let it run a bit
4. Observe how red capsules movement start to freeze a bit each time navmesh recomputes.
Actual behavior: nav engine recalculates the entire navmesh each time a carver is added to the scene
Expected behavior: it would recalculate only newly added carvers
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment