Search Issue Tracker
Active
Votes
0
Found in
2.0.0-pre.3
1.1.4
1.0.0-exp.4
Issue ID
UUM-133538
Regression
No
NavMeshSurface bounds include not only geometry when a child GameObject doesn't have the same global position as the parent
Reproduction steps:
1. Open the attached project “NavMeshTest”
2. In the Hierarchy window select “NAV MESH 1” GameObject
3. In the Inspector window Bake the NavMeshSurface
4. In the Hierarchy window select “NAV MESH 2” GameObject
5. Repeat step 3
6. Inspect “NAV MESH 1” and “NAV MESH 2” bounds in the Game view
Expected result: Bounds for both GameObjects only include geometry
Actual result: Bounds for “NAV MESH 2” Include not only geometry
Reproducible with: 1.0.0-exp.4 (2021.3.30f1), 1.1.4 (2022.3.9f1, 2023.1.13f), 2.0.0-pre.3 (2023.2.0b9, 2023.3.0a5)
Reproducible on: Windows 10
Not reproducible on: No other environment tested
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