Subscene Entities Cache, Loadable at Runtime ?

i built my player including subscenes entities cache which increased my APK size by 180mo. it's a huge number and unacceptable for android users. so i Zipped all the cache to a single file.zip and the result was awesome! the cache size went down to 4mo. but i dont know if it's possible to specifiy entities cache path at runtime and make it recognizable by subscenes.

any suggestion is much appreciated.

 

maybe my question wasn't enought clear sorry!
my Question is:
is it possible to Change Subscenes Binary Cache Files loading path ?
this way i can doawnload the compressed cache (4mo) and extract it (180mo) into it's the specified folder when the Game is first time opened.
the problem is in Android devices everything under "StreamingAssets" folder is read only.

 

Did you ever figure that out?

 

Most of the assets were uncompressed textures which hugly increased the size of the subscene cache.
The best solution is to use addressable + subscenes which unfortunately is not supported at the moment.
but here is a workaround:
https://forum.unity.com/threads/subscenes-and-addressable-asset-system.861838/#post-6792539

 

Thanks
ill give it a try, this way ill be able to update the subscene without the need to update the full app.

The o stands for Octet:
The octet is a unit of digital information in computing and telecommunications that consists of eight bits.
The term octad for eight bits is no longer common.
Symbol: o
In primary units of information: 1 o = 8 bits = 1 byte.
Mind blowing stuff huh!?

 

Ugh.... I didn't know that subscenes store textures uncompressed. I was using addressables, but then I did that comparison of using subscenes-vs-addressables, and decided to switch to subscenes. I'll add the uncompressed textures as a disadvantage to the pro/con list. Now I'm starting to second guess that decision. That's just sucky.

On a separate topic, when not building (just play mode) is used... what folder are the cache files stored in?

 

Thanks @topher_r ! It appears that I misunderstood how it worked, and it's good to know that the current and future methods use compression.

 

Can you shed some light on that? Is it related to

DOTS Addressables

or

ContentLoadInterface

ContentFile