Search Issue Tracker
Fixed in 5.4.3
Votes
14
Found in
5.4.0f3
Issue ID
825442
Regression
Yes
[Android]LoadScene is very slow if APK is split in 5.4
To reproduce:
1) Open attached project
2) Make sure it has "Split Application Binary" set in Player settings
3) Build and run on device
4) Tap "New", and then "Next" until you start the game
5) Note down the load times - it takes about 4-5 times more than it did in 5.3 under same conditions
DUT: Google Nexus 5 (Android 6.0.1)
Reproduced in 5.4.0f3, 5.4.1f1
Not reproduced in 5.3.6f1, 5.3.64
Comments (26)
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Rainking
Jan 21, 2017 08:06
Sorry, now I see it is fixed with 5.5.0f3!!!
Rainking
Jan 20, 2017 19:52
Not fixed on 5.5.0f3!!!
fengweipeng
Jan 03, 2017 11:16
It is not Fixed in Unity 5.4.3!
karl_jones
Nov 15, 2016 11:31
The fix for this can be found in patch 5.4.2p1
fengweipeng
Nov 11, 2016 09:01
Fixed in Unity 5.4.3, but Unity 5.4.3 would never be released!
So don't try to develop a large game with Unity!
andrew_2992
Nov 07, 2016 15:42
Oh my lord, I have just finished my game after a year and a half just to find that this 100mb limit is going to jeopardize everything now. I've been reading through all the obb tutorials and reviews and this is an absolute nightmare of a disaster. Life ruined :(
WillemKokke
Oct 24, 2016 18:40
This is mentioned as resolved in the release notes for 5.4.2p1 patch. (https://unity3d.com/unity/qa/patch-releases) so it won't be in a released version until 5.4.3f1, but you do have access to it now.
renanse
Oct 24, 2016 18:38
fwiw, 5.4.2p1 is just now available, which is supposed to fix the issue.
milox777
Oct 24, 2016 02:51
Somehow made even worse in 5.4.2f2.
renanse
Oct 21, 2016 14:47
Looks like 5.4.2 is back, but labeled as released today? Weird.