CesiumJS-Claude-Skill-Package

Use when starting a new CesiumJS application or feature and deciding how to structure the scene: which viewer class, which imagery and terrain, how to represent a dataset, and whether to enable on-demand rendering. Prevents the wrong-API-tier choice (Entity where 3D Tiles is needed, or the reverse), the continuous-render battery drain, and missing-token blank globes. Orchestrates the CesiumJS skill set into one setup decision path. Keywords: CesiumJS architecture, how do I structure a Cesium app, which viewer, Viewer or CesiumWidget, Entity or Primitive or 3D Tiles, choose imagery provider, choose terrain provider, requestRenderMode, scene setup decision, how do I display my data in Cesium, what API should I use, getting started Cesium scene, plan a Cesium scene.

Use when CesiumJS code has just been generated or reviewed and must be checked before it is called done, to catch deprecated APIs and common defects, or when auditing CesiumJS code from an older source. Detects the removed synchronous patterns (readyPromise, the url constructor option, ModelExperimental, defaultValue, new on a Cartesian factory), WebGPU assumptions, missing ion tokens, missing destroy() calls, and coordinate-type mistakes. Runs a deterministic checklist and routes each failure to the skill that fixes it. Keywords: validate CesiumJS code, review Cesium code, is this Cesium code correct, deprecated CesiumJS API, readyPromise, ModelExperimental, defaultValue removed, check before commit, CesiumJS code quality, lint Cesium, did I use the right API, audit Cesium scene, why might this code fail.

Use when CesiumJS geometry renders in the wrong place, falls through the terrain, sits at the center of the Earth, or never appears, and when position values come back as NaN. Prevents the radians-versus-degrees mistake, the Cartographic-versus-Cartesian3 mixup, the longitude and latitude swap, the GeoJSON ground-clamp surprise, and terrain-clamping before terrain has loaded. Covers Cartesian3, Cartographic, the fromDegrees factories, HeightReference, HeadingPitchRoll conventions, and terrain height sampling. Keywords: CesiumJS coordinates, NaN position, entity not showing, model wrong place, geometry at center of earth, off the globe, radians degrees, longitude latitude swapped, Cartographic Cartesian3, fromDegrees, fromRadians, clampToGround, sampleTerrainMostDetailed, HeightReference, HeadingPitchRoll, heading pitch roll wrong, why is my point underground, how do I place something on terrain, position is NaN.

Use when a CesiumJS app's memory keeps growing, the browser tab slows down or crashes after running a while, or the console reports "Too many active WebGL contexts" or "DeveloperError: This object was destroyed". Covers WebGL resource leaks from missing destroy() calls, teardown ordering, reusing primitives after destruction, entity-removal memory retention, lost-reference bugs that only look like leaks, and exhaustion of the browser 16-context WebGL budget by single-page-app routing or React re-mounts. Keywords: memory leak, heap grows, tab crash, out of memory, browser freezes, app slow over time, WebGL context lost, too many active WebGL contexts, This object was destroyed, DeveloperError, destroy, isDestroyed, PrimitiveCollection, destroyPrimitives, viewer.destroy, how do I clean up a Cesium viewer, why does my Cesium app leak memory.

Use when a CesiumJS globe renders blank, black, white, or frozen, when the canvas shows nothing, when the WebGL context is lost, or when a render-loop error panel covers the canvas. Prevents the blank-globe trap caused by an unset CESIUM_BASE_URL, a missing or invalid Cesium ion token, or an omitted bundler asset-copy step. Covers the renderError event, WebGL context-loss recovery, the 16-context budget, and missing imagery or terrain. Keywords: blank globe, black screen, white screen, nothing renders, globe not showing, CESIUM_BASE_URL, CONTEXT_LOST_WEBGL, renderError, rethrowRenderErrors, Ion.defaultAccessToken, HTTP 401, webglcontextlost, too many active WebGL contexts, no imagery, no terrain, how do I fix a blank Cesium globe.

