Search Issue Tracker
Fixed in 2021.2.X
Votes
2
Found in
2018.3.0b1
2018.3.0f2
2019.1.0a1
2019.2.0a1
Issue ID
1128902
Regression
No
Disabling a NavMeshLink component in the Editor does not correctly remove the link from the NavMesh system
How to reproduce:
1. Open the user-submitted project ("NavMeshComponents.zip")
2. Click on the "Link" GameObject
3. Disable the "NavMeshLink" component and deselect the object
4. Click on the Navigation Window and observe the navigation mesh in the Scene View
5. Enter and leave the Play Mode
6. Observe the navigation mesh in the Scene View again
7. Click on the "Link" GameObject again and observe the navmesh in the scene
8. Try to re-enable the "NavMeshLink" component
Expected result: The "NavMeshLink" component is immediately disabled and the mesh link is not visible in the scene
Actual result: The Nav Mesh Link is reintroduced into the Scene when clicking on the "Link" GameObject and trying to re-enable the component throws the "Link is already added: Link (UnityEngine.AI.NavMeshLink) UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)" error
Reproduced in: 2019.2.0a6, 2019.1.0b4, 2018.3.7f1, 2018.3.0b1
Couldn't test with: 2018.3.0a11, 2017.4.21f1 (due to multiple project errors when downgrading)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
Add comment