Search Issue Tracker
By Design
By Design in 2021.3.X
Votes
0
Found in
2021.3.30f1
Issue ID
UUM-52914
Regression
No
AssetBundles content bytes aren't equal when comparing with SpriteAtlas
How to reproduce:
1. Download and open the attached "BundleErrorRepro" project
2. In the toolbar, press "BundleError" > "BuildAssetBundlesAndCompare"
3. Observe the console window
Expected outcome: "Bytes Aren't Equal" message does not appear
Actual outcome: "Bytes Aren't Equal" message appears
Reproducible with: 2021.3.30f1, 2022.3.10f1, 2023.1.15f1, 2023.2.0b12, 2023.3.0a7
Reproduced on: MacOS Ventura (13.4)
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
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
- Meshes created via InstantiateAsync render at the spawn position when GPU Resident Drawer is enabled
Resolution Note:
The two bundles were built with different input assets and two different output names, so some differences are expected inside the content.
I've posted some more details to the forum post where this was discussed:
https://forum.unity.com/threads/assetbundle-generation-from-spriteatlas-is-not-deterministic.1494065/
Resolution Note (2021.3.X):
The two bundles were built with different input assets and two different output names, so some differences are expected inside the content.
I've posted some more details to the forum post where this was discussed:
https://forum.unity.com/threads/assetbundle-generation-from-spriteatlas-is-not-deterministic.1494065/