Use when a Cesium3DTileset does not load or render: the console floods with CORS errors, the network tab shows 401 or 403, readyPromise is undefined, fromUrl resolves but nothing appears, the tileset has holes, or fromUrl rejects with a RuntimeError. Covers CORS and file protocol failures, ion and Google authentication, the removed synchronous readyPromise construction, invisible tilesets, individual tile failures, and unhandled promise rejections. Keywords: Cesium3DTileset, fromUrl, fromIonAssetId, tileset not loading, 3D Tiles not showing, CORS error, blocked by CORS policy, file protocol CORS, 401 tileset, 403 Forbidden, tiles missing, holes in tileset, tileFailed, readyPromise is undefined, RuntimeError, unhandled promise rejection, GoogleMaps defaultApiKey, Ion.defaultAccessToken, why is my tileset blank, how do I load 3D Tiles, how do I fix a CORS error.

Use when placing a BIM model, CAD model, IFC export, or city model into a CesiumJS globe at its real geographic location, and the model renders at the center of the Earth, sits at the wrong place, floats above or sinks below terrain, or faces the wrong direction. Prevents the identity-modelMatrix mistake (a model with no transform draws in raw ECEF coordinates), the double-transform mistake (re-placing an already-georeferenced ion tileset), the radians-versus-degrees HeadingPitchRoll mistake, and the conversion-pipeline-is-an-API mistake. Separates the official CesiumJS georeferencing API (Transforms, Matrix4, HeadingPitchRoll, modelMatrix) from the external CityGML and IFC conversion workflow. Keywords: CesiumJS AEC, georeference, georeferencing, BIM in Cesium, IFC in Cesium, CityGML, modelMatrix, Transforms.eastNorthUpToFixedFrame, headingPitchRollToFixedFrame, HeadingPitchRoll, Matrix4, ECEF, local frame, east north up, digital twin, geo-BIM, EdgeDisplayMode, CAD edges, model wrong location, model at cente

Use when a bundled CesiumJS app shows a blank globe, logs 404s for Workers, Assets, or Widgets, fails with a worker or bundler error, or when converting a Sandcastle example into a production build. Covers the cesium npm package, the four static directories, window.CESIUM_BASE_URL, the Vite and webpack integrations, ES6 named imports, and the Sandcastle to production workflow. Keywords: CesiumJS build, cesium npm package, CESIUM_BASE_URL, window.CESIUM_BASE_URL, vite-plugin-cesium, CopyWebpackPlugin, DefinePlugin, webpack, Vite, widgets.css, static directories, Workers, ThirdParty, Assets, Widgets, Sandcastle, Ion.defaultAccessToken, ES6 named imports, tree shaking, blank globe, Workers 404, bundler error, worker failed to load, Cesium is not defined, globe is blank, how do I bundle Cesium, how do I deploy a Cesium app, how do I use a Sandcastle example.

Use when building a CesiumJS application in React with Resium, the declarative React component wrapper for CesiumJS. Covers the Viewer and CesiumWidget root components, nesting Entity and graphics components, the useCesium hook, and reaching the native Cesium object through a ref and CesiumComponentRef.cesiumElement. Keywords: Resium, reearth resium, React Cesium, useCesium, CesiumComponentRef, cesiumElement, Viewer component, Entity component, Cesium3DTileset component, CameraFlyTo, ImageryLayer, peer dependency, declarative Cesium, Resium viewer blank, cesiumElement undefined, ref is null, component must be inside Viewer, React Cesium not showing, how do I use Cesium with React, add a map to a React app.

Use when styling the features of a CesiumJS 3D Tiles tileset with the declarative styling language, coloring or hiding features by their metadata, or clipping a tileset with planes or polygons. Covers Cesium3DTileStyle, the styling expression language, conditions arrays, the color functions, ClippingPlaneCollection, and ClippingPolygonCollection. Keywords: Cesium3DTileStyle, 3D Tiles styling, styling expression, conditions array, color expression, feature property, pointSize, ClippingPlane, ClippingPlaneCollection, ClippingPolygon, ClippingPolygonCollection, unionClippingRegions, inverse clipping, makeStyleDirty, style not applying, all tiles same color, style does not work, feature not colored, clipping not working, clip not showing, tileset not cut, how do I color buildings by height, hide features, cut a hole in a tileset.

