Search Issue Tracker
Fixed
Fixed in 2022.2.7f1, 2023.1.0a8
Votes
0
Found in
2019.4.40f1
2020.3.36f1
2021.3.4f1
2022.1.5f1
2022.2.0a17
Issue ID
UUM-5760
Regression
No
ComputeShader.SetVector() does not work when assigning to int4
Reproduction steps:
1. Open the attached project "Case_1413515.zip" and load Scene "SampleScene"
2. Enter Play Mode
3. Observe the Game View
Expected result: The Game View is white
Actual result: The Game View is black
Reproducible with: 2019.4.40f1, 2020.3.36f1, 2021.3.4f1, 2022.1.5f1, 2022.2.0a17
Notes:
- Issue does not reproduce with regular shaders and Material.SetVector()
- ComputeShader.SetVector() works correctly when assigning to a Vector variable
- ComputeShader.SetInts() can be used as a workaround
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor Perforce login fails when Perforce shows a license expiry warning
- Assertion failed error in HDRP builds when enabling STP via script
- FBX Resamples Curves incorrectly when importing FBX files
- ProBuilder GameObject Faces disappear when increasing the Sides Count value
- FileUtil.CopyFileOrDirectory throws IOException when destination parent folder does not exist
Add comment