Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.0f1
2018.1.0a1
2018.2.0a1
2018.2.12f1
2018.3.0a1
2019.1.0a1
Issue ID
1091033
Regression
No
Not all shadows are rendered with Shadows.RenderShadowMap when GameObjects are drawn with DrawMeshInstancedIndirect
How to reproduce:
1. Open the attached project
2. Open "Instancing Bug" scene
3. Enter the Play Mode
4. Select "Instances B" in the Hierarchy window then go to Inspector window and disable "Instances B"
Expected: Both "Instances B" and "Instances A" have shadows
Actual: Shadows are rendered only on one "Instances" at the time
Reproduced on: 2017.4.16f1, 2018.1.9f2, 2018.2.18f1, 2018.3.0f1, 2019.1.0a11
Note: Couldn't test on 2017.3.0a1 version because of the thrown error
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
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note:
Won't fix as minor. This only happens on forward rendering pipeline. Workaround : duplicate the shader & material for each object group that are going to use with DrawMeshInstancedIndirect.