Search Issue Tracker
By Design
Votes
0
Found in
2019.3.0a2
2019.3.15f1
2019.4
2020.1
2020.2
2021.1
Issue ID
1278749
Regression
Yes
FPS drops when the Camera is on the right side of the instantiated GameObject with Graphics.DrawMeshInstancedIndirect method
How to reproduce:
1. Open the user's attached "GPU instancing test.zip" project
2. Open the "InstancedIndirectExample" Scene
3. Enter Play Mode
4. Move the Camera to the right side of the instantiated GameObject with the mouse (See attached "1278749_repro.mp4")
5. Observe the FPS in the Statistics window
Expected result: FPS is the stay when the Camera is on the left and right side of the instantiated GameObject
Actual result: FPS is lower (around 30-40) when the Camera is on the right side of the instantiated GameObject, while on the left side is higher (around 70-120)
Reproducible with: 2019.3.0a2 2019.4.12f1, 2020.1.9f1, 2020.2.0b8, 2021.1.0a1
Not reproducible with: 2018.4.28f1, 2019.3.0a1
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 ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Resolution Note:
This is normal slow down due to large GPU overdraw. Depending of the cubes generation order, the pixels can be fastly rejected or not by the depth-test.