Actor instance placement should NEVER be considered for upload size if we're to have project upload limits.

It doesn’t make sense to me as a creator, we already have so many memory requirements to consider. Limiting our actor placement to an arbitrary upload size feels very counter-intuitive.

I understand that FN has to take the data from somewhere and cook it, that part makes sense, but when you see the final Download size as only 300kb I wonder if anyone will ever reach a download size of 300mb when they will likely in most cases hit an upload limit before anything else.

Here is the same project but with added actors showing the upload size increasing.


Additionally, here is a test project compromised entirely of only Fortnite Props that has an upload size of 27mb!!

image

With the release of UEFN I’m hoping we can move towards a more perf-based dev experience rather than hand holding with arbitrary limits.

We would love some more memory / any word on this.

1 Like

This is a big blocker and I’m really hoping it’s addressed.

Big blocker for me right now as well. I’m using marketplace 4k textures, limited to 256 in max texture size. This project, cooked, would be no larger than 100mb, but it’s currently preventing me from even building it with UEFN as it’s reached the 2gb upload size limit, it doesn’t even want to upload! There should be a pre-upload calculation to make the build pipeline trust us and our config. (there’s even no global build config to set… yet.)