Search Issue Tracker
By Design
Fixed in 5.6.X
Votes
0
Found in
2017.1.0f3
Issue ID
938624
Regression
No
After removing some assets the "AssetBundleBuild[]" map does not rebuild the AssetBundle that was modified
Steps to reproduce:
1. Open the attached project
2. Click on Menu > TestAB > Create AssetBundles (Map) > 1. All Assets
3. Note that in the directory "Bundles" located in the root of the project, the manifest "bundlea" contains the four assets that belong to it:
Assets:
- Assets/2048tex.jpg
- Assets/SpherePrefab.prefab
- Assets/grass_normal.png
- Assets/TestMaterial.mat
4. Click on Menu > TestAB > Create AssetBundles (Map) > 2. Assets removed
5. Note that in the same manifest file for "bundlea" the "Assets:" tag continues showing the four assets, despite having erased two of them:
Assets whose should be removed:
- Assets/2048tex.jpg",
- Assets/TestMaterial.mat",
Actual result: The assets are not removed from the manifest
Expected result: Assets should be removed from the manifest
Reproduced with: 5.5.4p2, 5.6.3f1 , 2017.1.0p3, 2017.2.0b6, 2017.3.0a3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UnityLinker causes crash when outputting snapshot data for very large projects
- Camera Preview does not detect multiple cameras with same GameObject name
- Crash on TypeTreeIterator::Children() when renaming a corrupted asset while Asset Serialization is set to Mixed
- Cameras (Camera.targetDisplay) render only to Display 0 in the Player when Multi-Display setup is used and DX12 API is set
- [Vulkan] _CameraOpaqueTexture produces a feedback effect on Android Adreno devices when using Vulkan
Add comment