List
What determines marker file size?
Posted Date: 2018-01-16 4:36     Edited Date: 2018-01-24 9:20     Writer: reimajina

Hi,

We are wondering what impact the marker file size inside unity?

By marker, we means the .2dm that included inside downloaded unitypackage from develop website. Because we have 2 marker package, one with 3 width x 3 height and the other are 3 width x 4.xx height. But after we load it into the same project (with the same 3Dmodels, only changing the 2dm files), the build size (.apk) differ so much. From the unity build log:

Before:


After:

 

As you can see, the level size grows by 50MB. Note that we didnt change anything inside the project except reassigning the 2dm files.

Can you enlight us on this matter?

Thank you.

Best Regards.

Reimajina Team

Posted Date: 2018-01-16 6:24     Edited Date: 2018-01-16 6:29     Writer: inactive

Hi, 

We need some more information to answer your question.

: How many target images did you add to your app?

Thanks

- Maxst support team

Posted Date: 2018-01-16 6:27     Edited Date: 2018-01-16 6:27     Writer: reimajina

Hi,

1) yes, the build test is for android OS

2) 100 targets. It was the same ammount for each marker package.

Thank you.

Best Regards.

Reimajina Team

Posted Date: 2018-01-16 10:08     Edited Date: 2018-01-16 10:13     Writer: inactive

Hi, 

Thanks for your waiting.

We have investigated unity build log and found a optimization point.

If a texture is attached to gameobject which is in hierachy view then the texture might be included in Levels.

When building after removing material from all image trackables the Levels size was reduced dramatically. 

Please watch carefully test condition and log below

=============================

1) Test conditioin

- 2dmaps and textures are from MLPMalayEdited.unityPackage

- ImageTrackable count : 10

2) APK size after builds

- Normal build (No changes from sdk identity state)

Textures      688.2 kb     5.2% 
Meshes        20.9 kb     0.2% 
Animations    0.0 kb     0.0% 
Sounds        0.0 kb     0.0% 
Shaders       468.6 kb     3.6% 
Other Assets  4.2 kb     0.0% 
Levels        5.9 mb     46.0% 
Scripts       653.2 kb     5.0% 
Included DLLs 5.1 mb     39.7% 
File headers  49.1 kb     0.4% 
Complete size 12.9 mb     100.0% 

- After delete material of all ImageTrackables

Textures      688.2 kb     9.6% 
Meshes        20.9 kb     0.3% 
Animations    0.0 kb     0.0% 
Sounds        0.0 kb     0.0% 
Shaders       468.6 kb     6.5% 
Other Assets  4.2 kb     0.1% 
Levels        83.4 kb     1.2% 
Scripts       653.2 kb     9.1% 
Included DLLs 5.1 mb     72.7% 
File headers  49.1 kb     0.7% 
Complete size 7.0 mb     100.0% 

===============================

Actually background images are not used at runtime so removing all trackable's material when build time is good way to reduce app size.

If your team have VCS and knows about unity command line build then remove all trackable's material at build time.

If VCS is not prepared please don't try our recommendations because removing some component at build time is applied permanently and can not be restored.

Thanks

- Maxst support team

Posted Date: 2018-01-24 9:20     Edited Date: 2018-01-24 9:20     Writer: reimajina

Hi,

Thank you for your insight.

The build size was reduced after we remove the background image.

Thank you.


Best Regards,

Reimajina team.