Latest update crash

Ben1 · September 2, 2023, 9:46am

Just got update for cesium and its crashing all the time please fix asap. Its completely useless atm. There is no problem in editor but in game and in standalone it crashes.

Kevin_Ring · September 2, 2023, 11:31am

Sorry you’re having trouble @Ben1, but you’re going to have to give us more information before we can help you. Such as:

Confirm which version of Cesium for Unreal you’re using by going to Edit → Plugins → Geospatial.
What version of Unreal Engine itself are you using?
What platform are you on?
Does the Cesium for Unreal Samples project have the same problem, or is it only your own project? You can install this project from the Epic Launcher.
If it’s only your own project, what other plugins do you have active?
Does downgrading back to the old Cesium for Unreal version fix the problem? You can get old versions here: Releases · CesiumGS/cesium-unreal · GitHub
What tileset are you using when it crashes?

According to your call stack, you’re crashing on this line of code (assuming you’re using v1.30.0):

github.com

CesiumGS/cesium-unreal/blob/v1.30.0/Source/CesiumRuntime/Private/CesiumGltfComponent.cpp#L2233


      
          }
          
          if (pBaseWaterMaterial) {
            Gltf->BaseMaterialWithWater = pBaseWaterMaterial;
          }
          
          Gltf->CustomDepthParameters = CustomDepthParameters;
          
          encodeMetadataGameThreadPart(Gltf->EncodedMetadata);
          for (LoadNodeResult& node : pReal->loadModelResult.nodeResults) {
            if (node.meshResult) {
              for (LoadPrimitiveResult& primitive : node.meshResult->primitiveResults) {
                loadPrimitiveGameThreadPart(
                    model,
                    Gltf,
                    primitive,
                    cesiumToUnrealTransform,
                    tile,
                    createNavCollision,
                    pTilesetActor);
              }

I can’t see any good reason that line would crash, and it certainly doesn’t in a Windows Shipping build here, so we’re going to need your help to reproduce before we can fix it.

Ben1 · September 2, 2023, 12:06pm

1.30.0
UE 5.2
Windows 11
Yes it has the same problem
I have to do try this later…
Everything is default.

I had everything working fine yesterday untill today i updated cesium from epic game launcher and now its not working anymore. Here is crash report from cesium samples.

Kevin_Ring · September 2, 2023, 1:17pm

Really strange. I don’t have any trouble running a Shipping configuration build of the Cesium for Unreal Samples project. Windows 11, UE 5.2, plugin installed from the Epic Marketplace.

It’s a long shot, but maybe something was corrupted in the request cache? Delete cesium-request-cache.sqlite* in C:\Users\[your username]\AppData\Local\UnrealEngine\5.2.

Or maybe it’s worth trying an uninstall / reinstall of the plugin? Can you try a different computer and see if it happens there, too?

Would you mind walking me through the steps you’re following in excruciating detail so I can make sure I’m doing the same thing? Starting with installing the Samples project from the Epic Launcher.

Ben1 · September 2, 2023, 3:54pm

I tested with another computer with clean install and after i hit play in sample demo i get the same crash report in 10s - 1minute after launch. It sometimes take longer and sometimes shorter to crash. Tomorrow i will test with older versions.

Chris_Hofmann · September 2, 2023, 7:39pm

CONSTANT CRASHES INDEED! do you have a QA? dont worry ill post the log on my next one.

in editor…after loading the level…flying around for like 2 seconds…hangs…ue5.2.1 crashes.

it crashes in editor even if no tiles are visible in the viewport.
win10
ue5.2.1
cesium 5.2.0

pretty angry that such a version can be posted on the marketplace.

Kevin_Ring · September 2, 2023, 11:54pm

First of all, I’m really sorry you’re both having trouble.

But second, you may want to save your anger for someone who isn’t working on the weekend trying to help track down a problem with a free and open source plugin. Instead of anger, please provide as much information as you can to help me diagnose the problem. If it’s holding up your work in the meantime, it’s easy to downgrade to a previous version until this is resolved. All releases are here: Releases · CesiumGS/cesium-unreal · GitHub

I was eventually able to see a crash by building a shipping game with CWT + Bing and flying around for quite awhile, probably over 5 minutes. If you know a way to make it crash in “like 2 seconds”, please provide as much information as you can. Which tilesets? Was this the editor viewport, play in editor, a built game, etc? The faster I can reproduce it, the faster I’ll be able to solve it. But I’m working on it, in any case.

Kevin_Ring · September 3, 2023, 2:46am

I believe I’ve found and fixed this bug. You can download a pre-release version with the fix here:
UE 5.0: https://github.com/CesiumGS/cesium-unreal/suites/15765727426/artifacts/899942044
UE 5.1: https://github.com/CesiumGS/cesium-unreal/suites/15765727426/artifacts/899942050
UE 5.2: https://github.com/CesiumGS/cesium-unreal/suites/15765727426/artifacts/899942057

Uninstall the existing plugin using the Epic Launcher, and then extract the downloaded ZIP to C:\Program Files\Epic Games\UE_5.2\Engine\Plugins\Marketplace (or equivalent for your system and UE version).

More details about what was wrong are in the PR:

github.com/CesiumGS/cesium-native

Fix crash cause by redundant finishLoading call.

CesiumGS:main ← CesiumGS:finish-loading-crash

opened 12:45AM - 03 Sep 23 UTC

kring

+20 -3

Fixes crash reported here: https://community.cesium.com/t/latest-update-crash/2…6513 In #721, I added a call to `finishLoading` in a case that it was needed. `finishLoading` switches the tile into the `Done` state, which should guarantee that `finishLoading` won't get called again later. Or so I thought. The problem is that the tile may have been added to the main thread load queue while it was in the `ContentLoaded` state, but then by the time the main thread load queue is processed, by new call to finishLoading has already happened and so the tile is in the Done state. This would cause an assertion failure in debug builds, but in release builds it tends to just crash because the game engine integration interprets the renderer resources incorrectly. The solution in this PR is to double-check a tile is still in the ContentLoaded state when processing the load queue. I also added a bit more safety around the extra call to finishLoading for pathological tilesets with leaf tiles that have no renderable content.

If all looks well, we’ll release an official 1.30.1 this weekend, but it probably won’t be available in the Unreal Marketplace until Epic is able to review and publish it this week.

Thanks for your patience!

Chris_Hofmann · September 3, 2023, 9:12am

your pre-release UE 5.2 seems to do the trick…i dont get crashes anymore!

thank you so much for your rapid reaction! wont be forgotten.
and sorry for bringing my bad mood into the public…im under pressure this weekend and worried that i have to bring bad news on monday but its looking fine now and i might be able to catch up.

again what an awsome reaction by CESIUM…<3 <3 <3

Kevin_Ring · September 3, 2023, 11:31am

All good, mate. Thanks for trying out the pre-release and letting me know it solved the problem for you. I just published v1.30.1 with the fix to the Release page. It will take a little longer to hit the Unreal Marketplace. Apologies again for the regression!

Ben1 · September 4, 2023, 12:12pm

Everything is working now. Thanks alot!

Btw is it possible to have cesium compatible for ue 4.23 version? Would be nice to use cesium with html5 projects as unreal only supports html5 in 4.23 version and below. You can use html5 in 4.27 if you compile the engine from another source but i dont know how to do that… Is it huge task to get cesium working in 4.23 version of unreal? and would it even work in html5 “game”?

Kevin_Ring · September 5, 2023, 6:10am

Yes, it’s probably a lot of work to support UE 4.23, and even then it’s very unlikely the HTML5 support will just work. And even if you got all that working, you’d have invested all the time and energy in a version of UE (and a technique in general) that is no longer supported by Epic.

If you’re targetting the web, we highly recommend you use CesiumJS instead:

But it’s all open soruce, so go nuts if you feel like trying! The ue4-main branch contains the last version we released that supported UE4.27. Older versions in that branch worked on 4.26. We never supported any version older than that.

kalyan_chakravarthi · January 24, 2025, 1:50pm

we are using the Varjo XR-3 headsets for our flight simulator, created with UE 5.3.2 and the latest CESIUM plugin.

kalyan_chakravarthi · January 25, 2025, 1:22pm

Hi Kevin I follow all your steps but no use. I am using ue5.3, Win 10, and cesium 5.3.0. still, I am facing an issue my project is crashing every 1min when cesiuam can you give me a quick response or can we connect to solve this issue?

Kevin_Ring · January 29, 2025, 3:30am

@kalyan_chakravarthi that looks to be unrelated to the previous crashes mentioned in this thread. We’ve seen a crash like that show up when viewing the globe from very far away. If that’s your scenario, it should be fixed in the next release by this PR:

github.com/CesiumGS/cesium-native

Fix crash while creating culling volume when the camera is very far from the globe

CesiumGS:main ← CesiumGS:culling-volume-crash

opened 09:11PM - 24 Jan 25 UTC

azrogers

+50 -6

Fixes #633. As Kevin describes in the linked issue, the calculation to create a …culling volume currently uses `1.0` as the near plane distance. This is fine for most operations we need to do, but causes problems when the value of `position` is *really* large. In this case, adding `1.0` to the position results in the same position value, so the normal is calculated with a magnitude of 0 and an exception is thrown when trying to create a plane with this normal. This change uses `std::nextafter` to obtain the next representable value based on the position's magnitude, subtracting the position's magnitude to obtain the minimum value we need to add to the position to not result in the same value. We only use this value if it's greater than 1.0, so the previous near plane behavior is preserved in most cases (otherwise the near plane distance would be `std::numeric_limits<double>::epsilon()` for values close to zero!). This should work to prevent a crash for any positions with a magnitude less than `std::numeric_limits<double>::max()`. If the position is at the max double value, we will still crash, but I'm not sure there's any tricks we can do to make the math work out in that case. In the process, I noticed `CullingVolume` was in the `Cesium3DTilesSelection` namespace even though the files are in `CesiumGeometry`. I assume they were moved here at some point, but the namespace wasn't updated (was this on purpose or accidental?). I've updated the namespace to `CesiumGeometry`.

It’s also possible that there’s some other problem with one of your cameras. If you’re manually creating cameras via the C++ or Blueprint API on the CesiumCameraManager, it’s possible that one of your cameras has nonsensical parameters. It’s also possible that one of the cameras that Cesium for Unreal is automatically discovering itself, such as an Editor camera or a Player Controller camera, has nonsensical values.

Can you give us instructions for reproducing this crash ourselves?

Topic		Replies	Views
Crash on Play or Packaged Project Cesium for Unreal	15	1074	August 12, 2021
5.1 Play in "Standalone Game" Crashes & Build fails to Display Cesium Map Cesium for Unreal	5	30	November 4, 2024
Cesium for UE 5.5 release date Cesium for Unreal	12	357	November 27, 2024
Crash when play in editor or render sequnce Cesium for Unreal	3	198	October 19, 2023
Unreal Engine and Cesium version difference Cesium for Unreal	1	20	August 12, 2024

Latest update crash

Related topics