When we see a project folder, and through source control we accidentally create duplicate project files, do those get used in the build calculation, or does UEFN simply build with all the necessary files from the project and ignores the rest?
The ‘Project Size’ should only include assets which are actually used by your map. If you change the ‘Size Breakdown’ dropdown, you can see the cooked size of each asset. The size of files on disk is not really a good indication, as those are ‘uncooked’ - assets will change when cooked, some will get bigger (e.g. materials), some smaller (e.g. textures).
I see. So in terms of project file size limitations (512 mb), which size is taken into account (the cook size or project size)?
This is correct, UEFN should only upload the assets that are being used in your experience.
The smaller limitation you’ll deal with right now is the publish size limit. If you would like to publish, the limit is going to be 300 MB download size (That at the time of this writing 12/15/22). This download size is cooked data. You see this reflected in the Project Size panel. So if you push 700MB and it cooks down to 200MB, you’re fine to publish.
Generally in my experience, the cooked data is smaller than the initial upload data. As @Dig_Squid points out, if your project is primarily materials, it could be bigger. Depends on the composition of your project.
1 Like