Search Issue Tracker
By Design
Votes
0
Found in
5.3.3p2
Issue ID
775660
Regression
No
Two identical objects produce different Navmesh results
How to reproduce:
1. Open attached project
2. Open scene test.unity
3. Open the Navigation window
- Make sure the Agent Radius is about 0.05 and that the ThursdayTruck gameobject is marked as Navigation Static
4. Build the Navmesh
- Note that the truckMAT1_002 and truckMAT1_005 gameobjects do not have any Navmesh generated on them, while the identical objects right next to them do have a Navmesh generated on them
- Reproduced in Version 5.4.0b24
- By Design: Use "Min Region Area" Under Advanced bake setting to tweak the minimum size of navmesh - e.g. set it to 0 to keep small areas.
- See also: https://docs.unity3d.com/Manual/nav-AdvancedSettings.html
- This page also explains why the areas _does_ exist for two of the wheels in the report (the area straddles a tile boundary - the bright regular grid of lines on the navmesh debug geometry)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment