Search Issue Tracker
By Design
Votes
2
Found in
5.6.0f1
Issue ID
894384
Regression
No
NavMesh Modifiers and Volumes does not work with the Legacy NavMesh
1. Open the NavMeshComponents-master 2.zip example project
2. Create a plane
3. Mark it as Navigation Static
4. Attach the NavMesh Modifier (or the NavMesh Modifier Volume) component to it
5. If the Modifier Volume is attached, make sure the area it covers intersects the plane
6. Bake the NavMesh from the Navigation window
- Note that the NavMesh is not affected by the Modifiers, but this is not obvious before going through the steps
Reproduced in: 2017.1.0a4, 5.6.0f2, 5.6.0f1
-
Acreates
Oct 17, 2018 15:13
I also downloaded the navmeshcomponents from the git drive.
Placed down a navMesh Modifier Volume
Marked it unwalkable
Rebaked the NavMesh
The navmesh remains unaffected
If I place an object with collision, rebake the nav, it does get affected.This is the latest unity.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
- The build size is larger when Models have Animation Type set to Generic
- Error "ArgumentException: Both 'ok' and 'cancel' strings are null or empty" logged when User is trying to create circular dependencies in UI Builder Hierarchy
- "SupportsRandomWriteOnRenderTextureFormat()" shows "False" when executed on 2023.2 and 6000.0 streams
Resolution Note:
NavMeshModifier and NavMeshModifierVolume are used only by a NavMeshSurface that generates the NavMesh.
Building the NavMesh using the Bake button in the Navigation window does not use the Modifier or the Volume components.