Errors when packaging for Windows

Quest · February 13, 2024, 1:59pm

I’m getting this error when packaging my project in Unreal.
there’s a bit more to the errors but I didn’t want to overload the chat here.

was hoping I could get some help here.
I removed the access tokens.

UATHelper: Packaging (Windows): LogCesium: Error: [2024-02-13 06:09:08.222] [error] [ErrorList.h:72] Errors when loading tileset:
UATHelper: Packaging (Windows): - Received status code 401 for asset response https://api.cesium.com/v1/assets/1/endpoint?access_token=
UATHelper: Packaging (Windows): LogCesium: Error: [2024-02-13 06:09:08.222] [error] [ErrorList.h:72] Errors when loading tileset:
UATHelper: Packaging (Windows): - Received status code 401 for asset response https://api.cesium.com/v1/assets/96188/endpoint?access_token=
UATHelper: Packaging (Windows): LogCesium: Error: [2024-02-13 06:09:08.222] [error] [RasterOverlayCollection.cpp:127] Assets used with a raster overlay must have type ‘IMAGERY’, but instead saw ‘unknown’.
UATHelper: Packaging (Windows): LogCesium: Error: [2024-02-13 06:09:08.222] [error] [ErrorList.h:72] Errors when loading tileset:
UATHelper: Packaging (Windows): - Received status code 401 for asset response https://api.cesium.com/v1/assets/354307/endpoint?access_token=

UATHelper: Packaging (Windows): ERROR: Cook failed.
PackagingResults: Error: Unknown Cook Failure

I’m not sure if it’s related but I also get an error when I build the lighting:

=== Lightmass crashed: ===
Assertion failed: (Index >= 0) & (Index < ArrayNum) [File:D:\build++UE5\Sync\Engine\Source\Runtime\Core\Public\Containers\Array.h] [Line: 752]
Array index out of bounds: 969 from an array of size 969
0x00007ff78bb99af3 UnrealLightmass.exe!Lightmass::FStaticMeshLOD::GetIndex()
0x00007ff78bb9af9d UnrealLightmass.exe!Lightmass::FStaticMeshStaticLightingMesh::GetTriangleIndices()
0x00007ff78bb0b3c9 UnrealLightmass.exe!Lightmass::FEmbreeGeometry::FEmbreeGeometry()
0x00007ff78bb1516a UnrealLightmass.exe!Lightmass::FEmbreeAggregateMesh::AddMesh()
0x00007ff78bb6a8f0 UnrealLightmass.exe!Lightmass::FStaticLightingSystem::FStaticLightingSystem()
0x00007ff78bb1bd71 UnrealLightmass.exe!Lightmass::BuildStaticLighting()
0x00007ff78bb410eb UnrealLightmass.exe!Lightmass::LightmassMain()
0x00007ff78bb63410 UnrealLightmass.exe!main()
0x00007ff78bbd16cc UnrealLightmass.exe!__scrt_common_main_seh()
0x00007ffda1257344 KERNEL32.DLL!UnknownFunction
0x00007ffda29826b1 ntdll.dll!UnknownFunction

0x00007ff78bb99af3 UnrealLightmass.exe!Lightmass::FStaticMeshLOD::GetIndex()
0x00007ff78bb9af9d UnrealLightmass.exe!Lightmass::FStaticMeshStaticLightingMesh::GetTriangleIndices()
0x00007ff78bb0b3c9 UnrealLightmass.exe!Lightmass::FEmbreeGeometry::FEmbreeGeometry()
0x00007ff78bb1516a UnrealLightmass.exe!Lightmass::FEmbreeAggregateMesh::AddMesh()
0x00007ff78bb6a8f0 UnrealLightmass.exe!Lightmass::FStaticLightingSystem::FStaticLightingSystem()
0x00007ff78bb1bd71 UnrealLightmass.exe!Lightmass::BuildStaticLighting()
0x00007ff78bb410eb UnrealLightmass.exe!Lightmass::LightmassMain()
0x00007ff78bb63410 UnrealLightmass.exe!main()
0x00007ff78bbd16cc UnrealLightmass.exe!__scrt_common_main_seh()
0x00007ffda1257344 KERNEL32.DLL!UnknownFunction
0x00007ffda29826b1 ntdll.dll!UnknownFunction

Quest · February 13, 2024, 2:31pm

I also notice that most of these are 401 errs but one stood out which was a 400:

UATHelper: Cooking (Windows): LogInit: Display: LogCesium: Error: [2024-02-13 07:13:32.694] [error] [ErrorList.h:72] Errors when loading tileset:
UATHelper: Cooking (Windows): - Received status code 400 for tileset https://tile.googleapis.com/v1/3dtiles/root.json?key=

Quest · February 13, 2024, 2:33pm

perhaps is this because I should be using cesium ion instead of from url?
I’m not quite sure the difference but it seemed like it could be related.

Quest · February 14, 2024, 12:13am

here are some errors I get when cooking the project:

Kevin_Ring · February 15, 2024, 5:50am

Those errors make me think your level is simply misconfigured. Especially this one:

Assets used with a raster overlay must have type ‘IMAGERY’, but instead saw ‘unknown’.

Those errors pop up while it’s cooking a particular level, presumably. Can you try opening that same level in the Editor and see if you get similar errors? If so, and you’re not sure how to fix it, share how the Cesium objects in your level are configured.

Quest · February 22, 2024, 11:44am

just replying here to show that the issue was resolved in another thread:

Topic		Replies	Views
使用ue5.1打包失败了，请问是什么问题 Cesium for Unreal	2	583	June 2, 2023
Error while opening a cooked package - UE5 Cesium for Unreal	1	414	May 4, 2022
Packaging error unable to build shader Cesium for Unreal	9	3171	September 22, 2023
How to fix this package error? Cesium for Unreal	1	2010	May 23, 2022
Cesium Tile Loads fail with http 401 during CI build Cesium for Unreal	6	53	January 7, 2025

Errors when packaging for Windows

Related topics