Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2019.4
2019.4.20f1
Issue ID
1370072
Regression
No
NavMesh/Occlusion deletes Addressable AssetGroup NavMesh when baking NavMesh
How to reproduce:
1. Open the user attached "AssetGroupOcclusionCulling.zip" project
2. Open Window -> Asset Management -> Addressables -> Groups
3. Expand R -> level -> level_00 -> R-level-level_00-navmesh and select the entry that's in this group
4. Open Window -> AI -> Navigation" switch to the "Bake" tab and press the "Bake" button in the Inspector
Expected result: Addressable AssetGroups are unchanged
Actual result: The entry for the NavMesh asset is deleted
Reproducible with: 2019.4.31f1
Not reproducible with: 2020.1.0a1, 2020.3.20f1, 2021.1.25f1, 2021.2.0b15, 2022.1.0a12
Couldn't test: 2019.3.0a12 (Package issues after downgrade)
Note: The issue is in the Unity version
Comments (1)
-
Peter77
Oct 18, 2021 06:39
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.0a1