Cesium API stopped loading assets

Hi all,

I’m still learning some basic Cesium tools, specially the use of Cesium ION. I had some layers being retrieved from an Cesium.ion free account. The whole application was running smoothly and ingesting the ION assets. However, recently the app doesn’t shown any error while using F12 inspection. I see that I still have enough storage (less then 5 GB disk usage) for a free account, and I wonder if the fact that the assets have stopped rendering in the app could be related to the Cesium API Key. Any hint why the assets stopped being retrieved will be very appreciated.

Thank you for your time in advance


Hi Julierme,

Sorry for the delayed reply here. Are you still having issues? We do not have any sort of hard limits on rendering as you describe. The 5GB storage is the only hard limit in the free account.

Can you provide more details?


Hi Matthew,

Thank you very much for your reply. I’m still having the issue. My application is available here. If you run F12, you won’t see any code issue through an inspection. I changed the ionAccessToken, but my asset is no longer being retrieved by my application. Please take a look at the code below.

const ametistaTileset = viewer.scene.primitives.add(
new Cesium.Cesium3DTileset({
url: Cesium.IonResource.fromAssetId(1482238),

(async () => {
try {
await ametistaTileset.readyPromise;
await viewer.zoomTo(ametistaTileset);

// Apply the default style if it exists
var ametistaExtras = ametistaTileset.asset.extras;
if (
Cesium.defined(ametistaExtras) &&
Cesium.defined(ametistaExtras.ion) &&
) {
ametistaTileset.style = new Cesium.Cesium3DTileStyle(ametistaExtras.ion.defaultStyle);
} catch (error) {

I could not figure out what is going on as everything was working smoothly, and suddenly the asset stopped being retrieved.

Thank you very much for your time in advance.

@Julierme_Pinheiro This appears to be an issue with your application so I’ve moved this into the CesiumJS category.

I noticed a few things…

  • Your assets are loading fine.
  • Your application is zooming to an imagery layer (which shows up as expected).
  • The story you linked to is zooming to a 3D tileset. However, I noticed in the Story that terrain is disabled, so the OSM buildings are floating and your data shows up on the ground.
  • In the application, however, you have terrain turned on, so there is a good chance your data is simply being hidden under the ground. I’m also unsure if your imagery and 3D Tiles are located at the same position, but since your application is zooming to the imagery, that’s what is showing up.

I hope that helps point you in the right direction. Let us know if you have additional questions.


I created another Cesium Ion account and added the same asset and I still not being able to retrieve it.

Hi @Julierme_Pinheiro,

Would you mind putting together a minimal Sandcastle example so we can determine if there’s an issue with CesiumJS?

suddenly the asset stopped being retrieved.

Thank you!

Hi @Gabby_Getz and Matthew,

Thank you very much for your reply.

I found out the problem. I had set the Terrain reference to WGS84 Ellipsoid rather than Cesium World Terrain. I set the height to zero for WGS84 Ellipsoid and the layer was disappearing, but now I’m setting the height to (The Local Average Height of the area) referenced to Cesium World Terrain.

By the way, I’m in need of using the Cesium measure tools and also in need of getting a tool that allows users to extract slices of the 3D tiles asset, rather than downloading the entire 3D layer.

I appreciated your time and help.


Hi @Gabby_Getz and Matthew,

How much is the annual contract to use Cesium’s measure tool and a tool to extract parts of a 3D tile asset?

Thank you very much for your time in advance

Hi @Julierme_Pinheiro,

Glad the issue has been resolved.

For the measurement tools included in the Cesium ion SDK, please contact sales@cesium.com for pricing.

@Matt_Amato could you speak to the ability to cut out areas of 3D Tiles in Cesium ion?