Search Issue Tracker
By Design
Votes
0
Found in
2021.3.31f1
Issue ID
UUM-54608
Regression
Yes
NavMesh is not generated on Physics Triggers
How to reproduce:
1. Download and open the attached project
2. Enter Play Mode
3. Open scene view
4. Observe the mesh with a trigger
Expected: NavMesh is generated on trigger colliders
Actual: NavMesh is not generated on trigger colliders
Reproducible with: 2021.3.13f1, 2021.3.31f1, 2022.3.12f1, 2023.1.18f1, 2023.2.0b16, 2023.3.0a11
Not reproducible with: 2021.3.12f1
Note: This is directly related to UUM-10109 - the fix directly caused this behaviour
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
- 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
Resolution Note:
This was an intentional change that we made to prevent trigger boxes from being included in NavMesh generation because agents and physics bodies can move through trigger boxes and aren't blocked by them.
As a workaround, one can use a collider masked on specific layers. The performance overhead of that is expected to be minimal.