Search Issue Tracker
Fixed
Fixed in 2021.3.39f1, 2022.3.29f1, 6000.0.1f1
Votes
0
Found in
2020.3.41f1
2021.3.12f1
2022.2.0b14
2023.1.0a16
2023.2.0a1
2023.3.0a3
6000.0.0b11
Issue ID
UUM-18354
Regression
No
TextureArray asset format is not converted, causing runtime artifacts on non-mobile platforms
Reproduction steps:
- Open "SampleScene" in project [https://github.com/Wilfrid-Unity/test-unity-etc-texturearray-asset]
- Build and Run on Mobile, Desktop, Console Platforms
Expected Results:
- For all Standalone platforms, the scene looks the same as in Editor (one blue cube and one green cube).
Actual Results:
- The scene looks the same as in the Editor, when running on Android.
- The scene has artifacts, when running on PC Standalone player (as well as consoles) ; the cubes are rendered with incorrect colors.
Additional Information:
- The scene uses the Texture2DArray asset generated by running the Editor script "Texture2DArrayAssetCreator/Generate ETC2 Texture2D Array Asset". This script mimics the behavior of a popular Asset Store shader solution.
- ETC format is not supported on non-mobile platforms ; however Unity attempts to load it at run-time, resulting in artifacts.
- Ideally, the build process should convert these textures to a format supported by the target platform. At the very least, build process should issue warning/errors regarding Texture2DArray assets in the build that have formats unsupported by the target platform.
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
- Depth of Field doesn't apply correctly to Canvas UI when it is set to World Space Render Mode
- Crash on GetElementMapKey when "None" is assigned to a field with binding path "m_GameObject"
- Stereoscopic skybox renders as monoscopic when using Multi-pass render mode in XR plugin while using URP
- Parameterized Tests with ValueSource fail when supplied parameter is an System.Object
- Error Message "Broken text PPtr in file" is not informative enough to locate the problematic asset
Resolution Note (fix version 2022.3.29f1):
The issue is addressed by making the error explicit to the user
Resolution Note (fix version 2021.3.39f1):
The issue is addressed by making the error explicit to the user