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
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
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.