Babylon.js 9.18.0 Released
Babylon.js 9.18.0 is a focused maintenance update rather than a feature-heavy release, but it touches a few areas that matter in day-to-day engine work. The core fixes clean up PerfCounter min/max initialization, which should make performance metrics more trustworthy, and address a texture leak in the GS path when resizing, a bug that could show up as creeping memory use during window or canvas resizes.
There’s also a safety fix around XRGPUBinding before native fallback, which suggests Babylon.js is tightening its WebXR/native compatibility checks to avoid bad assumptions when hardware or platform support shifts. For teams experimenting with XR, that kind of guardrail can save time chasing platform-specific failures.
On the tooling side, Sandbox now applies persisted glTF loader options as soon as the page loads. In practice, that makes the browser-based testbed behave more predictably when revisiting scenes or sharing setup state, which is useful for artists, technical artists, and anyone debugging import settings.
Overall, this release looks like a patch-level cleanup pass: no breaking changes are called out, but the fixes improve profiling accuracy, memory behavior, and editor reliability. Developers already on Babylon.js 9.x should be able to upgrade with low risk while benefiting from the stability work.
- what
- Babylon.js 9.18.0 was released as a patch-style maintenance update with bug fixes in core engine behavior and Sandbox tooling.
- what
- PerfCounter min/max initialization was fixed, improving the reliability of performance measurements.
- what
- A GS texture leak during resize was fixed, reducing the risk of memory growth when the canvas or window changes size.
- what
- XRGPUBinding is now checked before native fallback, improving XR/native compatibility handling.
Small patch release with useful stability and tooling fixes
Follow JavaScript updates
See relevant stories in your personalized news feed.
Discussion