Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2019.4.X, 2020.3.X, 2021.2.X
Votes
5
Found in
2019.4
2020.1
2020.2
2021.1
2021.1.0b1
2021.2
Issue ID
1302707
Regression
No
Materials applied to GameObjects at runtime from Resources/Addressables are low resolution when Texture Streaming is enabled
How to reproduce:
1. Open the user's attached "U - Bugreport project.zip" project
2. Go to File -> Build And Run
3. Observe the GameObjects in the middle and on the right in the Player (See attached "1302707_repro.mp4")
Expected result: Materials applied at runtime from Resources folder (middle GameObject) and at runtime through Addressables (right GameObject) are displayed in high resolution
Actual result: Materials applied at runtime from Resources folder (middle GameObject) and at runtime through Addressables (right GameObject) are displayed in low resolution
Reproducible with: 2018.4.30f1, 2019.4.18f1, 2020.1.17f1, 2020.2.2f1, 2021.1.0b1, 2021.2.0a1
Note:
- The issue is not reproducible in the Editor
Comments (1)
-
TheDeepVR
Sep 29, 2025 05:22
Encountered a similar bug – I am loading textures from Addressables and changing materials accordingly. As a result, the resolution is low and it does not change; higher mipmap levels are not loading.
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
- Crash on SourceAssetDBReadTxn::SourceAssetDBReadTxn() when opening folders in a sepcific project
- Shader graph node does not update to red when there is a precision mismatch between the base graph and the subgraph
- Gaps between fields cause accidental element selection when pointing slightly above or below "Element ..." text in a list of elements
- UI flickering in Unity Version Control when the merge options are opened
- Build for iOS with UnityAds fails with linker failures when performing a CocoaPods build
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0b1
Resolution Note (fix version 2021.2):
Fixed in 2021.2.6f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.26f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.35f1