Search Issue Tracker
Fixed in 2021.1.20f1
Fixed in 2020.2.X
Votes
0
Found in
2020.1
2020.1.13f1
2021.1
Issue ID
1295490
Regression
No
Texture Mipmap Stripping corrupts the textures in the Build when the crunch compression is enabled
How to reproduce:
1. Open the attached "mipstripping" project
2. Open the Scene "SampleScene"
3. Open the Build Settings (File->Build Settings...)
4. Make sure the "SampleScene" is in the Scenes In Build list
5. Build And Run the project
Expected results: The image is rendered the same as in the Editor
Actual results: The image is corrupted
Reproducible with: 2020.1.0a20, 2020.1.16f1, 2020.2.0b14, 2021.1.0a8
Could not test with: 2020.1.0a19 and earlier because the "Texture Mipmap Stripping" option was not yet introduced
Notes:
- These are the exact conditions for the issue to reproduce:
The "Texture Mipmap Stripping" option in the Player Settings has to be enabled
The corresponding texture has "Use crunch compression" enabled in the Import settings.
Quality Settings is configured so all of the active quality levels have a "Texture Quality" different from 'Full res' (so mipmap stripping can actually be performed)
- The issue has been reproduced on Nintendo Switch, Windows, macOS
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
- Render Graph Execution errors when using GPU occlusion culling with 'Opaque Objects' frame setting disabled on a Camera
- Animator window: “Delete” menu item not greyed out for Base Layer context menu
- Resetting “PC_RP Asset (Universal Render Pipeline Asset)” causes Game view to become black and throws Renderer and NullReference errors in the Console window
- [Mobile] Player Crash on scripting_invoke_profiler_begin when the built Player Scene has an empty UIDocument and is built on IL2CPP
- Unnecessary Warnings are logged when running Player with -batchmode -nographics
Resolution Note (fix version 2021.1.20f1):
Fixed in 2021.1.0a10
Resolution Note (fix version 2020.2):
Fixed in 2020.2.2f1