Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.4.X, 2019.2.X, 2019.3.X
Votes
7
Found in
2018.4.9f1
Issue ID
1186887
Regression
No
Sprite Atlas stored hash changes when atlas is built on a different machine
To reproduce:
1) Open the attached project and scene
2) Select Atlas in the project browser
3) Change inspector to Debug, and check the Stored Hash value
4) Play the scene
5) Check the Atlas Stored Hash again
Expected: It shouldn't change
Actual: It changed
Reproduced in 2018.4.9f1, 2018.4.10f1
Not reproduced in 2019.3.0a12, 2019.3.0b5, 2020.1.0a1
There's no Stored Hash value in 2018.4.8f1, 2019.2.8f1, 2019.3.0a11
-
Ksushqa
Apr 21, 2020 07:38
Still here. In copies of the project i can see different hashes in sprite atlas, which means my asset bundles have different hashes too without any real changes. Annoying
-
tadakun111
Dec 10, 2019 06:55
me too.
-
zvinless
Dec 06, 2019 18:10
I am still seeing this on 2019.2.15f1
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
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Resolution Note (fix version 2020.1):
Fix in Version: 2020.1.0a15.1783