Search Issue Tracker
Fixed in 2020.2
Fixed in 2018.4, 2019.4, 2020.1
Votes
0
Found in
2018.4
2019.3.10f1
2020.2
Issue ID
1254505
Regression
No
Texture Streaming not loading correct mips and not respecting QualitySettings.masterTextureLimit
How to reproduce:
1. Open the attached '1254505.zip' project
2. Open 'SampleScene' Scene
3. Build for iOS and open the Xcode project
4. Select Menu bar-> Product-> Scheme-> Edit Scheme
5. Set GPU Frame Capture to Metal and Metal API Validation to Enabled
6. Deploy the Xcode project to the iOS device
7. Press 'Capture GPU frame' button
8. Observe the lightmaps texture dimensions and MipmapLevelCount
Expected result: 'Lightmap-0_comp_shadowmask' lightmap's resolution is 512x512 and MipmapLevelCount is 10
Actual result: 'Lightmap-0_comp_shadowmask' lightmap's resolution is 128x128 and MipmapLevelCount is 8
Reproducible with: 2018.4.23f1, 2019.4.1f1, 2020.1.0b12, 2020.1.0a15
Reproducible with:
- macOS
- iPhone XR (iOS 13.4.1)
- iPhone 8 Plus (iOS 12.0)
- iPad Air 2 (iOS 11.0.3)
Notes:
- Screenshot and video of the issue attached in Edit
- Could also reproduce inconsistencies with 1K texture
- When masterTextureLimit cycles to 2 then texture dimensions and MipmapLevelCount match
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
- Changes to instanced detail mesh material don't immediately apply
- Undo.RegisterObject or Undo.CreateObject dirties the scene, but no actual changes to Scene are made
- [Profiler] Scrubbing through filtered frames or sorting their data replaces the displayed data with duplicated data entries
- [UI Builder] It is possible to add content to parent document while editing child document in place
- EndChangeCheck is not triggered when clearing the IMGUI search field by pressing the "x" button
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0b1
Resolution Note (fix version 2020.1):
Fixed in 2020.1.5f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.10f1
Resolution Note (fix version 2018.4):
Fixed in 2018.4.27f1