Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2017.4.2f1
Issue ID
1030609
Regression
No
[Android] Assertion "(destWidth >= srcWidth && destHeight >= srcHeight)..." thrown when building with 32-bit, half ETC2 fallback
How to reproduce:
1. Open attached "Assertion" project and "SampleScene", notice it contains default Tree prefab
2. Observe the console
Result: Assertion is thrown: "Assertion failed: Assertion failed on expression: '(destWidth >= srcWidth && destHeight >= srcHeight) || (downscale && (destWidth * 2 == srcWidth) && (destHeight * 2 == srcHeight))"
How to reproduce from scratch:
1. Delete Library folder from "Assertion" project
2. Open the project again, switch to Android platform, open "SampleScene", notice that assertion is not appearing anymore
3. Do a build for Android with ETC2 Fallback set to 32-bit, half resolution
Result: Notice that Assertions start appearing again, both after build or when changing scenes. Building with 32-bit or 16-bit ETC2 Fallbacks did not cause this issue.
Reproducible with - 2018.2.0b2, 2018.1.0f1, 2017.4.2f1, 2017.3.0a4
Note: The issue only happens when building/opening the scene that contains default Tree prefab
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
- Shader Compilation for projects with lots of Shaders can be slow (i.e. VFX Graph asset heavy projects)
- Crash on RebuildTransformHierarchyOrMarkForDestruction when opening a scene
- The Editor hangs when opening a project that uses local packages and Version Control
- Area Light is culled when Camera Frustrum is outside the lights range
- The characters of the bottom option in the Scene View Debug Draw Mode dropdown menu are cut off
tessellation
Oct 09, 2018 23:40
Can someone answer the question of whether this assert causes any problems in the builds with the ETC2 fallback at half resolution setting enabled? If no problems, fine, but if it prevents the fallback feature from working then I would request that the fix get migrated back to 2017.4 LTS
Thanks!