[USER=“238697”]dark space[/USER] I have also experienced the “out of virtual memory” issue when packaging with frontend.
I get around it by first cooking a smaller map containing many of the assets you want cooking (so do a “Clean and full recook” with only the one map included). Then add additional maps and just “Cook”. Once you have everything cooked without the “virtual memory” issue, you can then package the game, install and then upload the installed game via the Steam SDK.
Another thing that fixed the issue for me when it started happening on the smaller maps was two things:
Cleanup asset redirects by running the following commandlet:
C:\UDK\UDK-2010-03\Binaries\Win32\UDK.com fixupredirects SomePackage.upk
Or for the full project:
Delete your local and global shader cache files from your UDKGame/Content/ folder and replace them with the same files from a fresh UDK install.
This issue was a big worry for me when I first started experiencing it, so now I make sure to regularly run the clean/cook/etc process while working on my project, so i can catch if it is going to start being an issue again, and thus be able to rollback to earlier version to catch what caused it happening.
Hope that helps. If you manage to get a build of your game working on Steam (without using frontend or exposing any of your assets .upk files), please let me know how you did it.
@Nathaniel3W Are you just including your raw .upk files in your Steam build (meaning anyone with UDK can access/view your assets)?