Hi guys, I load a terrain in UE and use the CesiumTileMapServiceRasterOverlay to add the texture from url, it works very well in UE. But the titled problem occurs after packaged.
Hey @Heily,
Can you provide more details so we can reproduce your issue? For example,
- What version of UE are you using?
- Are you using Cesium World Terrain or your own data?
- Can you reproduce this in the Cesium for Unreal samples?
- Screenshots would help.
Hi Janine, I am using UE5.0 and using my own terrain data. Unfortunately, doing it in Cesium for UE sample result same log.
After adding my own data to load the terrain(without texture, only a white terrain), it shows the titled problem already, but in this time, the game works well in UE and after package.
However, when I load the texture with an API key, the red error occurs. Although the terrain with texture can be shown in UE, it cant be packaged.
What platform are you packaging for? Are you using file URLs? file:/// URLs are only supported on Windows, due to a limitation of Unrealâs HTTP request system.
The bounding volume warning indicates a problem with your data, but if itâs displaying ok in the Editor then it might not be a catastrophic one.
Hi Kevin, I packaged for window exe with vr experience.
I searched for the message in your log, âCould not perform game thread setup, processing HTTP request failedâ, and itâs reported by Unrealâs FCurlHttp when SetRequest fails. It looks like most cases of failure would log a more useful message as well, except for one: âHttp disabled. Skipping request.â Have you disabled HTTP support somehow?
It may help to clarify âwindow exe with vr experienceâ as well, because I donât exactly know what that means.
@Kevin_Ring
I am also facing the same issue. Is there any solution for this warning.
@Aankit_K can you please elaborate on what problem youâre seeing exactly? If youâre just talking about the âdoes not include all of its contentâ warning, then a reasonably valid solution is to simply ignore it. If youâre seeing a problem beyond the message, please describe it, as well as the details of the tileset youâre seeing when you encounter the problem.
Hereâs an issue tracking a similar problem, which may or may not be the exact same one youâre seeing:
try zooming to north pole and south pole and see for yourself. tiles starts to disappear
Like this?
Thatâs caused by the Bing Maps tiles (in this case) using the Web Mercator projection, which stops at ~85 degrees latitude. When a terrain tile is at least partially covered by a texture, that texture will get stretched out to the edges. But if a terrain tile doesnât have any imagery tiles at all that overlap it, youâll get that white, untextured look.
We have an issue covering this, but it hasnât been a high priority so far:
1 Like
Hello, I am still encountering this issue in UE5.2 Cesium for Unreal 2.11.
Tile has a bounding volume that does not include all of its content, so culling and raster overlays may be incorrect: http://****/3/3/0.terrain?extensions=octvertexnormals upsampled L4-X6-Y0.
How should I solve this problem?
Hi @Unreal_Miracle,
Can you tell us more about how you created that screenshot? What tilesets and raster overlays are you using? Can you tell us how to reproduce it?
Better yet, start a new thread, because this one is quite old and possibly unrelated.
By the way, in general, we only release new versions of Cesium for Unreal for the three most recent Unreal Engine versions. So that means 5.4, 5.5, and 5.6. So if this does turn out to be a bug, youâll probably need to upgrade in order to get the fix.