Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
2017.1.0b5
Issue ID
917210
Regression
No
DrawMeshInstancedIndirect should validate arguments ComputeBuffer size/location
To reproduce:
1. Open the project, attached by the user (DrawMeshInstancedIndirectBug.zip)
2. Enter Play mode
3. Observe the Game view (nothing is drawn and no errors are shown)
4. (Optional) Comment line 52 in Example.cs and uncomment line 53 to make it work
Expected: Unity validates the ComputeBuffer size and shows the appropriate error when it is wrong
Actual: no errors are shown when the size of the ComputeBuffer is wrong
Reproduced in 5.6.0b5, 5.6.1p4, 2017.1.0b5, 2017.1.0b10, 2017.2.0a4
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 DynamicHeapAllocator::CreateTLSFBlock when opening a specific project
- Scene flickers when using Mesh Output with SpriteLit Shader in 2D project
- “Cache Management” text is misaligned in Preferences > Package Manager
- [macOS] network permission shows the name of previously closed app when different app requests network access
- Delta value returned by mouse movementsMonitor is different when changing Screen Resolution
Add comment