Runtime created Cesium Tileset with material (OSM Buildings for example) doesn't render

asaf.amit · August 14, 2021, 2:44am

For example creating an OSM Tileset at runtime doesn’t render the material that gets assigned to it leaving that layer invisible…

agallegos · August 16, 2021, 2:31pm

Hi @asaf.amit,

Thanks for bringing this to our attention. To help nail down the issue, how are you creating the tileset at runtime? It would be helpful if you could share your blueprint graph or C++ code.

-Alex

asaf.amit · August 17, 2021, 1:45am

Thank you, here is the C++ snippet

	ACesium3DTileset* Tileset = Cast<ACesium3DTileset>(
		UGameplayStatics::BeginDeferredActorSpawnFromClass(GetWorld(), ACesium3DTileset::StaticClass(), FTransform()));
	if (Tileset)
	{
		Tileset->SetTilesetSource(ETilesetSource::FromCesiumIon);
		Tileset->SetIonAssetID(Id);
		Tileset->SetIonAccessToken(CesiumAccessToken);
		Tileset->Rename(*LayerNameTextBox->GetText().ToString().TrimStartAndEnd());

		TileSet->SetMaterial(BaseMaterial);
		TileSet->EnableFrustumCulling = false;
		TileSet->EnableFogCulling = false;
		TileSet->GetRootComponent()->SetMobility(EComponentMobility::Movable);
		UGameplayStatics::FinishSpawningActor(Tileset, FTransform());
       }

Kevin_Ring · August 19, 2021, 9:53am

Hi @asaf.amit,

I was able to reproduce the problem using the code you provided. Upon further investigation, though, it doesn’t appear to have anything to do with runtime creation of the Cesium OSM Buildings tileset, or with setting the material. Rather, the problem is the “EnableFrustumCulling = false” combined with the (default) EnforceCulledScreenSpaceError=false when rendering certain tilesets like Cesium OSM Buildings. I wrote an issue describing the problem:

github.com/CesiumGS/cesium-native

External tilesets don't work right with enableFrustumCulling=false and enforceCulledScreenSpaceError=false

opened 07:49AM - 19 Aug 21 UTC

kring

bug

Originally reported here with Cesium OSM Buildings, which uses external tilesets… extensively: https://community.cesium.com/t/runtime-created-cesium-tileset-with-material-osm-buildings-for-example-doesnt-render/14834/2 In the tile selection algorithm, we treat external tilesets as if they have a really huge geometric error. This guarantees that we never select them, but instead always refine past them. At least, it usually does. A problem comes up when enableFrustumCulling is set to false. In this scenario, tiles that would otherwise be culled will be included in the render list. When enforceCulledScreenSpaceError is also false, we also will not (ever!) refine such tiles. And this is true even for external tilesets with their huge geometric error. Thus, we'll end up selecting an external tileset for rendering, even though it's not a thing we can render. Now this alone wouldn't be a _huge_ problem. It would just be a tile in the render list without any renderable content and we could just ignore it. But because `_meetsSse` is returning true for these culled external tileset tiles (and this is the _only_ situation in which it will), we add it to the render list with `_renderInnerTile`. And `_renderInnerTile` will note that the tile's `isRenderable` method returned false (which is fair enough, it's not renderable). Because this tile isn't renderable, and never has been, the next level up in the selection traversal will kick this tile _and its siblings_ out of the render list, waiting for them all to become renderable, presumably by further loading. But an external tileset will never become renderable no matter how long we wait for it to load. End result: we don't render this whole branch of the tile tree with these settings.

As a workaround until this is fixed, you should be able to set EnforceCulledScreenSpaceError to true. That alone will result in rendering more tiles, but you can counteract this (and get close to the original behavior you were aiming for) just by setting CulledScreenSpaceError to a large value like 1024 or so.

Here’s the code I used to test it:

  const FString CesiumAccessToken = TEXT("[my key]");
  const int32 Id = 96188;

  ACesium3DTileset* Tileset =
      Cast<ACesium3DTileset>(UGameplayStatics::BeginDeferredActorSpawnFromClass(
          GetWorld(),
          ACesium3DTileset::StaticClass(),
          FTransform()));
  if (Tileset) {
    Tileset->SetTilesetSource(ETilesetSource::FromCesiumIon);
    Tileset->SetIonAssetID(Id);
    Tileset->SetIonAccessToken(CesiumAccessToken);
    Tileset->Rename(TEXT("Test"));

    //TileSet->SetMaterial(BaseMaterial);
    Tileset->EnableFrustumCulling = false;
    Tileset->EnableFogCulling = false;
    Tileset->EnforceCulledScreenSpaceError = true;
    Tileset->CulledScreenSpaceError = 1024.0f;
    Tileset->GetRootComponent()->SetMobility(EComponentMobility::Movable);
    UGameplayStatics::FinishSpawningActor(Tileset, FTransform());
  }

Kevin

asaf.amit · August 20, 2021, 6:29am

Hi Kevin,

Thank you, the workaround works.

Regards,
Asaf

Topic		Replies	Views
cesium for unreal 3dtiles dynamicmaterial Cesium for Unreal	8	62	December 12, 2024
Adding tilesets at runtime Cesium for Unreal	1	342	May 5, 2022
Spawn Cesium3DTileset at runtime Cesium for Unreal	11	1778	July 8, 2021
3D tilesets created at runtime flicker, how to fix it? Cesium for Unreal	4	47	November 5, 2024
After dynamically loading 3DTileset, the model flickers severely. How to solve it? Cesium for Unreal	1	21	November 4, 2024

Runtime created Cesium Tileset with material (OSM Buildings for example) doesn't render

Related topics