Always use the wasm64 binary. Use only when you control the runtime environment and know Memory64 + SIMD are available. You must serve scichart-64.wasm. The wasm64 loader JS is bundled with your app, not served. (Union / one-wasm build: one binary serves both 2D and 3D, so there is no separate 3D file.)
Automatically use the wasm64 binary when the browser supports both Memory64 and SIMD, otherwise fall back to the standard wasm32 binaries. You must serve scichart-64.wasm alongside the standard binaries. The wasm64 loader JS is bundled with your app, not served. (Union / one-wasm build: one binary serves both 2D and 3D, so there is no separate 3D file.)
Never use the wasm64 binary. Always use the standard wasm32 binaries. This is the default.
Generated using TypeDoc
Defines how the WebAssembly Memory64 (wasm64) engine variant should be used by SciChart.
wasm64 lifts the wasm32 4GB heap limit but is supported by fewer browsers (Chrome 133+, Firefox 134+, not Safari as of 2025) and carries a per-operation performance cost from 64-bit pointers. It is therefore opt-in and always falls back to the standard wasm32 (SIMD / non-SIMD) binaries when not used.
The wasm64 binary is built with SIMD, so it is only served when both Memory64 and SIMD are supported.
See SciChartDefaults.useWasm64 for usage.