Search Issue Tracker
Fixed in 2019.2
Fixed in 2018.4, 2019.1
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
-
tyron0099
May 16, 2020 15:49
Where do i find my computer windows 10,once time in my computer my PC icon suddenly remove one desktop window 10 https://mycomputerwindows10.com so,first just click this site and get the best solution to solve this problem.
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 SceneVisibilityState when trying to open a project containing another project in the Assets folder
- Reflection probe bounces don't work when Rendering Path is set to 'Deferred'
- Shader error undeclared identifier "UNITY_TRANSFER_LIGHTING" when building project
- Shader effect with specific view disappears when multiple materials in scene are present
- Crash on ShaderLab::IntShader::CreateLocalKeywordRemap when loading custom shaders on standalone build
Resolution Note (fix version 2019.2):
Fixed in 2019.2