Search Issue Tracker
By Design
Votes
2
Found in
2018.2.0a1
2018.2.12f1
Issue ID
1092444
Regression
Yes
Creating Texture2DArrays with certain formats results in them being changed into another format
How to reproduce:
1. Open tester-submitted project (Texture2DArray)
2. Drag the 'Array2D.cs' script onto any GameObject
3. Enter Play Mode
4. Check Console window
Expected result: the formats, used to create the arrays match the current array formats
Actual result: the formats, used to create the arrays do not match the current array formats
Reproducible with: 2018.2.18f1, 2018.3.0b12, 2019.1.0a11
Not reproducible with: 2017.4.16f1, 2018.1.9f2
Notes:
Different versions may provide different results: for instance, in 2018.3.0b12 an array created with 'ETC_RGB4' format displays 'ETC2_RGB', but in 2019.1.0a11 displays the correct format
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
- “ValidateSchema Error2” error is thrown in the Player when using IL2CPP Scripting Backend
- Symbolic links disappear when a .xcframework file is added through the Unity Editor
- Errors regarding importing occur upon opening a project when the "Library" folder is deleted
- MeshRenderer.sortingLayerID cannot be changed when change is being done in a built Player
- Warnings related to App Icon are being thrown when building project to VisionOS Platform
Resolution Note (2019.1.X):
By-design because ASTC_RGB was a made up format by Unity which doesn't reflect the hardware so ASTC_RGB formats are deprecated. We've removed ASTC_RGB formats in the new GraphicsFormat enum so the result formats will be ASTC_RGBA .