I know there are already threads about the build size, but I havn’t read something about the build size of seperate scence compared to full project size.I have the following setup:
In my project, there are a lot a scenes with a lot of different assets.
My problem or question is:
When I export a single scene or a new, empty scene of this project it is insane big. By publishing a scene I would expect, that it only includes assets with a reference to in my package, but it seems like it packs everything inside.
Is this so?
I would call this at least a big ToDo cause it makes it almost impossible to reuse assets in bigger projects.
For the moment I always have to clone my main project, delete all unnecessary assets to get a smaller size and then build it. This is very nasty and not really useable, cause if you change an asset, you have to change it everywhere.
Is there a way to fix this or are there any workarounds to decide what should be in my build? This would help me a lot.
When it comes to mobile, I have troubles when my packages have 70 or 100MB, which is the case pretty soon when I upload about 20 models of different products.
This example for this external asset loader might help to solve my issues at the moment.
For the further development of PlayCanvas I believe, some kind of asset tree in the build process, where a expert user can select the assets for his build, would be an awesome step forward (where PlayCanvas don’t have to autodetect all references). I dont know, but I think this issn’t so difficult to add this to your ui and build process. But it would be very, very helpful for me and probably other professional users cause I think we all got similar issues with it.
Nice that you mentioned prefabs. I’m still waiting for some kind of prefab system in PlayCanvas for sharing assets beween projects
Yes, I was thinking you would have one project for all the models/textures etc (with a build script that auto uploads the assets to an external server) and another project for the app that loads the assets dynamically when ran. The issue is that you lose being able to scene editing ability.
A third option (and could be simpler) is to have post build script that removes the assets that are not needed from the package.
That’s a pretty good idea. @will opinions on this?
I’ve got one more suggestion to this build size and preload issue:
It would be much easier to handle this when folders could have this “preload” checkbox.
So you could easily check in or check out whole folders from your build without going through each asset part by part.
At least, this would fit my needs very well.
You can multi select and untick them in one go. Normally I suggest clicking on the first one and shift click on the last to select all. Unfortunately, if you have some files in the folder that are not assets (e.g a FBX file), it doesn’t show the tick box
Oh nice, I didn’t know that! Thanks for the support!
Still it would be an advantage to make this availabe for folders. And go through all subfolders and files automatically. (If the UI would be opensource I’m sure I could implement it )
Is there a “wishlist” somewhere or should I just post it under suggestions?
Has there been any progress on strategies included in PlayCanvas for controlling the asset build output per scene? This will be a factor for us, as well. We use individual scenes for each separate client’s project with the main differences between each scene being the model. Each of our models uses the same code base/functionality so it doesn’t make sense to split things into different projects.
We currently have about 50mb of models per scene and with only 3 scenes our build size is already 170mb where ideally it would be closer to 70mb. Going forward builds will become prohibitively large.
This isn’t a common use case for our users so it hasn’t progressed beyond this thread.
This is probably your best option at the moment and should be pretty straightforward to do with asset tags.
Edit: Just to high level the process: A script would download the build, unzip it, loading the config.json file which has all the asset meta information in it, look for assets that you don’t want included (via a naming convention or asset tags), use the filepath to delete the asset and remove the asset from the config.json.
Since assets now can be marked to be excluded from the final build in the Editor, perhaps you could set up your release flow around it. Maybe have a different branch for separate client, where only their related assets are included, while others are marked to be excluded. Or automate it via a script.