Search Issue Tracker
Fixed in 2022.2.X
Votes
0
Found in
2019.4
2020.3
2020.3.25f1
2021.2
2022.1
2022.2
Issue ID
1398510
Regression
No
[DirectX11] [URP] Incorrect render result in Play Mode when Graphics API is set to DirectX11
Reproduction steps:
1. Open the attached project "ConstantBufferUpdateIssue.zip"
2. Go to Player Settings and set the Graphics API to Vulkan
3. Enter Play Mode and observe the correct render result
4. Go to Player Settings and set the Graphics API to DirectX11
5. Enter Play Mode and observe the render result
Expected result: Two rows of white cubes are rendered
Actual result: Rendered white cubes are scattered around randomly
Reproducible with: 2019.4.35f1, 2020.3.28f1, 2021.2.11f1, 2022.1.0b9, 2022.2.0a5
Notes:
-Issue is also reproducible when Graphics API is set to DirectX12
-The render result is different each time when entering Play Mode when Graphics API is set to DirectX11 or DirectX12
-Issue is not reproducible when Graphics API is set to Vulkan, OpenGLES3, OpenGLCore
-Issue is not reproduced on Android. Two rows of white cubes are rendered correctly
-Issue is not reproduced on macOS12.2 (Metal) but reproduced on macOS 12.2 (OpenGLCore)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (fix version 2022.2):
Fixed in 2022.2.0a12