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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Resolution Note:
We recommend the use of the NavMeshComponents instead of the Navigation window.