Use when integrating Cesium ion assets into a CesiumJS app: loading ion-hosted 3D Tiles, terrain, or imagery, configuring the ion access token, uploading data for tiling, or deciding between ion SaaS and self-hosting. Prevents the missing-token blank globe (a 401 on every ion asset), the leaked-token security mistake (shipping a write-scoped or account token to the browser), the direct-constructor mistake on IonResource and the ion providers, and the demo-token-in-production mistake. Covers Ion.defaultAccessToken, IonResource.fromAssetId, Cesium3DTileset.fromIonAssetId, IonImageryProvider.fromAssetId, CesiumTerrainProvider.fromIonAssetId, the Cesium-hosted base assets, the upload and tiling flow, and self-hosting. Keywords: Cesium ion, ion access token, Ion.defaultAccessToken, IonResource, fromIonAssetId, fromAssetId, IonImageryProvider, CesiumTerrainProvider, createWorldTerrainAsync, createOsmBuildingsAsync, asset id, ion REST API, tiling pipeline, 401 unauthorized, 403 forbidden, ion token, asset not loadin

Use when a CesiumJS Geocoder widget search returns nothing, an ion geocode call fails, or a place name must be turned into a camera destination. Covers the GeocoderService interface, IonGeocoderService, PeliasGeocoderService, CartographicGeocoderService, the Viewer geocoder option, GeocodeType, IonGeocodeProviderType, and custom geocoders. States that CesiumJS and Cesium ion have no routing or directions API. Keywords: Cesium geocoding, GeocoderService, IonGeocoderService, PeliasGeocoderService, CartographicGeocoderService, GeocoderViewModel, Geocoder widget, geocode, GeocodeType, SEARCH, AUTOCOMPLETE, IonGeocodeProviderType, viewer geocoder option, custom geocoder, address to coordinate, place name search, routing, directions, geocoder not finding, search returns nothing, geocoder widget empty, geocode 401, how do I search for an address, how do I add place search.

Use when a CesiumJS click handler hits nothing, returns the wrong object, or reports a position at the wrong height, or when building distance and area measurement tooling. Covers scene.pick, drillPick, pickPosition, globe.pick, camera.pickEllipsoid, sampleHeight, clampToHeight, ScreenSpaceEventHandler input events, selectedEntity and the InfoBox, and geodesic versus straight-line distance. Keywords: Cesium picking, scene.pick, scene.drillPick, scene.pickPosition, pickPositionSupported, globe.pick, camera.getPickRay, camera.pickEllipsoid, sampleHeight, clampToHeight, sampleHeightMostDetailed, ScreenSpaceEventHandler, setInputAction, ScreenSpaceEventType, LEFT_CLICK, MOUSE_MOVE, selectedEntity, InfoBox, Cesium3DTileFeature, EllipsoidGeodesic, surfaceDistance, Cartesian3.distance, distance measurement, area measurement, pick returns nothing, click hits nothing, picked wrong object, wrong position, position at wrong height, model floats, measurement off, how do I get the coordinate I clicked, how do I select an

Use when configuring the CesiumJS sky, atmosphere, lighting, sun, moon, star field, or fog, and the sky renders black, the globe looks too dark or evenly lit, an atmosphere property has no visible effect, or the atmosphere is missing in 2D. Prevents the wrong-atmosphere-object mistake (sky atmosphere and ground atmosphere are separate objects with identically named properties), the disabled-lighting mistake (Globe.enableLighting defaults to false so there is no day-night terminator), the 3D-only mistake (SkyAtmosphere fades out in 2D), and the zero-length DirectionalLight error. Covers SkyAtmosphere, the Globe ground atmosphere, SkyBox, Sun, Moon, Fog, and the scene Light. Keywords: CesiumJS atmosphere, SkyAtmosphere, skyAtmosphere, skyBox, scene.sun, scene.moon, Fog, scene.light, SunLight, DirectionalLight, enableLighting, showGroundAtmosphere, atmosphereLightIntensity, hueShift, brightnessShift, sky black, no atmosphere, globe too dark, no day night terminator, sky is dark, no stars, atmosphere not showing,

