When I am packing the game it creates Pak files even though in Project Settings / Project / Packaging / Use Pak File is unchecked.
For packing I am using Platforms / Windows / Package Project with Use Project Settings checked.
I am using Unreal Engine 5.6.1
I was using Project Launcher until “5.6”, but now that “Loose files” is marked as legacy, I tried to get to learn the other way as well, in case the option to not use “Pak files” might be removed in the future from inside it.
Now with 5.7 launch I tried Project Launcher again but I get the following error, even on a new project:
********** COOK COMMAND COMPLETED **********
Deployment Context **************
ProjectFile = D:\Game Tests\Unreal Engine Projects\MyProject2\MyProject2.uproject
ArchiveDir = F:\ProgramUse\Unreal Engine\Packaged Projects\Windows
IsCodeBasedUprojectFile = True
DedicatedServer = False
Stage = False
StageTargetPlatform = Win64
InputRootDir = E:\Program Files\Epic Games\UE_5.7
InputProjectDir = D:\Game Tests\Unreal Engine Projects\MyProject2
PlatformDir = Win64
StagedOutputDir = (null)
ShortProjectName = MyProject2
ProjectArgForCommandLines = -project="D:/Game Tests/Unreal Engine Projects/MyProject2/MyProject2.uproject"
RunRootDir = E:\Program Files\Epic Games\UE_5.7
RunProjectDir = D:\Game Tests\Unreal Engine Projects\MyProject2
PakFileInternalRoot = ../../../
PlatformUsesChunkManifests = False
End Deployment Context **************
********** ARCHIVE COMMAND STARTED **********
Archiving to F:/ProgramUse/Unreal Engine/Packaged Projects
Deployment Context **************
ProjectFile = D:\Game Tests\Unreal Engine Projects\MyProject2\MyProject2.uproject
ArchiveDir = F:\ProgramUse\Unreal Engine\Packaged Projects\Windows
IsCodeBasedUprojectFile = True
DedicatedServer = False
Stage = False
StageTargetPlatform = Win64
InputRootDir = E:\Program Files\Epic Games\UE_5.7
InputProjectDir = D:\Game Tests\Unreal Engine Projects\MyProject2
PlatformDir = Win64
StagedOutputDir = (null)
ShortProjectName = MyProject2
ProjectArgForCommandLines = -project="D:/Game Tests/Unreal Engine Projects/MyProject2/MyProject2.uproject"
RunRootDir = E:\Program Files\Epic Games\UE_5.7
RunProjectDir = D:\Game Tests\Unreal Engine Projects\MyProject2
PakFileInternalRoot = ../../../
PlatformUsesChunkManifests = False
End Deployment Context **************
==============================================================================
System.NullReferenceException: Object reference not set to an instance of an object.
at AutomationTool.Platform.GetFilesToArchive(ProjectParams Params, DeploymentContext SC)
at AutomationScripts.Project.CreateArchiveManifest(ProjectParams Params, DeploymentContext SC) in E:\Program Files\Epic Games\UE_5.7\Engine\Source\Programs\AutomationTool\Scripts\ArchiveCommand.Automation.cs:line 26
at AutomationScripts.Project.Archive(ProjectParams Params) in E:\Program Files\Epic Games\UE_5.7\Engine\Source\Programs\AutomationTool\Scripts\ArchiveCommand.Automation.cs:line 71
at BuildCookRun.DoBuildCookRun(ProjectParams Params) in E:\Program Files\Epic Games\UE_5.7\Engine\Source\Programs\AutomationTool\Scripts\BuildCookRun.Automation.cs:line 262
at BuildCookRun.ExecuteBuild() in E:\Program Files\Epic Games\UE_5.7\Engine\Source\Programs\AutomationTool\Scripts\BuildCookRun.Automation.cs:line 43
at AutomationTool.BuildCommand.Execute()
at AutomationTool.BuildCommand.ExecuteAsync()
at AutomationTool.Automation.ExecuteAsync(List`1 CommandsToExecute, Dictionary`2 Commands)
at AutomationTool.Automation.ExecuteAsync(List`1 CommandsToExecute, Dictionary`2 Commands)
at AutomationTool.Automation.ProcessAsync(ParsedCommandLine AutomationToolCommandLine, StartupTraceListener StartupListener, HashSet`1 ScriptModuleAssemblies)
(see C:\Users\user\AppData\Roaming\Unreal Engine\AutomationTool\Logs\E+Program+Files+Epic+Games+UE_5.7\Log.txt for full exception trace)
NullReferenceException: Object reference not set to an instance of an object.
at AutomationTool.Platform.GetFilesToArchive(ProjectParams Params, DeploymentContext SC)
at AutomationScripts.Project.CreateArchiveManifest(ProjectParams Params, DeploymentContext SC) in E:\Program Files\Epic Games\UE_5.7\Engine\Source\Programs\AutomationTool\Scripts\ArchiveCommand.Automation.cs:line 26
at AutomationScripts.Project.Archive(ProjectParams Params) in E:\Program Files\Epic Games\UE_5.7\Engine\Source\Programs\AutomationTool\Scripts\ArchiveCommand.Automation.cs:line 71
at BuildCookRun.DoBuildCookRun(ProjectParams Params) in E:\Program Files\Epic Games\UE_5.7\Engine\Source\Programs\AutomationTool\Scripts\BuildCookRun.Automation.cs:line 262
at BuildCookRun.ExecuteBuild() in E:\Program Files\Epic Games\UE_5.7\Engine\Source\Programs\AutomationTool\Scripts\BuildCookRun.Automation.cs:line 43
at AutomationTool.BuildCommand.Execute()
at AutomationTool.BuildCommand.ExecuteAsync()
at AutomationTool.Automation.ExecuteAsync(List`1 CommandsToExecute, Dictionary`2 Commands)
at AutomationTool.Automation.ExecuteAsync(List`1 CommandsToExecute, Dictionary`2 Commands)
at AutomationTool.Automation.ProcessAsync(ParsedCommandLine AutomationToolCommandLine, StartupTraceListener StartupListener, HashSet`1 ScriptModuleAssemblies)
==============================================================================
AutomationTool executed for 0h 3m 29s
AutomationTool exiting with ExitCode=1 (Error_Unknown)
Why is that, and how can I fix it?
Hello there!
Checking around the community, this is quite a tricky scenario.
First, the fact that you are disabling Paks in 5.6, yet the files are created anyway. This seems to be a recurring problen when using Windows pack settings. Most user use Development Package as a workaround. Alternatively, the Loose Files option might be legacy in 5.6, but it’s still fully supported in 5.5. If you can afford the rollback, you should be able to get the build working with no Pak using that option.
Now, for the 5.7 error. This engine version was released days ago, and might still be prone to unexpected behaviours. Following just the error, I would test using package project instead, and make sure that Stage is enabled, and that it runs before Archive.
Also, it’s always recommended to review the UE docs tied to the issue, just in case: