Search Issue Tracker
Fixed
Votes
1
Found in [Package]
2019.4
2020.2.3f1
2020.3
2021.1
2021.2
Issue ID
1321912
Regression
Yes
NavMesh Assets aren't checked out in Version Control when the NavMesh changes after baking
How to reproduce:
1. Open the attached "1321912 repro" project
2. Set up Perforce connection in the Project Settings
3. Add and submit the Assets, Packages, and ProjectSettings folder to Perforce
4. Open the "SampleScene" Scene from the Assets folder
5. Select the "Cube" GameObject from the Hierarchy window
6. Enable the "Cube" GameObject in the Inspector window
7. Open the Navigation window from Window > AI > Navigation
8. Open the Bake tab of the Navigation window and click Bake button
Expected results: the "NavMesh" assets in the Assets > SampleScene folder is checked out since it has been modified
Actual results: the "NavMesh" assets in the Assets > SampleScene folder isn't checked out even though it has been modified
Reproducible with: 2019.4.23f1, 2020.3.0f1, 2021.1.0f1, 2021.2.0a10
Not reproducible with: 2018.4.32f1
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note:
Fixed in: 2022.2.0a3
Resolution Note:
Fixed in: 2022.1.0b10
Resolution Note:
Fixed in: 2021.2.12f1
Resolution Note:
Fixed in: 2020.3.32f1