hasmysocial.blogg.se

Esell hijack 1.0b7 kcnscrew
Esell hijack 1.0b7 kcnscrew










esell hijack 1.0b7 kcnscrew esell hijack 1.0b7 kcnscrew

(Case 1292862) Performance regression: scene load times in builds 2x-10x slower. URP Volume Framework does an entire assembly walk just to initialize itself (0.5s)īut the actual regression here seems to be Resources.Load every single Resources.Load call takes > 3 seconds!!Īnother example - note the blocking time is almost identicalĪnd one more, this call internally loads ~10 shaders in resources (from the Oculus integration) and thus easily blocks for 30 I reported a new case (and another one with additional data): Not sure what's going on here, "SetUserDefinedSettings" alone is taking between 0.5 and 1s in 2020.2 There is a number of really weird places in terms of timing some of them seem to contribute to the slowdowns. I went a bit deeper and profiled this in a larger project. Resources.Load / Shader.Find et al are massively slower in 2020.2.

esell hijack 1.0b7 kcnscrew

It seems that 2020.2 regresses heavily with multiple scenes (an empty scene is scene 0, then that just loads another scene in OnEnable).XR startup time adds (or multiplies, not sure) quite a lot of time to general startup.I kept the scene deliberately simple but there's already clearly regressions visible. See this comparison video I made.Īlso I took some measurements to get to the bottom of this, as we're effectively blocked on multiple current projects (x4-x10 startup time regression = unhappy clients). I backported the project from 2020.2.0a15 to 2020.1.0b12 and saw the load times immediately went back to their normal speeds. Often this has led to 100+ seconds in load time for the app start when on prior engine versions such as 2020.1 or 2019.x the load time was 3-6 seconds (during the Unity splash screen) If we add multiple other scenes in the build with that empty scene, the load time dramatically increases. However, when building an empty scene on it's own, the load time is fine. This behaviour is only observed when at least 3 scenes are included in the build. On earlier engine versions this load time was closer to 20-30 seconds. The load time at the start of our Oculus Quest app and the loading time using async scene load between scenes is almost 2 minutes+ for very simple scenes even though the priority of loading is set to high. Reported at: (Case 1256947) Oculus Quest build start of app and async single scene loading is vastly slower on 2020.2.0a15












Esell hijack 1.0b7 kcnscrew