Ue4 error cook failed

1 vote and 7 comments so far on Reddit

UATHelper: Packaging (Windows (32-bit)): LogInit: Display: Warning/Error Summary (Unique only)

UATHelper: Packaging (Windows (32-bit)): LogInit: Display: ————————————

UATHelper: Packaging (Windows (32-bit)): LogInit: Display: LogNavigation: Error: [/Script/Engine.RecastNavMesh] found in the DefaultEngine.ini file. This class has been moved. Please rename that section to [/Script/NavigationSystem.RecastNavMesh]

UATHelper: Packaging (Windows (32-bit)): LogInit: Display: LogProperty: Error: UStructProperty::Serialize Loading: Property ‘StructProperty /Game/TowerDefenseStarterKit/Blueprints/WaveSpawningSystems/BP_BatchedWaveSpawnController.BP_BatchedWaveSpawnController_C:LinkWaveSpawnDataToDataTableEntries.CallFunc_GetDataTableRowFromName_OutRow’. Unknown structure.

UATHelper: Packaging (Windows (32-bit)): LogInit: Display: LogProperty: Error: UStructProperty::Serialize Loading: Property ‘StructProperty /Game/TowerDefenseStarterKit/Blueprints/WaveSpawningSystems/BP_WeightedWaveSpawnController.BP_WeightedWaveSpawnController_C:RunBotSpawningSystem.CallFunc_GetDataTableRowFromName_OutRow’. Unknown structure.

UATHelper: Packaging (Windows (32-bit)): LogInit: Display: LogProperty: Error: UStructProperty::Serialize Loading: Property ‘StructProperty /Game/TowerDefenseStarterKit/Blueprints/WaveSpawningSystems/BP_WeightedWaveSpawnController.BP_WeightedWaveSpawnController_C:PrepareAISpawnWeightDistArrayForNewWave.CallFunc_GetDataTableRowFromName_OutRow’. Unknown stru

cture.

UATHelper: Packaging (Windows (32-bit)): LogInit: Display: LogProperty: Error: UStructProperty::Serialize Loading: Property ‘StructProperty /Game/TowerDefenseStarterKit/Blueprints/WaveSpawningSystems/BP_WeightedWaveSpawnController.BP_WeightedWaveSpawnController_C:SortAISpawnDataInIncreasingThreatOrder.CallFunc_GetDataTableRowFromName_OutRow’. Unknown struc

ture.

UATHelper: Packaging (Windows (32-bit)): LogInit: Display: LogProperty: Error: UStructProperty::Serialize Loading: Property ‘StructProperty /Game/TowerDefenseStarterKit/Blueprints/WaveSpawningSystems/BP_WeightedWaveSpawnController.BP_WeightedWaveSpawnController_C:LinkAISpawnDataToDataTableEntries.CallFunc_GetDataTableRowFromName_OutRow’. Unknown structure.

UATHelper: Packaging (Windows (32-bit)): LogInit: Display: LogUObjectGlobals: Warning: Class /Script/Engine.NavigationSystem is not a child class of Class /Script/Engine.NavigationSystemBase

UATHelper: Packaging (Windows (32-bit)): LogInit: Display: CookResults: Warning: Unable to find package for cooking /Game/TowerDefenseStarterKit/Maps/Map_DynamicNavMeshPathDemo

UATHelper: Packaging (Windows (32-bit)): LogInit: Display: LogCook: Warning: Unable to find package for cooking /Game/TowerDefenseStarterKit/Maps/Map_DynamicNavMeshPathDemo

UATHelper: Packaging (Windows (32-bit)): LogInit: Display: LogLinker: Warning: Unable to load PhysicsSerializer with outer InstancedStaticMeshComponent /Game/TowerDefenseStarterKit/Blueprints/GameplayActors/BP_GridGenerator.BP_GridGenerator_C:GridCell_GEN_VARIABLE because its class does not exist

UATHelper: Packaging (Windows (32-bit)): LogInit: Display: LogLinker: Warning: Unable to load PhysicsSerializer with outer InstancedStaticMeshComponent /Game/TowerDefenseStarterKit/Blueprints/GameplayActors/BP_GridCellDetector.BP_GridCellDetector_C:GridCellHighlighter_GEN_VARIABLE because its class does not exist

