Search Issue Tracker
Active
Under Consideration for 1.0.X, 1.1.X, 2.0.X
Votes
0
Found in [Package]
1.0.0-exp.4
1.1.4
2.0.0-pre.3
Issue ID
NAVB-58
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
- Tile Palette selected dropdown text does not update when palette is renamed
- ArgumentException thrown and reference to Template gets unset when opening UXML file after editing referenced Template in Play mode
- [iOS][WebGL] Player freezes when multiple properties of a VisualElement are changed at the same time
- Warning 'GetControlID at event ValidateCommand returns a controlID different from the one in the Layout event' is logged when undoing the deletion of an Edited Freeform 2D Light
- ShadowCaster2D breaks on certain Rotation positions when Casting Source is set to PolygonCollider2D
Add comment