I updated my Unity Editor from 2022 to Unity 6 and my app startup time for iOS rose from about 5 seconds to about 30! Any idea why? I have quite many large textures 1024x512 and some music. I don’t load anything manually, it is all loaded with the scene when the app runs.
Do I need to change resource loading change strategy with Unity 6?
Ok now I tried this: new blank project in Unity 6000.0.23, exported to xcode and built to my freshly restarted ipad. Same thing. Blank scene takes forever to load. Apps from Unity 2022 are still fast.
Since nobody has the same issue this is most likely some extra setup missing, thats why repro project would help (maybe you checked some “make it start slower” checkbox ;-)).
Great. Indeed, I got another iPad now, 9th generation, that does not have this problem. But I guess there is no harm always using that launch argument then? If I understand this correctly, without having the argument a small percentage of users will experience these long loads.
I’m having the same problem on the iPad 10.2 2019, the startup is very slow with unity6 and everything is very slow while the same xcode code on the iPhone is very fast. With the unity 2022 version on the iPad it is very fast
@aurimasc I would also like to get the link to the issue tracker, thanks.
I’ m also seeing general regression/overall slowness on iPad 6th gen between Unity 6000.0.33 and 2022.3.33. Our specific application even show some lag. And some comment as other users, no issue on iPhone 13.
Same here, adding the -force-gfx-direct only solve the building issue, when installed from testflight, the issue still exists. disabling multi-threading-rendering via player setting could by-pass this. reply just to receive any updates.
Also after the bug link - I’m not using Unity 6, but I recently upgraded to a more recent version of 2022 (3.62) and it started behaving very slowly on startup on iOS specifically, so I don’t know if it’s any better on an even more recent version of 2022.
Edit - I should note that the slowdown only seems to happen on the first time the app is opened, but it’s very distinctively slow and only seemed to happen after upgrading from an old version of 2022.3 to a new one.