Search Issue Tracker
Fixed
Fixed in 2021.3.44f1, 2022.3.42f1, 6000.0.15f1, 7000.0.0a1
Votes
0
Found in
2021.3.40f1
2022.3.35f1
6000.0.12f1
7000.0.0a1
Issue ID
UUM-74849
Regression
No
A wrong compute buffer is returned in a render pass when using the "ComputeBufferDesc" to create the descriptors
How to reproduce:
1. Open the “RenderGraphBug“ project
2. Open the “SampleScene“
3. Observe the Console window
Expected result: The “Buffer in Pass 1“ is logging “Count=1 Stride=96“ and the “Buffer in Pass 2“ is logging “Count=5 Stride=4“
Actual result: The “Buffer in Pass 1“ and the “Buffer in Pass 2“ both are logging “Count=1 Stride=96“
Reproducible with: 2021.3.40f1, 2022.3.35f1
Could not test with: 6000.0.8f1 (Could not resolve the scripting errors)
Reproducible on: macOS 14.5 (Intel), Windows 10 (User’s)
Not reproducible on: No other environments tested
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
Add comment