Use when styling a CesiumJS surface with a Material, writing a CustomShader for a Model or 3D Tileset, or adding a screen-space PostProcessStage effect. Covers Material.fromType and Fabric JSON, the built-in material types, CustomShader modes and lighting, and the post-process stage pipeline including the built-in FXAA, bloom, and ambient-occlusion stages. Keywords: Cesium Material, Material.fromType, Fabric, CustomShader, CustomShaderMode, LightingModel, PBR, UNLIT, PostProcessStage, PostProcessStageCollection, PostProcessStageLibrary, fragmentShader, colorTexture, v_textureCoordinates, MaterialAppearance, uniforms, vertexShaderText, fragmentShaderText, GLSL, material not showing, material wrong color, shader error, shader does not compile, post-process no effect, screen effect not working, how do I color a surface, add a glow, write a shader in cesium.

Use when loading a 3D Tiles tileset into a CesiumJS scene, streaming a city, point cloud, or photogrammetry dataset, picking a tile feature, or tuning a tileset for detail and memory. Covers Cesium3DTileset.fromUrl and fromIonAssetId, the 3D Tiles 1.0 binary formats versus 1.1 glTF content, structured metadata, maximumScreenSpaceError, and Cesium3DTileFeature. Keywords: Cesium3DTileset, Cesium3DTileset.fromUrl, fromIonAssetId, Cesium3DTileFeature, 3D Tiles, tileset json, b3dm, i3dm, pnts, cmpt, glTF tile content, 3D Tiles 1.1, structured metadata, implicit tiling, multiple contents, maximumScreenSpaceError, cacheBytes, clippingPlanes, clippingPolygons, getProperty, tileLoad, tileFailed, tileset not loading, tiles missing, tileset not showing, tileset blank, CORS error, 401 tileset, 403 tileset, tileset at wrong place, how do I load 3d tiles, add a city to the globe, stream a point cloud.

Use when loading CZML, GeoJSON, TopoJSON, KML, or KMZ files onto the CesiumJS globe, and the data does not appear, sits flat on the ellipsoid instead of on terrain, or a second load call erased entities that were already shown. Prevents the load-versus-process mistake (instance load silently wipes prior entities), the clampToGround-default mistake (GeoJSON and KML geometry floats at height zero), the unwrapped-promise mistake (reading entities before the load promise resolves), and the missing-camera-canvas mistake for KML network links. Covers DataSourceCollection, CzmlDataSource, GeoJsonDataSource, KmlDataSource, the async load pattern, and teardown. Keywords: CesiumJS datasources, DataSourceCollection, viewer.dataSources, CzmlDataSource, GeoJsonDataSource, KmlDataSource, CZML, GeoJSON, TopoJSON, KML, KMZ, load vs process, clampToGround, dataSources.add, document packet, GeoJSON not showing, KML flat, CZML wiped my entities, polygons floating, data sits underground, network link, how do I load a GeoJSON fil

Use when a CesiumJS entity track does not move, an animation is frozen, a clock or timeline shows the wrong time, or a SampledPositionProperty fails to interpolate between its samples. Covers JulianDate, Clock, ClockViewModel, SampledPositionProperty, the Linear, Lagrange and Hermite interpolation algorithms, ExtrapolationType, and TimeIntervalCollection driving Entity.availability. Keywords: Cesium time, JulianDate, JulianDate.fromIso8601, JulianDate.fromDate, JulianDate.now, addSeconds, Clock, shouldAnimate, ClockStep, ClockRange, ClockViewModel, SampledPositionProperty, addSample, setInterpolationOptions, LinearApproximation, LagrangePolynomialApproximation, HermitePolynomialApproximation, ExtrapolationType, TimeIntervalCollection, TimeInterval, entity availability, time-dynamic data, interpolationDegree, animation not moving, animation frozen, entity not interpolating, track not animating, wrong time, clock not advancing, timeline stuck, how do I animate an entity, how do I play back a flight path.

