Search Issue Tracker
Won't Fix
Votes
0
Found in
5.4.0a6
Issue ID
755342
Regression
No
[NavMeshSurface] Original NavMeshSurface looses NavMesh data if same NavMesh is assigned to another NavMeshSurface
Steps to reproduce:
1. Open attached project "AI11.zip"
2. Open scene "repro"
3. In hierarchy, select "NavMesh Surface (1)" and bake NavMesh
4. After baking, move it aside
5. In hierarchy, select "NavMeshSurface" and assign it NavMesh created using step 3
6. Notice that "NavMesh Surface (1)" doesn't have NavMesh anymore
Note: might be tricky to reproduce
Reproduced with: Version 5.4.0a6 (e9a637d5a860)
Thu, 17 Dec 2015 13:02:38 GMT
Branch: ai/navmesh/builder
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment