Search Issue Tracker
By Design
Votes
0
Found in
2018.2.13f1
2018.3.0a1
2019.1.0a1
2019.2.0a4
Issue ID
1095382
Regression
No
Objects are invisible when using IndirectDrawing based on CommandBuffer
To reproduce:
1. Open user's attached project ("IndirectDraw")
2. Open "IndirectDraw" scene
3. Select "Main Camera" and disable "IndirectDraw" script component
4. Enter Play mode
-- Rocks are visible
5. Enable the same Component
-- Rocks are invisible
Expected: Rocks are visible with the Script Component enabled
Actual: Rocks are invisible with the Script Component enabled
Reproduced with: 2018.3.5f1, 2019.1.0b2, 2019.2.0a4
Notes:
- Could not test with 2017.4 due compilation errors
- ArgumentException: ComputeBuffer.SetData() - error is thrown upon enabling the Component in the Play mode
- ArgumentNullException: Argument cannot be null. - error is thrown upon enabling the Component in the Play mode
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
Make sure the size of data that is being set to the ComputeBuffer matches the size of ComputeBuffer. The console gives an error if the size doesn't match.