5.6 Project Launcher no longer has an option to stage builds (unable to use pak files)

Development Pipeline & Plugins
, ,
1

The new Project Launcher in 5.6 seems to be missing a way to stage builds which is a prerequisite for using pak files (which is an option that the Project Launcher offers). See the “steps to reproduce” for details. Is there some way to enable this functionality out of the box (and I’m just missing it) or do you recommend we add an engine modification to append -stage to the command the project launcher uses?

2

Steps to Reproduce

  • Use the new Project Launcher to create a custom configuration with “Content Scheme” set to “Pak Files”
  • Run it
  • Build fails with “Only staged builds can be paked, use -stage or -skipstage.”
3

Hi Andrew, thank you for reporting this. My Apologies for the delay in replying - Epic has been on summer break until today.

I’ve reproduced the issue - it seems that the code will only add -stage if you choose to deploy to a device. The same issue can occur with the old Project Launcher too if a profile is configured in the same way.

I’ll create a bug to get this fixed - although I don’t know if it’ll be in 5.6.1 or 5.7 at this stage.

In the meantime, the easiest fix is to change LauncherWorker.cpp line 771:

if (InProfile->IsPackingWithUnrealPak()) { UATCommand += TEXT(" -pak"); UATCommand += TEXT(" -stage"); // <---- fix

Best regards,

David

4

Sounds good, we’ll go with this approach for the time being. Thanks.