Using the Mac Platform, when deploying app to iPhone, my app size is too large (several gigs, 4.9 version more than 5gig vs the same app in 4.7 version which was 435 MEG).
Hey KINGandKONG,
Could you please explain a bit further the size of the packages you’re having trouble with? I haven’t seen this large of a difference in packages from 4.8 to 4.9. Does this only occur with one project, or all projects for you? Can you reproduce this on an Android or Windows - - basically does it happen with all packages?
Looking forward to hearing back from you, thanks!
Hi ,
In previous versions, my iOS app was about 800 meg, in 4.9 preview versions, it is much bigger than 4 gigs. My iPhone runs out of storage before the whole app gets loaded.
Do people still use Windows?!!! :):)
I only work on Mac & iOS platform, so I dont know if this happens on other platforms.
Hey K,
So, I’ve packaged two projects that are the same, without starter content from 4.8.3 and 4.9 Preview 3. With the changes that come with the engine, the builds do become a bit larger over time however, I do not see that big of a change as you’ve described.
Could you please to package a template in both 4.8.3 and 4.9.0 Preview 3 and verify that there is not a huge difference? I see the difference between my 2 packages is approximately 68,000kb.
Thank you!
I can confirm that there is a difference. In our case full packaging made with the project launcher tool has gone up about 2x. Most of it are built-in engine content.
Hey ,
Are your projects identical? It’s not unusual for packages to become slightly larger due to upgrades from the engine however, they should not be doubling in size. Please provide some additional information as I was not able to reproduce this and I would like to get a bug in as soon as possible if this is happening. One last question, is this occurring on all projects or just one?
Thanks!
The increase in size is for cooked configurations packaged with Project Launcher as By The Book. It is not our project content that has gone up, but Engine/Content. For example EngineMaterials and EngineDebugMaterials take up 55 Mb combined.
We only have one project. The upgrade process was simple and we have not really changed the project inis from 4.8 to 4.9.
Hi ,
I have packaged an exact identical project in the latest version of 4.7 and 4.9:
I’m including the log files for both so you can compare the two process. The 4.7 version works on iPhone and has the size of 435 Meg. The 4.9 version gets up to 4.2 gig before my iPhone runs out of space.
[4.7 version][1]
[4.9 version][2]
54519-4seven.txt (1.42 MB)
[2]: 54520-4nine.txt (1.16 MB)
I tested this again in 4.9 preview 4. Our .ipa size is around 100 Mb when using Launch on Device but 200 Mb when using Project Launcher → Cook By The Book. It is also 200 Mb when using File → Package Project
We have three maps in the game, but the other two are transition maps that are almost empty. Launch On Device only cooks the main level, but that should certainly not be a difference of 2x.
Hi guys,
A lot of the increase in size is due to the extra shaders due to dynamic point lights. If you don’t want dynamic lighting you can set the number of dynamic point lights to 0 in your Project Settings which should return the shaders to their previous size.
For 4.10 we will be making some improvements to reduce the number of shaders. We have tickets for that UEMOB-45 and UEMOB-46.
Thanks for the information! That does not explain the difference in size though between “launch map on device” versus doing a full cook (in our case the difference is 2x in size, even though the additional levels are very small)
Are you doing this on a Mac or PC? I’m trying to understand the difference in size. When cooking on a Mac we precompile Metal shaders but we may not do that when using Launch On Device.
The project has some engine source changes and is compiled on a windows machine with VS 2013 and running Mac OSX as Virtual Machine.
The editor is running on PC, so cooking and launch on device all happens from Windows.
I tested changing dynamic point lights to 0, turn of mobile hdr in project settings and also turned off Forward Rendering with Metal. The full cook then went down from 200 Mb to about 140 Mb. Launch on Device did not change at all but stayed at 100 Mb.
Hey ,
I reached out to our Developers regarding your concerns. It sounds as if you’re seeing what we’re expecting however, our Developers are looking into this further.
Thanks!
Hi ,
Were the log files of any help? Changing the dynamic point light setting didn’t change anything.
Hey ,
Please review JackP’s response. The increase of size is due to the extra shaders to dynamic point lights. He tells you below how to resolve this issue.
Thanks!
Hi ,
's answer only accounts for “double the size” of an app when the Dynamic Point Light is used. In my case the increase in size is in the order of 10 to 20 times the original size.
Having said that, I think I just figured out why my 4.9 version of the app was several “gigs” instead of the original 400 Meg in 4.7 version.
I’ll update the thread as soon as I run some more tests with the new release version of 4.9.
Hey ,
Definitely provide us additional information, especially if the lighting wasn’t the reason why your app sizes were GBs larger than an app from 4.7.
Thanks!