Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2017.4.0f1
2018.4.0f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
2019.3.0a5
Issue ID
1163002
Regression
No
In the Cubemap preview incorrect dimensions are shown when the cubemap texture has wrong resolution
How to reproduce:
1. Open attached project "BugReport_Cubemap.zip"
2. In Project window, observe "skybox_2048_1536" cubemap (the resolution is good, in the preview 512x512 is shown)
3. In Project window, observe "skybox_2084_1536" cubemap (the resolution is a bit wider)
Expected result: in the preview the resolution is shown as 512x512
Actual result: in the preview the resolution is shown as 1024x1024
Reproducible with: 2017.4.30f1, 2018.4.3f1, 2019.1.10f1, 2019.2.0b9, 2019.3.0a9
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
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
Resolution Note (fix version 2020.2):
Fixed in 2021.1.0a1
To clarify, this can still happen, but we added warnings for such cases notifying that artifacts are possible with a texture of irregular resolution