Use when loading a glTF or glb 3D model into a CesiumJS scene, placing and orienting it on the globe, playing its animations, driving its articulations, or styling it with color and shaders. Covers Model.fromGltfAsync, modelMatrix placement, the up-axis and forward-axis, activeAnimations, and articulations. Keywords: Cesium Model, Model.fromGltfAsync, glTF, glb, 3D model, modelMatrix, eastNorthUpToFixedFrame, headingPitchRollToFixedFrame, upAxis, forwardAxis, activeAnimations, ModelAnimationCollection, setArticulationStage, applyArticulations, heightReference, customShader, model not showing, model wrong place, model at earth center, model on its side, model wrong orientation, animation not playing, how do I load a 3d model, add a glb file, place a model on the map.

Use when adding, stacking, or styling raster map imagery on the CesiumJS globe, and the globe shows no imagery, tiles return 401 or 403, layers draw in the wrong order, or a provider fails to construct. Prevents the direct-constructor mistake (calling new on a provider that requires an async fromUrl factory), the removed-readyPromise pattern, the unwrapped-promise error (passing a provider Promise to new ImageryLayer), and the layer-order confusion. Covers ImageryLayer, ImageryLayerCollection, every built-in provider, the synchronous versus asynchronous provider split, and layer blending. Keywords: CesiumJS imagery, ImageryLayer, ImageryLayerCollection, imageryLayers, fromProviderAsync, addImageryProvider, IonImageryProvider, BingMapsImageryProvider, ArcGisMapServerImageryProvider, OpenStreetMapImageryProvider, UrlTemplateImageryProvider, WebMapServiceImageryProvider, WebMapTileServiceImageryProvider, TileMapServiceImageryProvider, SingleTileImageryProvider, WMS, WMTS, TMS, MapTiler, basemap, no imagery, map

Use when adding elevation to a CesiumJS globe, choosing between Cesium World Terrain, a custom quantized-mesh endpoint, an ion terrain asset, or an ESRI elevation service, or debugging a globe that stays flat, terrain that never loads, or markers that float above or sink below the ground. Covers the async terrain factories CesiumTerrainProvider.fromUrl and fromIonAssetId, createWorldTerrainAsync, the Terrain async helper class, the Viewer terrain option and scene.setTerrain, ArcGISTiledElevationTerrainProvider, EllipsoidTerrainProvider as the flat fallback, the requestVertexNormals, requestWaterMask, and requestMetadata options, and elevation sampling with sampleTerrainMostDetailed. Keywords: CesiumTerrainProvider, fromUrl, fromIonAssetId, createWorldTerrainAsync, Terrain, fromWorldTerrain, ArcGISTiledElevationTerrainProvider, EllipsoidTerrainProvider, scene.setTerrain, terrainProvider, requestVertexNormals, requestWaterMask, requestMetadata, sampleTerrain, sampleTerrainMostDetailed, depthTestAgainstTerrain,

Use when positioning, flying, or constraining the CesiumJS camera, and a view refuses to update, the camera will not rotate, the camera ends up underground, or flight completion fires at the wrong time. Prevents the awaited-flyTo mistake (Camera.flyTo returns void, not a Promise), the stuck-camera bug after lookAt leaves a reference-frame lock in place, the degrees-versus-radians orientation error, and the camera-clips-through-terrain problem. Covers setView, flyTo, lookAt, lookAtTransform, flyToBoundingSphere, viewBoundingSphere, HeadingPitchRoll orientation, frustum types, and ScreenSpaceCameraController constraints. Keywords: CesiumJS camera, setView, flyTo, lookAt, lookAtTransform, flyToBoundingSphere, viewBoundingSphere, HeadingPitchRoll, heading pitch roll, endTransform, frustum, PerspectiveFrustum, OrthographicFrustum, ScreenSpaceCameraController, minimumZoomDistance, enableCollisionDetection, camera stuck, camera will not rotate, camera underground, wrong view, view does not update, flyTo does nothing

