Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.0f1
2017.4.20f2
Issue ID
1129750
Regression
No
The GPU Instancing does not take effect on all gameObjects if they use the same material
To reproduce:
1. Download attached project “Shadow_Instancing_Demo.zip" and open in Unity
2. Open "Demo" scene
3. Enter to Play mode
4. Open Frame Debugger
5. Press "Enable" button in Frame Debugger
Expected results: Observe the Shadows.RenderJobDir > "Draw Mesh M_Mountain_Desert_Three_01" are only called once and say it's instanced
Actual results: Observe the Shadows.RenderJobDir > 4 "Draw Mesh M_Mountain_Desert_Three_01" are not instanced
Reproduced on : 2017.4.0f1 and 2017.4.20f2, 2017.4.21f1, 2018.1.0a1, 2018.1.0a5, 2018.1.0b1, 2018.1.9f2
Not-reproduced on : 2018.2.20f1, 2018.3.7f1, 2019.2.0a6
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
- Crash on when D3D12RenderPass::SetupDeviceResources when opening FBX animation preview
- Serialization errors are thrown when "com.unity.render-pipelines.core" is added as a custom package and Graphics window is opened
- Character Joints unexpectedly rotate when a ragdoll is created using the Ragdoll Wizard
- Crash on GfxDeviceD3D11Base::DrawBuffersBatchMode when rendering the Scene view
- The shared EditorBuildSettings.asset file of symlinked projects is not updated when changing the order of the Scenes in Build Settings in one of the projects
Resolution Note (2018.2.20):
This is fixed in 2018.2+