Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2019.4.X, 2020.3.X, 2021.1.X
Votes
0
Found in
2018.4
2018.4.26f1
2020.2
Issue ID
1274983
Regression
No
NavMesh source object is not pinged when clicking NavMesh error
How to reproduce:
1. Open the user's attached project from "test Immediate Insancing (for grass).zip"
2. Set "SampleScene" as active scene
3. Enter Play Mode
4. Click on error ("Failed to create agent because there is no valid NavMesh") in the Console
Expected result: Indication of the problematic source object
Actual result: No indication of any sort of what causes the problem
Reproducible with: 2018.4.27f1, 2019.4.11f, 2020.1.6f1, 2020.2.0b3
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
- "Cameras" tooltip is too far from the window
- Crash on D3D12CommonShader::ApplyGpuProgram when attaching material which samples "_UnityFBInput0" to "Full Screen Pass Renderer Feature" Component
- SpeedTree meshes and objects count differs when comparing the numbers in the Player with the Editor
- "State comes from an incompatible keyword space" errors when building Entity catalogs
- Model and Prefab Preview icons are not updated after upgrading associated Materials to URP
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0a8
Resolution Note (fix version 2021.1):
Fixed in 2021.1.26f1
Uniform indication added
Resolution Note (fix version 2020.3):
Fixed in 2020.3.23f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.33f1