We’re aware that many users are experiencing issues with loading 3D Tiles in packaged Unreal apps, including those that have been packaged several releases ago. We sincerely apologize for the inconvenience.
Our AWS certificates were renewed this week, and we suspect that this is the problem. If you’re experiencing this issue, please try the following workarounds:
Clearing the DNS cache on the machine.
Delete the cesium-request-cache.sqlite file. I believe this is located in the Engine folder used by the packaged app.
Please let us know whether these do or do not work for you. I would hate to suggest repackaging the app to all of our users, but it may be a worthy last resort if the app can’t be fixed in its current state.
We will continue to watch for these reports throughout the day and determine if there are any more conclusive solutions we can provide. Thank you everyone for raising awareness about these issues and for your patience.
One more thing to add. After flushing the DNS cache, please restart the machine as well. The reboot will force the machine to let go of anything that could be trying to hold onto open certifications.
Please let us know if you’re still running into issues after these steps. Thank you for your patience thus far.
I have tried the above steps, and I am still unable to get Ion tilesets to load in a packaged game.
I flushed the dns, deleted the database in the packaged game and then restarted my machine.
I will try repackaging now.
Edit, Repackaging did not fix the issue.
@ZenithEdge (and anyone else still experiencing problems), can you please let us know where you’re located? That will help us understand if certain edge locations are the problem. You can message me privately if you prefer not to say publicly.
Thanks @ZenithEdge! Can you also try adding these lines to your configuration and send me the log:
[Core.Log]
LogHttp=VeryVerbose
In a built application, you can add these lines to the end of [project name]/Saved/Config/Windows/Engine.ini. That’s assuming you’re on Windows (are you?).
Thanks for sharing your logs @ZenithEdge. I can’t reproduce your problem, even when configuring my system to talk to the particular CloudFront edge location that you’re using. Is there any chance that your corporate IT has modified your list of trusted certificate authorities?
The only other thing that jumps out at me is that you’re on Windows 11 22H2, which is slightly old, but I don’t know of any reason that that would be a problem.
@steadystefano0605 please share your logs as well. The more examples of the problem we can see, the more likely we are to be able to spot the commonality.
Which is caused by a combination of this change on AWS:
Plus some missing updates or misconfiguration on your system.
If so, the troubleshooting steps in the first link should help. I’ll quote them here:
Players may be experiencing connection issues because “Starfield Services Root Certificate Authority - G2” is not installed on their systems, which is causing the SSL certificate validation to fail.
We expected this root certificate to be available on up-to-date Windows systems or to be installed automatically via Windows’ Auto-Root Certificate Retrieval feature. However, some players are experiencing connection issues due to this certificate not being present.
Possible reasons include:
Outdated Windows systems that haven’t received recent root certificate updates.
Auto-root certificate retrieval is disabled in system settings or group policies.
Network restrictions prevent Windows from fetching the missing root certificate.
It is possible to check if the “Starfield Services Root Certificate Authority - G2” is installed on your Windows system by doing the following:
Press the Windows Key + R to open the Run dialog.
Type certmgr.msc and press Enter.
In the left panel, navigate to Trusted Root Certification Authorities → Certificates.
Look for Starfield Services Root Certificate Authority - G2 in the list as shown in this image.
LogPluginManager: Mounting Engine plugin CesiumForUnreal
LogPluginManager: Found config from plugin[CesiumForUnreal] E:/Projects/ExpanseProject/MyProject/Saved/Config/WindowsEditor/Editor.ini
LogPluginManager: Found config from plugin[CesiumForUnreal] Engine
19B946A8709F4309D7CC4E5FC6044ADB1684FBEF19B946A8709F4309D7CC4E5FC6044AD_FWaterVertexFactoryWithSelectionWithIndirectC5746E15D6AF88B3C8967DC47D7FF57AA98C4058FFF1837A5730F4CB2E1C8D75C2A9C8B36A4E5D26_FMeshParticleVertexFactory8E5462CD108F3ACF9C2D93B79DB64B3906833D1AF773920348F231C490A74B1A551F8CE3ABF04791_FCesiumPointAttenuationVertexFactoryFD165BE6F990F4243CB13F6A57EFAAA76778D8DCC8E67C27A64AE201DFA6C7409BEA87B97017C9DA_FInstancedStaticMeshVertexFactory1808145E713BFCB3CC3257922C12D5C1B321869739A00A3AF8434811E9EA9890B934C37C364D15CD39A00A3AF8434811E9EA9890B934C37C364D15CD39A00A3AF8434811E9EA9890B9
LogClass: Error: StructProperty FCesiumSampleHeightResult::LongitudeLatitudeHeight is not initialized properly. Module:CesiumRuntime File:Public/CesiumSampleHeightResult.h
LogClass: Error: BoolProperty FCesiumSampleHeightResult::SampleSuccess is not initialized properly. Module:CesiumRuntime File:Public/CesiumSampleHeightResult.h
LogAutomationTest: Error: LogClass: StructProperty FCesiumSampleHeightResult::LongitudeLatitudeHeight is not initialized properly. Module:CesiumRuntime File:Public/CesiumSampleHeightResult.h [log]
LogAutomationTest: Error: LogClass: BoolProperty FCesiumSampleHeightResult::SampleSuccess is not initialized properly. Module:CesiumRuntime File:Public/CesiumSampleHeightResult.h [log]
LogCesium: Display: Caching Cesium requests in C:/Users/shida/AppData/Local/UnrealEngine/5.4/cesium-request-cache.sqlite
LogCesium: Loading tileset for asset ID 2275207
LogCesium: Loading tileset for asset ID 2275207 done
UATHelper: Packaging (Windows): C:\UE_5.4\UE_5.4\Engine\Plugins\Marketplace\CesiumForUnreal\Source\CesiumRuntime\CesiumRuntime.Build.cs(147,31): warning CS0618: ‘EngineIncludeOrderVersion.Unreal5_2’ is obsolete: ‘The Unreal 5.2 include order is deprecated and will be unsupported in 5.5.’
UATHelper: Packaging (Windows): C:\UE_5.4\UE_5.4\Engine\Plugins\Marketplace\CesiumForUnreal\Source\CesiumEditor\CesiumEditor.Build.cs(123,31): warning CS0618: ‘EngineIncludeOrderVersion.Unreal5_2’ is obsolete: ‘The Unreal 5.2 include order is deprecated and will be unsupported in 5.5.’
31CC93ACB2AFCB9C42E7DC41_FLandscapeXYOffsetVertexFactory9C72E626AD265877B69662468B699912974F6255B1684FBEF19B946A8709F4309D7CC4E5FC6044ADEBA49461CECB1EA5D21E2BF8918B91C7C3994DCEB1684FBEF19B946A8709F4309D7CC4E5FC6044ADB1684FBEF19B946A8709F4309D7CC4E5FC6044AD_FWaterVertexFactoryWithSelectionWithIndirectC5746E15D6AF88B3C8967DC47D7FF57AA98C4058FFF1837A5730F4CB2E1C8D75C2A9C8B36A4E5D26_FMeshParticleVertexFactory8E5462CD108F3ACF9C2D93B79DB64B3906833D1AF773920348F231C490A74B1A551F8CE3ABF04791_FCesiumPointAttenuationVertexFactoryFD165BE6F990F4243CB13F6A57EFAAA76778D8DCC8E67C27A64AE201DFA6C7409BEA87B9701
79DB64B3906833D1AF773920348F231C490A74B1A551F8CE3ABF04791_FCesiumPointAttenuationVertexFactoryFD165BE6F990F4243CB13F6A57EFAAA76778D8DCC8E67C27A64AE201DFA6C7409BEA87B97017C9DA_FInstancedStaticMeshVertexFactory1808145E713BFCB3CC3257922C12D5C1B321869739A00A3AF8434811E9EA9890B934C37C364D15CD39A00A3AF8434811E9EA9890B934C37C364D15CD39A00A3AF8434811E9EA9890B934C37C364D15CD39A00A3AF8434811E9EA9890B934C37C364D15CD_FSplineMeshVertexFactory1808145E713BFCB3CC3257922C12D5C1B3218697A747D67BD07743C1BEA1DE549F682B82EB7B9965A747D67BD07743C1BEA1DE549F682B82EB7B9965A747D67BD07743C1BEA1DE549F682B82EB7B9965_FLocal
UATHelper: Packaging (Windows): LogCesium: Warning: “Enable World Bounds Checks” in the world settings is currently enabled. Please consider disabling it to avoid potential issues.
UATHelper: Packaging (Windows): LogCesium: Display: Caching Cesium requests in C:/Users/shida/AppData/Local/UnrealEngine/5.4/cesium-request-cache.sqlite
There are some hints that the problems might be caused by certain network protection tools - specifically, certain forms of antivirus software that mess around with certificate chains.
If you are encountering the problem, then it could be helpful if you post a message here, saying which antivirus/network protection software you are using. Maybe it’s possble to spot a pattern there.
And iff (if and only if) it is possible in your environment, you might try to temporarily disable this software, start the application, and see whether the tiles appear then. (And then, immediately enable the software again).
I can confirm that installing that cert manually fixed my issue. I am able to get imagery in my packaged game now.
I did a windows update but that didnt give me the cert, so I had to grab it from here:
(Edited: Removed the link - see the following post)
Not sure if I am allowed to post the link, please let me know and I will delete.