Use when adding points, billboards, labels, polylines, polygons, or models to a CesiumJS scene, building time-dynamic tracks, or debugging an entity that never appears, a billboard with no image, a polygon that stays invisible, a CallbackProperty that does not animate, or a scene that slows down once it holds many entities. Covers the Entity class and Entity.ConstructorOptions, the per-aspect graphics objects, EntityCollection, the Property system (ConstantProperty, SampledProperty, CallbackProperty, CallbackPositionProperty), material properties, parent hierarchy, availability, and the Entity versus Primitive selection rule. Keywords: Entity, EntityCollection, viewer.entities.add, PointGraphics, BillboardGraphics, LabelGraphics, PolylineGraphics, PolygonGraphics, ModelGraphics, ConstantProperty, SampledProperty, CallbackProperty, isConstant, CallbackPositionProperty, ColorMaterialProperty, PolylineGlowMaterialProperty, availability, entity not showing, billboard missing, polygon not visible, callback not ani

Use when rendering large static geometry datasets in CesiumJS with the low-level Primitive API, batching many shapes into few draw calls, draping geometry over terrain or 3D Tiles, highlighting a volume, or choosing between the Entity API and the Primitive API. Covers Primitive, GeometryInstance, appearances, GroundPrimitive, and ClassificationPrimitive. Keywords: Cesium Primitive, GeometryInstance, appearance, PerInstanceColorAppearance, MaterialAppearance, GroundPrimitive, ClassificationPrimitive, ClassificationType, geometryInstances, modelMatrix, vertexFormat, scene.primitives, PrimitiveCollection, primitive not rendering, geometry missing, ground primitive flat, primitive not showing, nothing draws, DeveloperError differing color, how do I draw many shapes, render geometry fast, batch geometry on terrain.

Use when a CesiumJS app leaks memory, slows down the longer it runs, crashes the browser tab, or shows a blank Viewer after navigating between views or remounting a component. Covers explicit WebGL teardown with destroy() and isDestroyed(), the order to tear down tilesets, primitives, data sources, and the Viewer, the tileset GPU budget (cacheBytes and maximumCacheOverflowBytes), the roughly 16 WebGL contexts per tab limit, WebGL context loss handling, and how to tell a real leak from a lost JavaScript reference. Keywords: destroy, isDestroyed, cacheBytes, maximumCacheOverflowBytes, maximumMemoryUsage, renderError, rethrowRenderErrors, webglcontextlost, CONTEXT_LOST_WEBGL, WebGL context budget, destroyPrimitives, DeveloperError, memory leak, heap grows, tab crashes, out of memory, context lost, app gets slow over time, too many active WebGL contexts, blank viewer after navigation, how do I clean up a Cesium viewer, why does my map slow down.

Use when a CesiumJS application runs slowly, drops frames, stutters during camera movement, drains battery, or streams 3D Tiles too slowly, and the cause must be measured and fixed with the right lever. Prevents the guess-first mistake (raising maximumScreenSpaceError blindly until the scene turns blurry), the continuous-render battery drain, request storms from unthrottled tile loading, and leaked Web Workers. Covers requestRenderMode, tileset level-of-detail tuning, Scene render-cost levers, RequestScheduler throttling, and the TaskProcessor Web Worker API. Keywords: CesiumJS performance, slow, low fps, frame rate, stutter, lag, jank, battery drain, GPU pegged, debugShowFramesPerSecond, requestRenderMode, maximumScreenSpaceError, foveatedScreenSpaceError, skipLevelOfDetail, preferLeaves, preloadWhenHidden, dynamicScreenSpaceError, Scene.fog, logarithmicDepthBuffer, msaaSamples, RequestScheduler, maximumRequestsPerServer, TaskProcessor, Web Worker, level of detail, LOD, 3D Tiles slow to load, how do I make C

