Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
2017.1.0b1
Issue ID
902696
Regression
Yes
Scene with NavMesh and NavMeshAgent freezes in 2017.1
Steps:
1. Open the "repo" scene in Repo project (the scene has Nav Mesh baked with some Nav Mesh Agents)
2. Play the scene. After a few seconds, Editor stops responding with no error and no crash report.
3. If it doesn't freeze, stop and play again, wait for a few seconds.
Expected result:
Editor is still responding.
Actual result:
Editor is not reponding and not closing. It just freezed.
Notes:
1. If I disable Colliders on NavMeshAgent objects, no freeze.
2. Tried with a new scene, and baked a new Nav Mesh. It will also freeze, but not always. Like 20% (Open "newbake" scene to investigate).
3. Also tested repo scene in Windows Player, also freeze.
4. Tested DX11 and GLCore on Windows Editor, both freeze.
Reproducible with : 2017.1.0b1 (a29fc4a7eb25), 2017.1.0a6
Not reproducible with : 5.6.0p1
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