Attaching multiple raster tiles causes the program to crash

Cesium for Unreal
1

Attaching multiple raster tiles causes the program to crash.

Add an image layer (CesiumTileMapServiceRasterOverlay) under Cesium3DTileset, and then set the corresponding layer name and URL:
CesiumIonRasterOverlay → Overlay0
CesiumTileMapServiceRasterOverlay → Overlay1

After setting it up, the program crashes:
Assertion failed: textureCoordinateID >= 0 && textureCoordinateID < primData.overlayTextureCoordinateIDToUVIndex.size()
0x00007ffcc487e39d UnrealEditor-CesiumRuntime.dll!UCesiumGltfComponent::AttachRasterTile'::2’::<lambda_1>::operator()()

2

Hi @sjf2046, welcome to the community!

Can you share more information with us so that we can try to reproduce this issue on our machines?

  • What versions of Unreal Engine and Cesium for Unreal are you using?
  • What data are you applying raster overlays to? Cesium World Terrain? Something else?
  • Are you setting any custom materials in the Material parameter on the Cesium3DTileset?

Thanks in advance!

3

UE5.5 and Cesium 2.13.3

Applying a raster overlay to Cesium world terrain

A new material was created as shown in the image to support UDS.

(_D3%E6E607~}~@9%Q$40Q
(_D3%E6E607~}~@9%Q$40Q1457×700 195 KB

Strangely, it doesn’t crash when I use either layer alone.

The crash only occurs when both layers are added to Cesium World Terrain simultaneously.

4

Hi @sjf2046,

I don’t know for sure if it will help, but I think it’s worth trying an upgrade to the latest version (v2.21.0).

It’s also worth a try to revert to the default material and see if it still crashes. That’s not a fix, of course, but it might help narrow down the problem.

5

When I upgraded the plugin to version 2.19.1, the crash issue seemed to be resolved, but a new problem arose: Terrain clipping works correctly during PIE.

However, after packaging, unloaded terrain tiles appear outside the clipping area.

image
image975×537 225 KB

It keeps happening, and it’s not a network issue.

6

Hi @sjf2046,

Can you please check the log in your packaged application to see if there are any messages that might offer a hint about what is going wrong there?

Also, can I ask why you only upgraded to v2.19.1 instead of all the way to v2.21.0? (as of yesterday, v2.21.1 is out)