Search Issue Tracker
Fixed in 2018.1.X
Fixed in 2017.2.X, 2017.4.X
Votes
0
Found in
2017.1.1p3
Issue ID
955711
Regression
No
Compressed ETC Variant Sprite Atlases become corrupted when changing their scale with target platform set to Android
To reproduce:
1. Download and open attached "SpriteAtlas ETC Variant Size Issue.zip".
2. Make sure Build Settings are switched to Android platform.
3. Ensure "Test 66" is only Atlas version checked for "Include in Build" option.
4. Enter Play mode.
5. Notice the corrupted sprites in the Play mode and in the preview.
Expected result: Sprites Atlas is scaled and sprites are displayed correctly, maintaining correct aspect ratio.
Actual result: Sprite Atlas gets corrupted, it's aspect ratio is not maintained. Assertion failed error comes up in the console.
Reproduced with: 2017.3.0b3, 2017.2.0f3, 2017.1.1p4, 2017.1.0a5.
Notes: Sprite atlas was introduced in 2017.1.0a5. Error is thrown when Variant atlas Scale is changed to some number with which packing fails (when aspect ratio fails to be maintained). Issue seems to be specific to ETC textures. Issue does not happen when target platform is set to standalone, iOS. Issue persists when application is built.
Error:
Assertion failed: Assertion failed on expression: 'expectedSize + offset == length || (expectedSize < 64 && length == 64 + offset)'
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
Add comment