Search Issue Tracker
Fixed in 2018.2.X
Votes
1
Found in
2017.1.1f1
Issue ID
949490
Regression
No
Assertion failed error is thrown when loading textures without a full mipmap chain from an AssetBundle
To reproduce:
1. Download and open attached "AssetBundles_TextureWithPartialMipmapChainLoadBug.zip".
2. Enter Play mode.
3. Notice the console output.
Expected result: No "Assertion failed" errors are thrown.
Actual result: "Assertion failed" error is thrown when loading textures without a full mipmap chain.
Reproduced with: 2017.3.0a7. 2017.2.0b11, 2017.1.1p1, 5.6.3p3.
Full error: Assertion failed: Warning: Streaming Size differs from Actual Size.
Notes: Texture loading is located in Loader.cs script. Textures with full mipmap chain loads without problems. 4 textures are loaded in the project, texture 2 and 4 are the ones which cause assertion error. Despite the error, texture is still correctly loaded.
Comments (1)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Saturn1004
Jan 27, 2019 02:09
I'm having this bug in 2018.3