Search Issue Tracker
Fixed in 2019.2.X
Fixed in 2018.4.X, 2019.1.X
Votes
0
Found in
2018.3.5f1
Issue ID
1130212
Regression
No
[Graphics, Textures] SRVs are not correct for Texture2DMSArrays
Steps to reproduce:
1. Open attached project
1. Play the "Sample Scene"
2. Take a RenderDoc capture
3. In the resource inspector navigate to "RenderTexture-SRV-*-color-512x512"
4. Expand the ID3D11Device -> pDesc -> Texture2DMSArray and observe that array size is 1
Expected result: ArraySize should be 2 instead of 1
ArraySize: UINT32_MAX instead of ArraySize: 1 displayed in: 2019.2.0a7, 2019.2.0a5
Reproduced in: 2019.2.0a4, 2019.1.0b5, 2018.3.5f1
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2019.2):
Fixed in 2019.2