Search Issue Tracker
Fixed in 2017.2.X
Votes
0
Found in
5.6.0f3
Issue ID
919044
Regression
No
Big (>1KB) ComputeBuffers created with IndirectArguments flags fails to be written completely in a Compute Shader
Steps to reproduce:
1) Download attached project and open in Unity
2) Open scene 'Scene' and press play
3) After ~3 seconds stop Play mode
4) Open Console window and you will see a message which says that Items was not written properly
5) Open 'TestCompute' script and edit line 24 (remove or comment the ComputeBufferType.IndirectArguments flag in the constructor)
6) Press Play
7) Check Console window and you will see that items was written properly 'Shader dimension returned: structs 1024 - stride 20'
Expected result: ComputeBuffers created with IndirectArguments flags should be written correctly in a Compute Shader (check attached image 'expected.png')
Actual result: ComputeBuffers created with IndirectArguments flags fails to be written in a Compute Shader (check attached image 'actual.png')
Reproduced with:
5.5.1f1, 5.5.4f1, 5.6.1p3, 2017.1.0b9, 2017.2.0a3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android][GameActivity] APK built with Development Build enabled gets flagged as having Malware
- Default name of manually created Global Light 2D GameObject differs from the one included in the initial project Scene
- Option for "Acceleration Structure Build Flags" cannot be toggled when Lightmaps have been Generated for a Mesh Renderer
- Lights in Batch keep resetting to 0 in the Light Batching Debugger when a new GameObject is created and the mouse cursor is hovered over the Inspector window
- [macOS] Rendering Debugger Volume's "Component" dropdown is opened with a big offset when "Component" field is set to any "Sample Scene"
Add comment