Use when creating a CesiumJS application, constructing a Viewer or CesiumWidget, configuring widget toggles, render-quality options, or the WebGL context, deciding between the full Viewer and the bare CesiumWidget, or wiring the ion access token. Covers constructor options, defaults, the token ordering rule, and the baseLayer/terrain/dataSources data options. Keywords: Cesium Viewer, CesiumWidget, new Cesium.Viewer, constructor options, widget toggles, contextOptions, requestWebgl2, powerPreference, msaaSamples, scene3DOnly, requestRenderMode, Ion.defaultAccessToken, baseLayer, terrain, blank globe, black globe, viewer not showing, nothing renders, widgets cluttered, timeline showing, container not found, how do I create a map, how do I set up CesiumJS, set up a globe.

Use when setting up a CesiumJS application and deciding how Viewer, CesiumWidget, Scene, Globe, and Camera fit together, or when the render loop, requestRenderMode, or SceneMode behaves unexpectedly. Prevents the wrong-containment mistake (treating Globe as a sibling of Scene, or expecting a scene.viewer back-reference), the continuous-render battery drain, the stale-frame bug after a manual change, and any WebGPU backend assumption. Covers the Viewer versus CesiumWidget decision, the Scene containment graph, the per-frame event order, requestRenderMode, SceneMode morph transitions, and the Entity versus Primitive API tiers. Keywords: CesiumJS Viewer, CesiumWidget, Scene, Globe, Camera, render loop, requestRenderMode, scene.requestRender, maximumRenderTimeChange, SceneMode, SCENE3D, SCENE2D, COLUMBUS_VIEW, morphTo3D, preRender postRender events, scene3DOnly, Entity vs Primitive, WebGL2, WebGPU, blank globe, nothing renders, scene not updating, scene frozen, app uses too much battery, how do I set up a Cesium

Use when converting between geographic coordinates and CesiumJS positions, placing entities or 3D models on the globe, building local reference frames for oriented objects, or debugging positions that land at the Earth center, float above or below the globe, or read as NaN. Covers Cartesian3 ECEF math, Cartographic radians storage, Ellipsoid.WGS84 and the configurable Ellipsoid.default, Transforms local-frame matrices, and HeadingPitchRoll orientation. Keywords: Cartesian3, Cartographic, fromDegrees, fromRadians, fromDegreesArray, fromDegreesArrayHeights, Ellipsoid.WGS84, Ellipsoid.default, Transforms.eastNorthUpToFixedFrame, headingPitchRollToFixedFrame, localFrameToFixedFrameGenerator, HeadingPitchRoll, ECEF, WGS84, geocentric, modelMatrix, radians vs degrees, NaN position, off the globe, model at Earth center, entity in the wrong place, point is underground, how do I place a model on the map, convert lon lat to position, why is my coordinate wrong.

Use when upgrading CesiumJS between releases, when code copied from old tutorials or Sandcastle examples throws errors, when a constructor or utility suddenly fails after a version bump, or when deciding how to port legacy synchronous patterns to the modern async factories. Covers the 1.104 to 1.142 version matrix, the async-factory migration, and removed APIs. Keywords: CesiumJS version, upgrade CesiumJS, migration, breaking change, deprecated, readyPromise is not a function, tileset.readyPromise is undefined, tileset.ready is undefined, defaultValue is not defined, Cartesian3 is not a constructor, ModelExperimental, createWorldTerrain is not a function, async factory, fromUrl, fromIonAssetId, fromGltfAsync, CHANGES.md, code broke after upgrade, old example fails, how do I migrate, what version do I need, why does the old code throw.