Search Issue Tracker
Fixed in 2021.3.30f1
Fixed in 2021.3.X, 2022.3.X, 2023.1.X, 2023.2.X, 2023.3.X, 2023.3.0a1, future release
Votes
0
Found in
2021.1.9f1
2021.3.0f1
2022.2.21f1
2022.3.0f1
2023.1.5f1
2023.2.0b1
2023.3.0a1
Issue ID
UUM-43741
Regression
No
[Vulkan] maxComputeBufferInputs limits get slashed when device property is max uint
maxComputeBufferInputs limits get slashed when device property is max unit. This happens because device property is unit, but maxComputeBufferInputs is integer. an incorrect fix a long time ago assigns default values when device property is max unit.
Reproduced (mostly) only on AMD GPUs
Contact Matas Tunkevicius for steps on how to reproduce
Reproduction Steps
1. Open Repro Project
2. Switch to Vulkan API
3. Open Sample Scene
4. Press Play
Faulty And Expected behavior shown in image bellow.
!image-2023-07-27-14-02-20-498.png!
Note: Values might differ, depending on GPU you have (example shown uses AMD RX 6800XT)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Trying to access the DPI setting of a visual element that is not on a panel." warning thrown when entering/exiting Play Mode with new Hierarchy not displayed
- Transparent geometry does not render in Built-in Renderer Deferred mode when a custom post-processing effect is enabled on Mac with Metal API
- BuildVectorImage(SceneInfo, Rect) is internal, and should be public
- SVGImporter preset added to the Preset Manager changes to a ScriptedImporter when restarting the project
- Built-in Standard shader variants remain stripped from the build when retained via Shader Variant Collection or Shader Build Settings
Add comment