I want to hide part of a set of Photorealistic 3D Tiles in Google and place other levels that I have created myself there

I created the level using Google’s Photorealistic 3D Tiles in UE5.1.

I want to hide parts of tilesets with Cartographic Polygons and place other levels with my own buildings in them, but I can’t!

What is the correct way to place them?

Have you seen the tutorial?

Yes, I can hide some of the tiles as in the video linked in that tutorial and even place a level with another building there.

And you can also have the original third person walking around.

However, the Windws packaging does not work!


Looks cool!

But “does not work” doesn’t give us anything to go on as far as diagnosing the problem. Tell us in what way it does not work and maybe we can help.

Packaging is successful at the level with no cesium at all in the aforementioned video.

However, if cesium is added to that level and Platforms>Wondows>Package Project is executed, it fails.
(I have also uploaded a screen capture of UE5 at that level.)

The logs are as follows.

UE5OutputLog.rar (37.3 KB)

Hmm as far as I can tell, the cook failure is a result of this error:

UATHelper: Packaging (Windows): LogInit: Display: LoadErrors: Error: Collision Profile settings do not include an entry for the Water Body Collision profile, which is required for water collision to function. Add entry to DefaultEngine.ini?

That’s not one I’ve seen before, and it’s not clear that it has anything to do with Cesium.

As a first step, can you try the Cesium for Unreal Samples project (you can install it from the Epic Marketplace) and see if you’re able to package that one successfully, at least?

I found this thread on the Unreal Engine forum with some folks running into the same problem. Perhaps some of the solutions suggested by Epic there will be helpful for you.

1 Like

A few days ago, we confirmed that the Cesium for Unreal Samples project can be successfully packaged.

Ok, that’s good. I’m not sure what’s different about your project that prevents it from being packaged, but I suggest you try the tips in the forum post I linked above. Such as removing and re-adding the water plugin and adding the extra configuration to your DefaultEngine.ini.


I took the link you posted as a hint, deleted and re-added the water plugin, then added that line to DefaultEngine.Ini and the packaging was successful!.

Glad to hear it worked!