Search Issue Tracker
Fixed
Fixed in 2021.3.41f1, 2022.3.39f1, 6000.0.11f1
Votes
2
Found in
2020.3.44f1
2021.3.18f1
2022.2.5f1
2022.3.0f1
2023.1.0b3
2023.2.0a1
2023.3.0a1
6000.0.0b11
6000.1.0a7
7000.0.0a1
Issue ID
UUM-29346
Regression
No
NavMesh from previous Scene is visible after going into Play Mode when Reload Scene is toggled off
How to reproduce:
1. Open the user’s attached project “BugDemoPlayMode.zip”
2. Enter Play Mode
3. Press the “Switch Scenes” button
4. Open the Scene View window
Expected result: Only the current Scene’s NavMesh is shown
Actual result: The previous Scene’s NavMesh is shown together with the current one
Reproducible with: 1.0.0-exp.4 (2020.3.44f1), 1.1.0-pre.1 (2022.2.0b10), 1.1.1 (2020.3.44f1, 2021.3.18f1, 2022.2.5f1, 2023.1.0b3, 2023.2.0a1)
Reproduced on: Windows 10
Notes:
- Workaround to this issue is to re-launch the Editor
- Issue reproduces with these continuing steps as well:
5. Exit Play Mode
6. Open Scene2 from the Scenes folder
7. Open Scene View
- Issue does not reproduce when Reload Scene is toggled on in Edit > Project Settings > Editor > Enter Play Mode Settings
Comments (1)
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
- TextMeshPro text input's caret is flickering when Line Mode is set to Multi Line and text is selected
- Can’t delete gradient keys with Mac keyboard or context menu options
- Editor freezes for a few minutes when closing or switching a VFX window that was opened in a previous project
- UI Overlaps when switching Render Pipeline Asset for different Quality Levels in Quality Project Settings
- Ray Tracing Shader link to the documentation isn’t working
GAMEDIA_Justin
Mar 18, 2024 11:05
The NavMesh is also there in PlayMode. NavMesh.SamplePosition and NavMesh.CalculatePath are giving us positions on the NavMesh of the old scene. This makes disabling 'Reload Scene' completely useless for us.