UATHelper: Packaging (Windows (32-bit)): LogInit: Display:

UATHelper: Packaging (Windows (32-bit)): LogInit: Display: Failure — 6 error(s), 5 warning(s)

UATHelper: Packaging (Windows (32-bit)): LogInit: Display:

UATHelper: Packaging (Windows (32-bit)):

UATHelper: Packaging (Windows (32-bit)): Execution of commandlet took: 7.50 seconds

UATHelper: Packaging (Windows (32-bit)): Took 18.9222119s to run UE4Editor-Cmd.exe, ExitCode=1

UATHelper: Packaging (Windows (32-bit)): ERROR: Cook failed.

UATHelper: Packaging (Windows (32-bit)): (see C:UsersRoHilAppDataRoamingUnreal EngineAutomationToolLogsD+Program+Files+Epic+Games+UE_4.20Log.txt for full exception trace)

UATHelper: Packaging (Windows (32-bit)): AutomationTool exiting with ExitCode=25 (Error_UnknownCookFailure)

UATHelper: Packaging (Windows (32-bit)): BUILD FAILED

PackagingResults: Error: Unknown Cook Failure

Вот такое вылазит при сборке
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: NOTE: Only first 50 warnings displayed.
UATHelper: Packaging (Windows (64-bit)): LogInit: Display:
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: Failure — 103 error(s), 3932 warning(s)
UATHelper: Packaging (Windows (64-bit)): LogInit: Display:
UATHelper: Packaging (Windows (64-bit)):
UATHelper: Packaging (Windows (64-bit)): Execution of commandlet took: 1727.73 seconds
UATHelper: Packaging (Windows (64-bit)): Took 1781,793983s to run UE4Editor-Cmd.exe, ExitCode=1
UATHelper: Packaging (Windows (64-bit)): Cook failed. Deleting cooked data.
UATHelper: Packaging (Windows (64-bit)): ERROR: Cook failed.
UATHelper: Packaging (Windows (64-bit)): (see C:UsersComputer EgoraAppDataRoamingUnreal EngineAutomationToolLogsD+UE_4.18UAT_Log.txt for full exception trace)
UATHelper: Packaging (Windows (64-bit)): AutomationTool exiting with ExitCode=25 (Error_UnknownCookFailure)
UATHelper: Packaging (Windows (64-bit)): BUILD FAILED
PackagingResults: Error: Unknown Cook Failure

Лог вот:

