# Tile not rendering which closer to camera **URL:** \ **Category:** Cesium for Unity\ **Created:** [October 24, 2024, 11:47am UTC](https://community.cesium.com/t/tile-not-rendering-which-closer-to-camera/36033 "2024-10-24T11:47:07Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![sendreams](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/sendreams/32/14000_2.png) [@sendreams](https://community.cesium.com/u/sendreams)\ **Post date:** [October 24, 2024, 11:47am UTC](https://community.cesium.com/t/tile-not-rendering-which-closer-to-camera/36033/1 "2024-10-24T11:47:07Z")
i have used custom tileset which contains terrain and a raster overlay. When moving the camera, terrain tiles near the camera become invisible/disappear, while distant tiles render normally. When raising the camera higher, those previously invisible tiles near the camera become visible again. [![](https://global.discourse-cdn.com/cesium/original/3X/c/1/c12efb19bfe8837026afa426c956af73928b1a28.jpeg "terrain rendering") ](https://www.youtube.com/watch?v=-hoApv_WN6A) ---
**Author:** ![sendreams](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/sendreams/32/14000_2.png) [@sendreams](https://community.cesium.com/u/sendreams)\ **Post date:** [October 24, 2024, 2:04pm UTC](https://community.cesium.com/t/tile-not-rendering-which-closer-to-camera/36033/2 "2024-10-24T14:04:12Z")
i have found the reason, because the tileset defination in layer.json is not exactly same to the tile files, layer.json has define level 1 to 18, but the tile files just only have level 1~15, so while camera colosed to terrain, the cesium should render more detail level tile, but can not download it. cesium may be can show warning message will be better for developer while it can not download terran tile. ---
**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 29, 2024, 4:59am UTC](https://community.cesium.com/t/tile-not-rendering-which-closer-to-camera/36033/3 "2024-10-29T04:59:36Z")
Hi @sendreams, welcome to the community! Have you checked the Console tab? There should be a message in the log when a tile fails to download. ---
**Author:** ![sendreams](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/sendreams/32/14000_2.png) [@sendreams](https://community.cesium.com/u/sendreams)\ **Post date:** [October 30, 2024, 3:59pm UTC](https://community.cesium.com/t/tile-not-rendering-which-closer-to-camera/36033/4 "2024-10-30T15:59:14Z")
i really have been checked the console tab, but i don’t find any useful message. It took a lot of time to find the root cause of this problem. ---
**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:** [November 4, 2024, 7:22am UTC](https://community.cesium.com/t/tile-not-rendering-which-closer-to-camera/36033/5 "2024-11-04T07:22:30Z")
I just checked this in the latest version of Cesium for Unity. It seems that when a 3D Tiles content file referenced from a tileset.json fails to load, the user will see an error. However, if a `.terrain` file from layer.json fails to load, the error is silently ignored. I wrote an issue against cesium-native for this problem: > > > I saw this in Cesium for Unity, but it's most likely a cesium-native problem, no…t specific to Unity. > > If a particular tile from a tileset.json is missing, users will see a message in the log: > > \> \[2024-11-04 18:13:29.274\] \[error\] \[TilesetJsonLoader.cpp:924\] Received status code 404 for tile content http://localhost:8080/batchedColors.b3dm > > However, if one of the \`.terrain\` files in quantized-mesh / layer.json is missing, the error is silently ignored, leaving users wondering why there's a hole in their terrain. > > Originally reported by a user here: > https://community.cesium.com/t/tile-not-rendering-which-closer-to-camera/36033 Thanks for reporting it!