Search Issue Tracker
Won't Fix
Votes
0
Found in
5.4.0b8
Issue ID
776897
Regression
No
Using instancing reduces performance when compared to not using instancing
How to reproduce:
1. Open attached project
2. Open the scene main.unity
3. Open the Profiler window
4. Play the scene
- Make a note of the performance
5. Stop playing the scene
6. Modify the material of the Sphere gameobject to be the Default-Material
7. Play the scene again
- Note how the Rendering time increases and the overall performance decreases
- Using instancing appears to have a lot of Overhead compared to not using it
- Reproduced in Version 5.4.0b10 (d5987c96f84a), Version 5.4.0b9 (04b47bfe5580)
- Not reproducible in Version 5.3.3p3 (1c43f6d3d3c3)
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 BatchRendererCullingOutputs::SyncFences when navigating through a Scene via the Scene view
- [Android][Vulkan] Crash on /system/lib/libandroid.so (ANativeWindow_setBuffersGeometry+4) when the Vulkan Graphics API is used
- Event handlers are preventing operations when trying to copy or paste HTML text in the WebGL Player
- [macOS] Crash on __pthread_kill when Exporting a Package while another export is in progress
- Crash on TransformAccessDestroyCallback when removing a URP Decal Projector component from a parent GameObject that had a URP Decal Projector child GameObject
Add comment