Failing to Cook Content for Windows

What does the cook log say? It’s in C:\Users\Brett\AppData\Roaming\Unreal Engine\AutomationTool\Logs\E+Unreal+Engine+4.6\Cook.txt (according to that output log)

Hello there,

I’m currently attempting to package a project for a class assignment, but I cannot get past the “Cook Content” step, and my cook fails every time. Here are the last lines of code from the output log:

MainFrameActions: Cooking (Windows): CommandUtils.Run: Run: Took 321.2143724s to run UE4Editor-Cmd.exe, ExitCode=1
MainFrameActions: Cooking (Windows): Project.Cook: Cook failed. Deleting cooked data.
MainFrameActions: Cooking (Windows): ErrorReporter.Error: ERROR: AutomationTool error: Cook failed.
MainFrameActions: Cooking (Windows): BuildCommand.Execute: ERROR: BUILD FAILED
MainFrameActions: Cooking (Windows): Program.Main: ERROR: AutomationTool terminated with exception:
MainFrameActions: Cooking (Windows): Program.Main: ERROR: Exception in AutomationScripts.Automation: BUILD FAILED: Failed while running Cook for E:\Unreal Projects\Huco616Clone\Huco616Clone.uproject; see log C:\Users\Brett\AppData\Roaming\Unreal Engine\AutomationTool\Logs\E+Unreal+Engine+4.6
MainFrameActions: Cooking (Windows): Cook.txt
MainFrameActions: Cooking (Windows): Stacktrace: at Project.Cook(ProjectParams Params)
MainFrameActions: Cooking (Windows): at BuildCookRun.DoBuildCookRun(ProjectParams Params)
MainFrameActions: Cooking (Windows): at BuildCommand.Execute()
MainFrameActions: Cooking (Windows): at AutomationTool.Automation.Execute(List1 CommandsToExecute, CaselessDictionary1 Commands)
MainFrameActions: Cooking (Windows): at AutomationTool.Automation.Process(String[] CommandLine)
MainFrameActions: Cooking (Windows): at AutomationTool.Program.MainProc(Object Param)
MainFrameActions: Cooking (Windows): at AutomationTool.InternalUtils.RunSingleInstance(MainProc Main, Object Param)
MainFrameActions: Cooking (Windows): at AutomationTool.Program.Main()
MainFrameActions: Cooking (Windows): Program.Main: ERROR: BUILD FAILED: Failed while running Cook for E:\Unreal Projects\Huco616Clone\Huco616Clone.uproject; see log C:\Users\Brett\AppData\Roaming\Unreal Engine\AutomationTool\Logs\E+Unreal+Engine+4.6\Cook.txt
MainFrameActions: Cooking (Windows): ProcessManager.KillAll: Trying to kill 0 spawned processes.
MainFrameActions: Cooking (Windows): Program.Main: AutomationTool exiting with ExitCode=25
MainFrameActions: Cooking (Windows): Domain_ProcessExit
MainFrameActions: Cooking (Windows): ProcessManager.KillAll: Trying to kill 0 spawned processes.
MainFrameActions: Cooking (Windows): copying UAT log files…
MainFrameActions: Cooking (Windows): RunUAT.bat ERROR: AutomationTool was unable to run successfully.
MainFrameActions: Cooking (Windows): BUILD FAILED

Now, I can launch the game in a standalone just fine from the engine. However, I do have errors when I build, but they are about UV’s overlapping and attempting to reference assets that I have deleted. Is this what is keeping me from being able to package it? If so, is there a way to ignore these errors?

Any help would be greatly appreciated.

Did you delete the unused assets from within the UE content browser, or just from a file window in your OS? If it’s the latter, then I’d imagine a lot of references ended up with a bunch of loose ends.

I deleted the additional levels through the file window, but all of the assets from the content browser.

I’m no expert at this stuff, but it looks like errors are coming from an attempt to find/reference items in Unreal that I deleted.

In order to make the export quicker, more efficient, and the file smaller, I copied my previous game project, and deleted all of the levels and assets that I was not using. But it looks like now it is trying to access these items. Is there any way around this?
link text

By the way, attached is the cook log.

Hi!

Are you still seeing this issue? Have you updated to the newest version of the editor? We are at 4.7.5 now.

Hi bnisbet,

We did not hear back from you in response to this issue, so we are marking this post as Resolved for tracking purposes. If you are still experiencing the issue you reported, please respond to this message with additional information and we will offer further assistance.

Thank you.