Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2020.1.0b10
2020.2
Issue ID
1251254
Regression
No
[Bug] ComputeShader calculates the wrong result with Structured and Raw Buffer Shaders when using Intel GPU
Reproduction steps:
1. Open user's attached project "IntelComputeBug.zip" and scene "TestScene"
2. Enter Play Mode
3. Observe "Canvas" -> "Text" GameObject
Expected result: 0 calculations incorrect
Actual result: All "Buffer-Structured" and "Buffer-Raw" calculations incorrect
Reproducible with: 2019.4.4f1, 2020.1.0b16, 2020.2.0a17
Could not test with: 2018.4.25f1 (project breaks)
Note:
Issue does not reproduce with Vulkan and OpenGLCore
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
- SystemInfo.get_graphicsDeviceName() is generating garbage GC Alloc when using Metal graphics API
- Crash on D3D12CommonShader::ApplyGpuProgram when attaching material which samples "_UnityFBInput0" to "Full Screen Pass Renderer Feature" Component
- SpeedTree meshes and objects count differs when comparing the numbers in the Player with the Editor
- Model and Prefab Preview icons are not updated after upgrading associated Materials to URP
- Game view is rendered white when viewing the Editor with HDR display and Post Proccesing is enabled on the Main Camera with 2D URP
Resolution Note (2020.2.X):
The used buffer types should be compatible between C# and the shader (i.e. a StructuredBuffer in C# should correspond to a (RW)StructuredBuffer in the shader). We will add some validation to prevent bugs happening because of this.