Reducing Package size
I've found quite a few topics about this but none so far have been able to help me out unfortunately. I'm making a very simple visualization that I want to send to a client. It shows a very simple 3D model and has one blueprint in it. The data isn't more than 5MB's. However, upon packaging the project the packaged result is more than 200MB!
Not knowing if it was a content issue I've created a new blueprint based testgame without starter content and deleted the few items in the world, making it pitch black. I disabled all plugins except for the plugin manager itself, I ticked the "create compressed cooked packages" checkbox, disabled any irrelevant platforms, decreased the max point lights from 4 to 1 and changed the packaging type from developer to shipping. The exported package size is still a massive 170MB's. All the while the project folder size is only 18MB's.
I highly doubt the base engine with it's prime functions is so large. How else can mobile development be achieved? 170 or 200MB is unacceptable for a file to send to a client because as expected, he was rather put off by the large download for something so simple. I heard that the Tappy Chicken game is only 15MB so there must be something fundamental that I'm doing wrong. Unfortunately I don't posses the skills to modify the engine itself in C++ and disable functionality in there. That's way beyond my league.
Does anyone know what I'm doing wrong?
Please review this documentation, it is Reducing APK Package Size. While it is targeted for mobile development, the blacklisting feature is used on other platforms and will help pull out any files you plan on not using once packaged.
answered Oct 31 '16 at 04:56 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here