Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
5.6.1p1
Issue ID
914787
Regression
No
Only one shadow is cast when using Graphics.DrawMeshInstancedIndirect more than one time per frame
How to reproduce:
1. Open the attached "InstancedDrawingTest" project and "Test" scene
2. Observe the Scene Hierarchy, notice that there are three GameObjects that will be drawn with Graphics.DrawMeshInstancedIndirect
3. Enter the playmode
Expected result: Meshes are drawn and all of their shadows are cast
Actual result: Meshes are drawn, but only one mesh gets its shadow cast
Reproducible with - 2017.2.0a1, 2017.1.0b6, 5.6.1p1
Note - Disabling the GameObject that casts the shadow and when enabling it again, makes the shadow being cast by other GameObject
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