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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment