ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #babylonjs
Stop killing your frame rate with excessive draw calls. Learn when to use InstancedMesh versus Thin Instances in Babylon.js to render thousands of objects efficiently.
When a child mesh appears in the wrong place after parenting, Babylon.js's world matrix order—parentWorld multiplied by childLocal—is usually the cause. Here is how to verify and work with it.
When rendering thousands of identical objects in Babylon.js, instancing drastically reduces draw calls. This guide outlines the minimal architecture, operational checks, data validation, and fallback strategies for efficient and reliable instanced rendering.
Learn how to reduce draw calls in Babylon.js by combining AssetContainers, InstancedMesh, and the SceneOptimizer. A practical guide with code, trade‑offs, and a step‑by‑step example.
Asset Loading Retry in Babylon.js Babylon.js exposes a SceneLoader option called retry that can be set per asset load, but the official documentation does not detail its default value or limits. In current releases the default behavior is to attempt a single load with no automatic retry; if the request fails, an error event is emitted and the asset is omitte
Establishing a repeatable development environment in Babylon.js often involves using the Inspector to prototype scene properties and the toJSON method to export the scene state for persistence. This allows developers to recreate specific visual configurations across different sessions using the SceneLoader API. While the serialization of the scene graph, mat