Search Issue Tracker
Won't Fix
Votes
0
Found in
5.6.2f1
Issue ID
924019
Regression
No
In Multi-Scene editing, changing active scene leaves NavMesh settings of the previously active scene
To reproduce:
1. Open attached Unity project "NavMeshWindow.zip"
2. Observe that scenes "1" and "2" have different Navigation Bake configurations
3. Load both scenes (multi scene editing)
4. Change active scene and observe the results
Expected results: Changing active scene should also change Navigation Bake settings
Actual result: Changing active scene has no impact on the Navigation Bake settings. The settings are always set based off the scene which was active first (see attached gif "NavMeshMultiBug.gif")
Reproduced on: 5.5.4p1, 5.6.2f1, 2017.1.0f2, 2017.2.0b1
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
- 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
Resolution Note:
We recommend the use of the NavMeshComponents instead of the Navigation window.