Search Issue Tracker
By Design
Votes
0
Found in
2019.2
2019.2.0f1
2019.3
2020.1
Issue ID
1184416
Regression
No
ComputeBufferType.Constant is incompatible with ComputeShader
How to reproduce:
1. Open the attached project ("case_1184416-ComputeCBufferBug") using the EnvIronman VM (optional) (more information in Edit)
2. Open the repro scene ("SampleScene")
3. Enter Play Mode
4. Inspect Console
Expected results: Numbers from 1 to 8 are printed
Actual results: "0" is printed 8 times
Reproducible with: 2019.2.11f1, 2019.3.0b9, 2020.1.0a11
Couldn't test with 2017.4, 2018.4 ('ComputeBufferType' does not contain a definition for 'Constant')
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Use Shader.SetConstantBuffer for Constant Buffer. For more information, please read:
https://docs.unity3d.com/2019.1/Documentation/ScriptReference/ComputeBufferType.Constant.html