Description

The following workaround will allow UAT to pass the correct initial map to the application.

 

RunProjectCommand.Automation.cs

	private static void SetupClientParams(List<DeploymentContext> DeployContextList, ProjectParams Params, string ClientLogFile, out ERunOptions ClientRunFlags, out string ClientApp, out string ClientCmdLine)
	{

...

            if (!String.IsNullOrEmpty(Params.ClientCommandline))
            {
                TempCmdLine += Params.ClientCommandline + " ";
            }
            else
            {
//                TempCmdLine += Params.MapToRun + " ";
                TempCmdLine += Params.StageCommandline + " ";  // workaround
            }

Steps to Reproduce
  1. create a project
  2. make some levels on the editor
  3. open project launcher and create a custom launch profile 
  4. apply following settings
    1. Cook : By the book
    2. Cooked platform : WindowsNoEditor
    3. Cooked maps : select multiple maps
    4. Package : do not package
    5. Deploy : copy to device
    6. Launch : using default role
    7. Initial map : select non default map
  5. Launch the profile

Result

UAT passes multiple maps specified in CookedMap (e.g. ThirdpersonExsampleMap+ThirdpersonExsampleMap1+ThirdpersonExsampleMap2) as startup option and does not respect the initial map.

 

Have Comments or More Details?

There's no existing public thread on this issue, so head over to AnswerHub just mention UE-119188 in the post.

2
Login to Vote

Unresolved
ComponentTools
Affects Versions4.26
Target Fix5.0
CreatedJun 30, 2021
UpdatedJul 15, 2021