ProcessResult.StdOut: LogInit: Display:
ProcessResult.StdOut: LogInit: Display: Failure — 103 error(s), 3932 warning(s)
ProcessResult.StdOut: LogInit: Display:
ProcessResult.StdOut:
ProcessResult.StdOut: Execution of commandlet took: 1727.73 seconds
CommandUtils.Run: Took 1781,793983s to run UE4Editor-Cmd.exe, ExitCode=1
InternalUtils.SafeDeleteFile: SafeDeleteFile C:UsersComputer EgoraAppDataRoamingUnreal EngineAutomationToolLogsD+UE_4.18Cook-2018.02.20-16.28.33.txt
InternalUtils.SafeCopyFile: SafeCopyFile D:UE_4.18EngineProgramsAutomationToolSavedCook-2018.02.20-15.58.51.txt C:UsersComputer EgoraAppDataRoamingUnreal EngineAutomationToolLogsD+UE_4.18Cook-2018.02.20-16.28.33.txt
InternalUtils.SafeDeleteFile: SafeDeleteFile D:UE_4.18EngineProgramsAutomationToolSavedCook-2018.02.20-15.58.51.txt
Project.Cook: Cook failed. Deleting cooked data.
ExceptionUtils.PrintExceptionInfo: ==============================================================================
ExceptionUtils.PrintExceptionInfo: ERROR: Cook failed.
ExceptionUtils.PrintExceptionInfo: (see C:UsersComputer EgoraAppDataRoamingUnreal EngineAutomationToolLogsD+UE_4.18UAT_Log.txt for full exception trace)
ExceptionUtils.PrintExceptionInfo:
ExceptionUtils.PrintExceptionInfo: CommandletException: Editor terminated with exit code 1 while running Cook for D:Unreal ProjectsGPGP.uproject; see log C:UsersComputer EgoraAppDataRoamingUnreal EngineAutomationToolLogsD+UE_4.18Cook-2018.02.20-16.28.33.txt
ExceptionUtils.PrintExceptionInfo: в AutomationTool.CommandUtils.RunCommandlet(FileReference ProjectName, String UE4Exe, String Commandlet, String Parameters)
ExceptionUtils.PrintExceptionInfo: в AutomationTool.CommandUtils.CookCommandlet(FileReference ProjectName, String UE4Exe, String[] Maps, String[] Dirs, String InternationalizationPreset, String[] CulturesToCook, String TargetPlatform, String Parameters)
ExceptionUtils.PrintExceptionInfo: в Project.Cook(ProjectParams Params)
ExceptionUtils.PrintExceptionInfo: Wrapped by AutomationException: Cook failed.
ExceptionUtils.PrintExceptionInfo: в Project.Cook(ProjectParams Params)
ExceptionUtils.PrintExceptionInfo: в BuildCookRun.DoBuildCookRun(ProjectParams Params)
ExceptionUtils.PrintExceptionInfo: в BuildCookRun.ExecuteBuild()
ExceptionUtils.PrintExceptionInfo: в AutomationTool.BuildCommand.Execute()
ExceptionUtils.PrintExceptionInfo: в AutomationTool.Automation.Execute(List`1 CommandsToExecute, Dictionary`2 Commands)
ExceptionUtils.PrintExceptionInfo: в AutomationTool.Automation.Process(String[] Arguments)
ExceptionUtils.PrintExceptionInfo: в AutomationTool.Program.MainProc(Object Param)
ExceptionUtils.PrintExceptionInfo: в AutomationTool.InternalUtils.RunSingleInstance(Func`2 Main, Object Param)
ExceptionUtils.PrintExceptionInfo: в AutomationTool.Program.Main()
ExceptionUtils.PrintExceptionInfo: ==============================================================================
Program.Main: AutomationTool exiting with ExitCode=25 (Error_UnknownCookFailure).
Никаких русских букв, имён пользователей нет. Я без понятия почему такое происходит… Помогите пожалуйста)

Packaging failed UE4 Help please #3

Comments

ATHelper: Packaging (Windows (64-bit)): LogInit: Display: NOTE: Only first 50 warnings displayed.
UATHelper: Packaging (Windows (64-bit)): LogInit: Display:
UATHelper: Packaging (Windows (64-bit)): LogInit: Display: Failure — 1 error(s), 302 warning(s)
UATHelper: Packaging (Windows (64-bit)): LogInit: Display:
UATHelper: Packaging (Windows (64-bit)):
UATHelper: Packaging (Windows (64-bit)): Execution of commandlet took: 1144.69 seconds
UATHelper: Packaging (Windows (64-bit)): LogShaderCompilers: Display: === FShaderJobCache stats ===
UATHelper: Packaging (Windows (64-bit)): LogShaderCompilers: Display: Total job queries 0, among them cache hits 0 (0.00%)
UATHelper: Packaging (Windows (64-bit)): LogShaderCompilers: Display: Tracking 0 distinct input hashes that result in 0 distinct outputs (0.00%)
UATHelper: Packaging (Windows (64-bit)): LogShaderCompilers: Display: RAM used: 0.00 MB (0.00 GB) of 409.60 MB (0.40 GB) budget. Usage: 0.00%
UATHelper: Packaging (Windows (64-bit)): LogShaderCompilers: Display:

UATHelper: Packaging (Windows (64-bit)): LogHttp: Display: cleaning up 0 outstanding Http requests.
UATHelper: Packaging (Windows (64-bit)): LogContentStreaming: Display: There are 1 unreleased StreamingManagers
UATHelper: Packaging (Windows (64-bit)): Took 1277,9703187s to run UE4Editor-Cmd.exe, ExitCode=1
UATHelper: Packaging (Windows (64-bit)): ERROR: Cook failed.
UATHelper: Packaging (Windows (64-bit)): (see C:UsersslavaAppDataRoamingUnreal EngineAutomationToolLogsF+UE_4.27Log.txt for full exception trace)
UATHelper: Packaging (Windows (64-bit)): AutomationTool exiting with ExitCode=25 (Error_UnknownCookFailure)
UATHelper: Packaging (Windows (64-bit)): BUILD FAILED
PackagingResults: Error: Unknown Cook Failure

The text was updated successfully, but these errors were encountered:

I’m not sure why there’s «F+UE_4.27» in there. Is your project in a folder named «F+UE_4.27» or something? Project names should contain no spaces or other special characters (like ‘+’).

Источник

Since yesterday I have been unable to cook any projects for windows in the 4.25.3 edition of Unreal Engine. Even a brand new empty project is failing. This was working fine for the first couple of days but today I opened up the last project I was working on and unable to cook content. This is the same for all projects both new and existing.

Note* Building new and existing projects in the standard edition of Unreal 4.25.3 is working successfully just for comparison.

Log file:

UATHelper: Cooking (Windows (64-bit)):   LogWindows: Error: begin: stack for UAT

UATHelper: Cooking (Windows (64-bit)):   LogWindows: Error: === Critical error: ===

UATHelper: Cooking (Windows (64-bit)):   LogWindows: Error:

UATHelper: Cooking (Windows (64-bit)):   LogWindows: Error: Assertion failed: OutputStream [File:E:Build2UnrealEngineEngineSourceRuntimeCorePublicProfilingDebugging/DiagnosticTable.h] [Line: 46] (*Note: This directory location does not exist on my machine)

UATHelper: Cooking (Windows (64-bit)):   LogWindows: Error:

UATHelper: Cooking (Windows (64-bit)):   LogWindows: Error:

UATHelper: Cooking (Windows (64-bit)):   LogWindows: Error:

UATHelper: Cooking (Windows (64-bit)):   LogWindows: Error:

UATHelper: Cooking (Windows (64-bit)):   LogWindows: Error: end: stack for UAT

PackagingResults: Error: begin: stack for UAT

PackagingResults: Error: === Critical error: ===

PackagingResults: Error: Assertion failed: OutputStream [File:E:Build2UnrealEngineEngineSourceRuntimeCorePublicProfilingDebugging/DiagnosticTable.h] [Line: 46] (*Note: This directory location does not exist on my machine.)

PackagingResults: Error: end: stack for UAT

UATHelper: Cooking (Windows (64-bit)): Took 7.0340367s to run UE4Editor-Cmd.exe, ExitCode=3

UATHelper: Cooking (Windows (64-bit)): ERROR: Cook failed.

UATHelper: Cooking (Windows (64-bit)):        (see C:UsersDanielAppDataRoamingUnreal EngineAutomationToolLogsC+Program+Files+Aximmetry+DE+UnrealEngineLog.txt for full exception trace)

PackagingResults: Error: Cook failed.

UATHelper: Cooking (Windows (64-bit)): AutomationTool exiting with ExitCode=25 (Error_UnknownCookFailure)

UATHelper: Cooking (Windows (64-bit)): BUILD FAILED

________________________________________________________________________________________________________

I have been through all of the log files and they just come back with the same error codes and nothing obvious. There are no other errors prior to this one.

This is affecting all projects relating to aximmetry DE. Projects on regular Epic 4.25.3 are working fine.

I have also been through and disabled all plugins in a set of tests but no improvement.

I have completely removed and reinstalled Aximmetry DE, and Unreal for Aximmetry, as well as manually delete all of the working directories such as those found under approaming.

Reinstalled, restarted, fresh project, etc. Nothing seems to resolve the problem.

Thanks

Package and Deployment Troubleshooting — Epic Wiki

# Package and Deployment Troubleshooting

This page is currently under construction, more errors and solutions will be added over time.

# Contents

  • 1 Additional Resources
  • 2 Using Answerhub for Packaging Issues
    • 2.1 Packaging Failed (Automation Tool Unable to Run Successfully)
    • 2.2 Searching for your error
    • 2.3 Posting on Answerhub
    • 2.4 Retrieving Logs from a packaged game
    • 2.5 What are Unreal Engine 4’s system recommendations?
  • 3 Common errors
    • 3.1 Non-platform specific
    • 3.2 Windows
    • 3.3 Android
    • 3.4 iOS
    • 3.5 HTML5
    • 3.6 Mac
    • 3.7 TVOS
    • 3.8 Additional Resources
    • 3.9 Miscellaneous Links

Packaging and Deployment Troubleshooting

# Additional Resources

Here are a few helpful guides:

  • Mobile Development Troubleshooting Guide
  • Packaging Projects Documentation
  • Packaging and Cooking Games Documentation
  • Android Quick Start
  • iOS Quick Start
  • Obtain logs off an Android Device
  • Obtain logs off an iOS Device

This page is currently under development and will be populated as we find more common mobile development bugs/crashes. Thank you for your understanding.

If you notice a build failure in your logs, please try the following first:

  1. Open the log that includes the information about your build failure in a text editor. This can be found in the project’s directory under the Saved/Logs directory.
  2. Use the find function (Ctrl+F) to search for the word «Error» and «Warning»
  3. Make a list of each unique error/warning and attempt to search for other Answerhub posts that mention them (Please take a look further in this guide for more information on common error messages, as well as the information that would likely be needed to diagnose your issue)

If you cannot find another report of the error you’re receiving and are not able to solve the issue, a general all purpose solution can sometimes be to delete the following folders:

  • Intermediate

  • Saved

  • Config

  • Restart your computer if there is an ‘Unknown Cook Failure’

If the above does not help your situation, please look through the rest of this guide for a run down of the troubleshooting process and examples of common errors and solutions

# Using Answerhub for Packaging Issues

The first thing to keep in mind is that there are multiple error messages that are generic that are there to let you know that a process failed but will not give any useful information otherwise. These error messages are two examples of general errors which are stating that the process failed. This could be the result of a multitude of different errors. The best course of action is to search elsewhere in the log for other errors and warnings, as this is likely a symptom of those issues.

A couple more of these types of errors are:

  • RunUAT.bat ERROR: AutomationTool was unable to run
  • Error: Error Unknown Error

# Searching for your error

Once you believe you’ve found the actual error or warning that is causing your problem, try searching for the issue here. If the issue isn’t listed on this page, you can try searching for it in our database. Try searching for your error on the Documentation page as this covers all of our support outlets.

If you are able to find a post that relates to your issue but the information is not helpful or the issue was never resolved, check the Product Version listed. If the Product Version is older than what you are currently using, create a new post (see next section). Otherwise, feel free to post about your issue on the existing page.

# Posting on Answerhub

When posting about a packaging issue on Answerhub, it will be easier for someone to help you when you provide them with as much information as possible. The list below can give you a starting point but any additional information is always helpful.

  • Logs (These are the most important and should be attached as a .txt file)
  • Engine version
  • The exact steps you’ve taken to package.
  • The exact OS version you’re on.
  • Can it be reproduced in a clean project?
  • If it can be reproduced, provide a clear list of steps to reproduce the issue.

# Retrieving Logs from a packaged game

Finding errors that occur in the game that results from a successful package attempt can be done by looking at the warnings in the original packaging log but can also be seen in the logs for the packaged game itself. They can found different locations based off the platform.

  • Windows: PackagedDirectory/ProjectName/Saved/Logs/ProjectName.log
  • Mac: ~/Library/Logs/ProjectName/
  • iOS: Obtain logs off an iOS Device
  • Android: Obtain logs off an Android Device
  • HTML5: To be added
  • Linux: To be added
  • tvOS: To be added

# What are Unreal Engine 4’s system recommendations?

For developing with UE4, we recommend a certain level of hardware for a desired result. UE4 will run on desktops and laptops below these recommendations, but performance may be limited. For more information on these recommendations, please see Recommended Hardware.

# Common errors

This section will provide a list of common errors along with resolved Answerhub links related to the issue as well as possible solutions.

# Non-platform specific

  • Error loading an asset

  • WARNING: Visual C++ 2015 toolchain does not appear to be correctly installed. Please verify that «Common Tools for Visual C++ 2015» was selected when installing Visual Studio 2015.

  • No 32-bit compiler toolchain found in C:Program Files (x86)Microsoft Visual Studio 14.0VCbincl.exe

This is a warning that can cause other errors to occur. This can be resolved by installing the Common Tools for Visual C++ 2015 for Visual Studio 2015. Please see the Answerhub post for steps to do so.

  • No modules found to build. All requested binaries were already part of the installed engine data.

This is a message that points out that you are using a Plugin that requires being compiled but you’re using it in a Blueprint-only project. In this case, there are three options:

  • Find a version of the plugin that does not require compiling, if it exists
  • Disable/Uninstall the plugin
  • Add code to your project (File > New C++ Class…). Please note: This will permanently make the project a code project.

# Windows

  • Shipping — Source Build

Ensure you have built for the type of build you’re packaging: Shipping | Debug | Development

  • Rename the .exe

  • Migrating Files to a New Project

  • An item with the same key has already been added

  • How to create a working Shipping build?

  • Win10: Configurations are not updating on iOS devices via Remote Build

  • Global shader cache-pcd3d-sm5 missing

  • UE4Game.pdb Missing

This may also be resolved by unchecking «Include Debug Files» in your project’s Project Settings under the Packaging section.

  • Cannot find HCAD.lib

  • Unknown Structure Error

  • Fatal Error

  • MSCORLIB ERROR: An item with the same key has already been added

# Android

  • Unable to Deploy to Android

  • Error: C:Unreal ProjectsProjectNameIntermediateAndroidAPKJavaLibsplay-services-ads-9.2.0 is not a valid project (AndroidManifest.xml not found).

# iOS

  • Unable to Launch Code Projects on Windows — Cygwin

  • How to manually remove Mobile Provisions for iOS

  • Windows: C:Users(you)AppDataLocalApple ComputerMobileDevicesProvisioning Profiles

  • Mac: ~/Library/MobileDevice/Provisioning Profiles

  • Crashes on First Launch

  • Distribution Source Build Fails to Package

  • iOS Identifier is Not Matching

  • Code signing is required for product type ‘Application’ in SDK iOS 10.0′

  • In-App Purchase Enabled Apps are Rejected from iOS

  • Provision & Signing Keys Not Found

  • Related documentation: Creating & Importing Provisions

  • iOS 4S Incorrect HUD Scaling

  • Related documentation: Setting Device Profiles

  • AssetPackManifest.plist Errors

# HTML5

  • Issues hosting a HTML5 game online

  • Environment Variables aren’t set for HTML5

  • Trouble Launching Packaged Projects on Certain Sites

  • How to Deploy HTML5 Games on Apache? (4.9)

  • HTML5: Little-Endian Error

  • Failed to run llvm optimizations

  • HTML5 In-Game Complications

  • Related documentation: Levels

# Mac

  • Cooking with a Macbook Pro Hangs

  • Related documentation: Packaging and Cooking Games

# TVOS

  • Error: iOS Incorrect Bundle Identifier

# Additional Resources

  • How to stop UE4 from crashing on its own
  • Mobile Development Troubleshooting Guide
  • Packaging and Cooking Games

# Miscellaneous Links

  • Packaging Fails when using Chunk ID

  • Renaming Target Build

Retrieved from «https://wiki.unrealengine.com/index.php?title=Package_and_Deployment_Troubleshooting&oldid=25394»

Category:

  • Troubleshooting

Понравилась статья? Поделить с друзьями:
  • Ue4 error 0x887a0006
  • Ubuntu журнал ошибок
  • Ue4 atlas fatal error как исправить
  • Ubuntu выдает ошибку при загрузке
  • Ue4 atlas engine fatal error crash