Search Issue Tracker
Won't Fix
Votes
0
Found in
5.4.0f3
Issue ID
830614
Regression
No
AssetBundle has a dependency on another AssetBundle due to old properties being stored in the .unity file
To reproduce:
1. Open attached project
2. Open example scene
3. Select TextureReference object
4. In Texture Reference script change Size to 2
5. Add references to textures
6. Change size to 0
7. Save scene
8. Look at .unity file in a text editor and observe that in the
m_Modifications section there are still references to the textures
Expected results: .unity file under m_Modifications section should not contain any references to the textures.
Reproducible: 5.5.0b3, 5.4.1f1, 5.3.6p4, 5.2.5f1
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (2021.1.X):
While true that the dependency calculation is wrong we are not going to fix this as it is no longer a problem in the Scriptable Build Pipeline https://docs.unity3d.com/Packages/com.unity.scriptablebuildpipeline@1.14/manual/index.html.
It is recommended to switch to SBP.