BabylonJS/Babylon.js · error · Error

${context}: ${e.message}

Error message

${context}: ${e.message}

What it means

After a glTF buffer's data promise resolves, the loader slices a Uint8Array view at (byteOffset, byteLength). If that slicing throws (typically a RangeError because byteOffset+byteLength exceeds the buffer data), the underlying exception is re-thrown wrapped with the buffer's context path. This is a bounds-check failure on the resolved binary data.

Source

Thrown at packages/dev/loaders/src/glTF/2.0/glTFLoader.pure.ts:2066

        }

        if (!buffer._data) {
            if (buffer.uri) {
                buffer._data = this.loadUriAsync(`${context}/uri`, buffer, buffer.uri);
            } else {
                if (!this._bin) {
                    throw new Error(`${context}: Uri is missing or the binary glTF is missing its binary chunk`);
                }

                buffer._data = this._bin.readAsync(0, buffer.byteLength);
            }
        }

        return buffer._data.then((data) => {
            try {
                return new Uint8Array(data.buffer, data.byteOffset + byteOffset, byteLength);
            } catch (e) {
                throw new Error(`${context}: ${e.message}`, { cause: e });
            }
        });
    }

    /**
     * Loads a glTF buffer view.
     * @param context The context when loading the asset
     * @param bufferView The glTF buffer view property
     * @returns A promise that resolves with the loaded data when the load is complete
     */
    public loadBufferViewAsync(context: string, bufferView: IBufferView): Promise<ArrayBufferView> {
        const extensionPromise = this._extensionsLoadBufferViewAsync(context, bufferView);
        if (extensionPromise) {
            return extensionPromise;
        }

        if (bufferView._data) {
            return bufferView._data;

View on GitHub (pinned to 0592b347b8)

Solutions

1. Re-download or re-export the asset so the binary data matches the declared byteLength.
2. Ensure the .bin file paired with the .gltf is the correct, complete one.
3. Check buffer/byteLength values in the JSON against the actual binary size.
4. Validate with glTF-Validator, which reports out-of-range buffer references.

Example fix

// before: buffer.byteLength = 4096 but scene.bin is only 2048 bytes
// after: re-export so scene.bin is 4096 bytes, or fix the JSON
"buffers": [{ "uri": "scene.bin", "byteLength": 2048 }]

const binSize = binBuffer.byteLength;
for (const bv of gltf.bufferViews ?? []) {
  const buf = gltf.buffers?.[bv.buffer];
  if (buf && (bv.byteOffset ?? 0) + (bv.byteLength ?? 0) > binSize) {
    throw new Error(`bufferView out of range: needs ${bv.byteLength} bytes at ${bv.byteOffset}, bin has ${binSize}`);
  }
}

function viewFitsInBuffer(bv: { byteOffset?: number; byteLength?: number }, binSize: number): boolean {
  return (bv.byteOffset ?? 0) + (bv.byteLength ?? 0) <= binSize;
}

try { await loadAsset(); } catch (e) {
  if (e instanceof Error && /RangeError|buffer out of bounds|byteLength/.test(e.message)) {
    // re-fetch the binary data; it is likely truncated
  }
}

When it happens

Trigger: A bufferView/accessor whose byteOffset/byteLength lies outside the actual buffer data — e.g. the .bin file is truncated, a wrong byteLength is declared, or the wrong .bin was paired with the .gltf.

Common situations: Mismatched .gltf/.bin pairs after manual file management, partially uploaded/truncated binary chunks, files edited by scripts that change byteLength without regenerating data, GLB chunks cut short by a bad download.

Related errors

• ${context}: Uri is missing or the binary glTF is missing its
• Buffer access is out of range
• ${context}: Uri is missing or the binary glTF is missing its
• ${context}: Camera orthographic properties are missing
• ${context}: Invalid camera type (${camera.type})

AI-assisted analysis of BabylonJS/Babylon.js@0592b347b8 (2026-08-30). Data as JSON: /api/errors/1714f20e83421f1e. Report an issue: GitHub.