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
- UI Overlay Image gets darker on each Camera when multiple Cameras are used
- Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL error when opening the standalone profiler window
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
Add comment