Search Issue Tracker
Fixed
Fixed in 2021.3.30f1, 2022.3.8f1, 2023.1.9f1, 2023.2.0b5, 2023.3.0a1, 7000.0.0a1
Votes
0
Found in
2021.1.9f1
2022.2.21f1
2023.1.5f1
2023.2.0b1
2023.3.0a1
7000.0.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
- Object Picker takes the debounce time to load objects when Object Selector is set to Advanced search
- Packman: The same asset data is displayed differently in "Import" and "Remove" popups
- Reference to a deleted GameObject becomes "None" instead of "Missing" when the GameObject is restored with undo after entering and exiting Play Mode
- Size value in Particle System Curve's tab is highlighted with selection across all tab header
- Particle System Curve's Presets window has no visual indication of what preset is selected
Add comment