# Tile has a bounding volume that does not include all of its content, so culling and raster overlays may be incorrect **URL:** \ **Category:** Cesium for Unreal\ **Created:** [October 9, 2023, 7:41am UTC](https://community.cesium.com/t/tile-has-a-bounding-volume-that-does-not-include-all-of-its-content-so-culling-and-raster-overlays-may-be-incorrect/27241 "2023-10-09T07:41:06Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![Heily](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/heily/32/3476_2.png) [@Heily](https://community.cesium.com/u/Heily)\ **Post date:** [October 9, 2023, 7:41am UTC](https://community.cesium.com/t/tile-has-a-bounding-volume-that-does-not-include-all-of-its-content-so-culling-and-raster-overlays-may-be-incorrect/27241/1 "2023-10-09T07:41:06Z")
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. ---
**Author:** ![janine](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/janine/32/5135_2.png) [@janine](https://community.cesium.com/u/janine)\ **Post date:** [October 9, 2023, 6:36pm UTC](https://community.cesium.com/t/tile-has-a-bounding-volume-that-does-not-include-all-of-its-content-so-culling-and-raster-overlays-may-be-incorrect/27241/2 "2023-10-09T18:36:49Z")
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. ---
**Author:** ![Heily](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/heily/32/3476_2.png) [@Heily](https://community.cesium.com/u/Heily)\ **Post date:** [October 10, 2023, 1:49am UTC](https://community.cesium.com/t/tile-has-a-bounding-volume-that-does-not-include-all-of-its-content-so-culling-and-raster-overlays-may-be-incorrect/27241/3 "2023-10-10T01:49:50Z")
Hi Janine, I am using UE5.0 and using my own terrain data. Unfortunately, doing it in Cesium for UE sample result same log. ![tile problem1](https://global.discourse-cdn.com/cesium/original/3X/9/8/98d0e2003a148f459020a7d2174f8909ad75d237.png) 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. ![tile problem2](https://global.discourse-cdn.com/cesium/original/3X/f/8/f85e873a89e7a370d89369d94c97db214f44db9d.png) 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. ---
**Author:** ![Kevin\_Ring](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/kevin_ring/32/2003_2.png) [@Kevin\_Ring](https://community.cesium.com/u/Kevin_Ring)\ **Post date:** [October 10, 2023, 11:08pm UTC](https://community.cesium.com/t/tile-has-a-bounding-volume-that-does-not-include-all-of-its-content-so-culling-and-raster-overlays-may-be-incorrect/27241/4 "2023-10-10T23:08:32Z")
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. ---
**Author:** ![Heily](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/heily/32/3476_2.png) [@Heily](https://community.cesium.com/u/Heily)\ **Post date:** [October 11, 2023, 1:22am UTC](https://community.cesium.com/t/tile-has-a-bounding-volume-that-does-not-include-all-of-its-content-so-culling-and-raster-overlays-may-be-incorrect/27241/5 "2023-10-11T01:22:24Z")
Hi Kevin, I packaged for window exe with vr experience. ---
**Author:** ![Kevin\_Ring](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/kevin_ring/32/2003_2.png) [@Kevin\_Ring](https://community.cesium.com/u/Kevin_Ring)\ **Post date:** [October 11, 2023, 10:27am UTC](https://community.cesium.com/t/tile-has-a-bounding-volume-that-does-not-include-all-of-its-content-so-culling-and-raster-overlays-may-be-incorrect/27241/6 "2023-10-11T10:27:19Z")
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. ---
**Author:** ![Aankit\_K](https://avatars.discourse-cdn.com/v4/letter/a/b19c9b/32.png) [@Aankit\_K](https://community.cesium.com/u/Aankit_K)\ **Post date:** [August 31, 2024, 11:18pm UTC](https://community.cesium.com/t/tile-has-a-bounding-volume-that-does-not-include-all-of-its-content-so-culling-and-raster-overlays-may-be-incorrect/27241/7 "2024-08-31T23:18:11Z")
If we change the relativeEpsilon value will it solve this issue? ![image](https://global.discourse-cdn.com/cesium/original/3X/b/0/b03328b6815d62b0a5c55aadd5ac59b725542a97.png) ---
**Author:** ![Aankit\_K](https://avatars.discourse-cdn.com/v4/letter/a/b19c9b/32.png) [@Aankit\_K](https://community.cesium.com/u/Aankit_K)\ **Post date:** [August 31, 2024, 11:18pm UTC](https://community.cesium.com/t/tile-has-a-bounding-volume-that-does-not-include-all-of-its-content-so-culling-and-raster-overlays-may-be-incorrect/27241/8 "2024-08-31T23:18:52Z")
@Kevin_Ring I am also facing the same issue. Is there any solution for this warning. ![image](https://global.discourse-cdn.com/cesium/original/3X/7/2/72c2d0128c43e3fcffd91b6a9a08fb37a8aa00ac.jpeg) ---
**Author:** ![Kevin\_Ring](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/kevin_ring/32/2003_2.png) [@Kevin\_Ring](https://community.cesium.com/u/Kevin_Ring)\ **Post date:** [September 6, 2024, 8:59am UTC](https://community.cesium.com/t/tile-has-a-bounding-volume-that-does-not-include-all-of-its-content-so-culling-and-raster-overlays-may-be-incorrect/27241/9 "2024-09-06T08:59:06Z")
@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: > > > As reported here: > https://community.cesium.com/t/warning-tile-has-a-bounding-vo…lume-that-does-not-include-all-of-its-content-so-culling-and-raster-overlays-may-be-incorrect/25460 ---
**Author:** ![Aankit\_K](https://avatars.discourse-cdn.com/v4/letter/a/b19c9b/32.png) [@Aankit\_K](https://community.cesium.com/u/Aankit_K)\ **Post date:** [September 6, 2024, 9:34am UTC](https://community.cesium.com/t/tile-has-a-bounding-volume-that-does-not-include-all-of-its-content-so-culling-and-raster-overlays-may-be-incorrect/27241/10 "2024-09-06T09:34:16Z")
try zooming to north pole and south pole and see for yourself. tiles starts to disappear ---
**Author:** ![Kevin\_Ring](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/kevin_ring/32/2003_2.png) [@Kevin\_Ring](https://community.cesium.com/u/Kevin_Ring)\ **Post date:** [September 9, 2024, 10:52pm UTC](https://community.cesium.com/t/tile-has-a-bounding-volume-that-does-not-include-all-of-its-content-so-culling-and-raster-overlays-may-be-incorrect/27241/11 "2024-09-09T22:52:50Z")
Like this? ![image](https://global.discourse-cdn.com/cesium/original/3X/9/b/9b3cf535f6fc095ca3215c1d4989d5f6544f2fee.jpeg) 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: > > > Web Mercator texture coordinates get dodgy north/south of ~+/-85 degrees latitud…e. CesiumJS deals with this by reprojecting web mercator imagery tiles to geographic when they're attached to terrain tiles that cross this boundary. We could do the same here, or alternatively we could insert extra vertices in the geometry at ~+/-85 degrees latitude so that we never try to texture map across this boundary. ---
**Author:** ![Unreal\_Miracle](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/unreal_miracle/32/14000_2.png) [@Unreal\_Miracle](https://community.cesium.com/u/Unreal_Miracle)\ **Post date:** [August 25, 2025, 6:29am UTC](https://community.cesium.com/t/tile-has-a-bounding-volume-that-does-not-include-all-of-its-content-so-culling-and-raster-overlays-may-be-incorrect/27241/12 "2025-08-25T06:29:47Z")
@Kevin_Ring 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? ![地形错误](https://global.discourse-cdn.com/cesium/original/3X/b/0/b087cb4f08fda85f92c6052fbfe8e50d13f8bd20.jpeg) ---
**Author:** ![Kevin\_Ring](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/kevin_ring/32/2003_2.png) [@Kevin\_Ring](https://community.cesium.com/u/Kevin_Ring)\ **Post date:** [August 25, 2025, 8:26am UTC](https://community.cesium.com/t/tile-has-a-bounding-volume-that-does-not-include-all-of-its-content-so-culling-and-raster-overlays-may-be-incorrect/27241/13 "2025-08-25T08:26:27Z")
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.