UE5.2.1 Packaging error:Unknown Cook Failure .Could I trouble you to help?Thanks.
yanccee opened this issue · 2 comments
I am still in process in UE5 learning,and I just instaled the Visual Studio 2022.
However,when I was packaging it as the course of the study,it errored.
Could I trouble you to help?Thanks again.
This is the ending of the log:
UATHelper: 打包 (Windows): LogShaderCompilers: Display: === FShaderJobCache stats ===
UATHelper: 打包 (Windows): LogShaderCompilers: Display: Total job queries 0, among them cache hits 0 (0.00%)
UATHelper: 打包 (Windows): LogShaderCompilers: Display: Tracking 0 distinct input hashes that result in 0 distinct outputs (0.00%)
UATHelper: 打包 (Windows): LogShaderCompilers: Display: RAM used: 240.00 B of 819.20 MiB budget. Usage: 0.00%
UATHelper: 打包 (Windows): LogShaderCompilers: Display: === Shader Compilation stats ===
UATHelper: 打包 (Windows): LogShaderCompilers: Display: Shaders Compiled: 0
UATHelper: 打包 (Windows): LogShaderCompilers: Display: Jobs assigned 0, completed 0 (0.00%)
UATHelper: 打包 (Windows): LogShaderCompilers: Display: Time at least one job was in flight (either pending or executed): 0.00 s
UATHelper: 打包 (Windows): LogShaderCompilers: Display: ================================================
UATHelper: 打包 (Windows): Took 18.1252s to run UnrealEditor-Cmd.exe, ExitCode=1
UATHelper: 打包 (Windows): ERROR: Cook failed.
UATHelper: 打包 (Windows): (see C:\Users\ZryYanc_\AppData\Roaming\Unreal Engine\AutomationTool\Logs\C+Program+Files+Epic+Games+UE_5.2\Log.txt for full exception trace)
UATHelper: 打包 (Windows): AutomationTool executed for 0h 0m 18s
UATHelper: 打包 (Windows): AutomationTool exiting with ExitCode=25 (Error_UnknownCookFailure)
UATHelper: 打包 (Windows): BUILD FAILED
PackagingResults: Error: Unknown Cook Failure
This is the former log：
C:\GameExploitation\UEProject\Demo2_zhangliang002_2024.8\Demo2\Content\Resources\Effects_Particles\FXVarietyPack\EpicContent\Materials\M_DemoWallPattern.uasset: Failed to compile Material for platform PCD3D_SM6, Default Material will be used in game.
UATHelper: 打包 (Windows): (Node TextureSample) Texture Sample> Missing input texture
UATHelper: 打包 (Windows): (Node TextureSample) Texture Sample> Missing input texture
UATHelper: 打包 (Windows): LogInit: Display: LogMaterial: Warning: [AssetLog] C:\GameExploitation\UEProject\Demo2_zhangliang002_2024.8\Demo2\Content\Resources\Effects_Particles\FXVarietyPack\EpicContent\Materials\M_DemoWallPattern.uasset: Failed to compile Material for platform PCD3D_SM5, Default Material will be used in game.
UATHelper: 打包 (Windows): (Node TextureSample) Texture Sample> Missing input texture
UATHelper: 打包 (Windows): (Node TextureSample) Texture Sample> Missing input texture
UATHelper: 打包 (Windows): LogInit: Display: LogMaterial: Warning: [AssetLog] C:\GameExploitation\UEProject\Demo2_zhangliang002_2024.8\Demo2\Content\Resources\Effects_Particles\FXVarietyPack\EpicContent\Materials\M_DemoRoomTiles.uasset: Failed to compile Material for platform PCD3D_SM6, Default Material will be used in game.
UATHelper: 打包 (Windows): (Node TextureSample) Texture Sample> Missing input texture
UATHelper: 打包 (Windows): (Node TextureSample) Texture Sample> Missing input texture
UATHelper: 打包 (Windows): LogInit: Display: LogMaterial: Warning: [AssetLog] C:\GameExploitation\UEProject\Demo2_zhangliang002_2024.8\Demo2\Content\Resources\Effects_Particles\FXVarietyPack\EpicContent\Materials\M_DemoRoomTiles.uasset: Failed to compile Material for platform PCD3D_SM5, Default Material will be used in game.
UATHelper: 打包 (Windows): (Node TextureSample) Texture Sample> Missing input texture
UATHelper: 打包 (Windows): (Node TextureSample) Texture Sample> Missing input texture
UATHelper: 打包 (Windows): LogInit: Display: LogMaterial: Warning: Cooking a material resource (in M_DemoWallPattern hierarchy) that doesn't have a valid ShaderMap! Shadermap pointer is null.
UATHelper: 打包 (Windows): LogInit: Display: NOTE: Only first 50 warnings displayed.
UATHelper: 打包 (Windows): LogInit: Display:
UATHelper: 打包 (Windows): LogInit: Display: Failure - 9 error(s), 129 warning(s)
UATHelper: 打包 (Windows): LogInit: Display:
UATHelper: 打包 (Windows): Execution of commandlet took: 9.27 seconds
UATHelper: 打包 (Windows): LogShaderCompilers: Display: ================================================
UATHelper: 打包 (Windows): LogShaderCompilers: Display: === FShaderJobCache stats ===
UATHelper: 打包 (Windows): LogShaderCompilers: Display: Total job queries 0, among them cache hits 0 (0.00%)
UATHelper: 打包 (Windows): LogShaderCompilers: Display: Tracking 0 distinct input hashes that result in 0 distinct outputs (0.00%)
UATHelper: 打包 (Windows): LogShaderCompilers: Display: RAM used: 240.00 B of 819.20 MiB budget. Usage: 0.00%
UATHelper: 打包 (Windows): LogShaderCompilers: Display: === Shader Compilation stats ===
UATHelper: 打包 (Windows): LogShaderCompilers: Display: Shaders Compiled: 0
UATHelper: 打包 (Windows): LogShaderCompilers: Display: Jobs assigned 0, completed 0 (0.00%)
UATHelper: 打包 (Windows): LogShaderCompilers: Display: Time at least one job was in flight (either pending or executed): 0.00 s
UATHelper: 打包 (Windows): LogShaderCompilers: Display: ================================================
UATHelper: 打包 (Windows): Took 18.1252s to run UnrealEditor-Cmd.exe, ExitCode=1
UATHelper: 打包 (Windows): ERROR: Cook failed.
UATHelper: 打包 (Windows): (see C:\Users\ZryYanc_\AppData\Roaming\Unreal Engine\AutomationTool\Logs\C+Program+Files+Epic+Games+UE_5.2\Log.txt for full exception trace)
UATHelper: 打包 (Windows): AutomationTool executed for 0h 0m 18s
UATHelper: 打包 (Windows): AutomationTool exiting with ExitCode=25 (Error_UnknownCookFailure)
UATHelper: 打包 (Windows): BUILD FAILED
PackagingResults: Error: Unknown Cook Failure
This might have nothing to do with Cesium; you should carefully review the log files to look for other causes.
Yeah @yanccee from the log it looks like a problem with some materials in a plugin called FXVarietyPack, nothing obvious to do with Cesium. So I'm going to close this issue, but if you do think it's Cesium related, please start a thread on the community forum instead of making a GitHub issue, and include as much detail as you can, particularly around what makes you think it's Cesium-related.