Search Issue Tracker
Fixed in 5.3.5
Votes
3
Found in
5.3.2p2
Issue ID
771609
Regression
No
Instantiating prefab with animator component for the first time causes main thread hitch
Steps to reproduce:
1) open users attached project
2) build for standalone
3) press "Spawn Direct Reference Prefab"
- note the time it took to instantiate (printed out)
4) close and run the build again
5) press "Load resources prefab" and then "Spawn resources prefab"
- notice that it took the same amount of time to Instantiate
Expected: instantiating for the first time should be quicker after loading the prefab
Comments (1)
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
jorgenpt
Feb 18, 2016 18:46
To clarify, the issue is that spawning a prefab takes longer the first time you do it, and up to ~50ms that we cannot hide, causing frame hitches. That 3 & 5 take the same amount of time is expected, but that they take a lot longer the first time than the subsequent times is unexpected.