Search Issue Tracker
Fixed
Fixed in 1.1.5, 2.0.0-pre.4
Votes
0
Found in [Package]
1.0.0-exp.4
1.1.4
2.0.0-pre.3
Issue ID
NAVB-47
Regression
No
ExecuteInEditMode warning is listing all of the NavMesh Components when entering the Play Mode from the Prefab mode
How to reproduce:
1. Open the user-attached project “NavMeshAttributes”
2. Open the “SampleScene” scene
3. Open the “Plane” Prefab from the Project window
4. Enter the Play Mode
5. Observe the ExecuteInEditMode warning
Expected result: The warning notifies the user without naming all of the NavMesh Components
Actual result: All of the NavMesh Components are listed, the more Components the bigger the warning window is
Reproducible with: 2021.3.28f1, 2022.3.5f1, 2023.1.4f1, 2023.2.0a23
Reproducible on: Windows 11 Pro
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