babylonjs-loaders 9.16.2 → 9.17.0

package/babylonjs.loaders.d.ts

@@ -8522,8 +8522,19 @@ declare namespace BABYLON {
         private _unzipWithFFlateAsync;
         private _parseAsync;
         /**
-         * Applies camera limits based on parsed meta data
+         * Extracts the safe-orbit camera limits from parsed splat metadata, or null when the file
+         * carries none. Exposed on the loaded mesh (GaussianSplattingMeshBase.safeOrbitCameraLimits)
+         * so consumers can apply/track them regardless of the active camera type.
          * @param meta parsed splat meta data
+         * @returns the parsed safe-orbit limits, or null
+         */
+        private static _ExtractSafeOrbitLimits;
+        /**
+         * Applies safe-orbit camera limits parsed from the file metadata to the scene's active
+         * ArcRotateCamera. No-op when no limits are present, `disableAutoCameraLimits` is set, or the
+         * active camera is not an ArcRotateCamera — in which case consumers can still read the limits
+         * from the loaded mesh's `safeOrbitCameraLimits` and apply them themselves.
+         * @param limits parsed safe-orbit limits (see _ExtractSafeOrbitLimits)
          * @param scene
          */
         private applyAutoCameraLimits;
@@ -9381,7 +9392,14 @@ declare namespace BABYLON {
          * cheap per-node frustum test every frame so the off-screen LOD bias tracks camera rotation. The LOD
          * re-evaluation is throttled to at most every {@link _lodUpdateInterval} frames once the camera has
          * translated far enough, but also runs immediately whenever a node enters/leaves the frustum (so its
-         * detail upgrades/downgrades promptly) or a cap change forces it. Active ranges rebuild on any LOD change.
+         * detail upgrades/downgrades promptly), a node whose cooldown just expired still needs to switch LOD,
+         * or a cap change forces it. Active ranges rebuild on any LOD change.
+         *
+         * The cooldown-expiry trigger lets a node reach its already-computed target level as soon as its
+         * cooldown clears, rather than waiting for the camera to move. This matters right from load: a
+         * node's base-layer decode is itself applied as a switch (from no active level to the base one), so
+         * it starts the same cooldown a later switch would — this trigger is what lets the node progress past
+         * that base level promptly once it expires, even at a fixed camera pose.
          */
         private _onLodFrame;
         /**