Troubleshooting

All F13LD tools render geometry via WebGL. The Bundle tool requires WebGL 2 specifically — a black canvas with no error message is the symptom when it's missing.

• Older iOS / Safari — WebGL 2 support gaps on some devices
• Chromium-based browsers with hardware acceleration disabled
• Firefox with webgl.disabled set to true in about:config
• Corporate machines with GPU driver restrictions or remote desktop sessions

• Run the self-test above — it will report WebGL 1 and WebGL 2 status directly
• Visit get.webgl.org — if the spinning cube is missing, WebGL is blocked at the browser or system level
• If only the Bundle tool fails and the others work, WebGL 2 is the specific gap

• Chrome / Edge: Settings → System → enable "Use hardware acceleration when available" → relaunch
• Firefox: navigate to about:config, search webgl.disabled, set to false
• Safari on iOS: update to the latest iOS version — WebGL 2 support was patchy before iOS 15
• If on a corporate machine: try a personal device or mobile (cellular, not WiFi) to confirm the issue is policy-related

F13LD.mesh uses the Manifold WASM library for boolean operations and mesh export. Manifold requires cross-origin isolation headers (COOP / COEP) to enable multi-threaded execution — and these headers are not currently available on GitHub Pages.

This is a known architectural limitation, not something fixable on your end. The tool will load and the preview will render, but heavy operations (boolean union, level-set export, 3MF generation) may stall or produce no output.

• Mesh tool loads and renders the viewport fine
• Clicking Export or running a boolean op does nothing, or spins indefinitely
• Browser console shows SharedArrayBuffer is not defined

• No workaround available on GitHub Pages — this is a hosting constraint, not a browser setting
• Migration to a host that supports custom response headers (Cloudflare Pages, Netlify) is planned and will resolve this permanently
• If you need the export workflow urgently, contact support — we can discuss interim options

F13LD tools are hosted on GitHub Pages. Corporate, hospital, and institutional networks frequently block github.io domains or restrict CDN resources loaded by the tools (Google Fonts, etc.).

• Users on hospital, medical device, or pharmaceutical company networks
• University or research institution networks with restrictive firewall policies
• Users with aggressive browser extensions (uBlock Origin in strict mode, Privacy Badger)

• Switch to cellular data (turn off WiFi) and try again — if it loads, the network is the culprit
• Try a different browser with all extensions disabled (incognito mode in Chrome disables most extensions by default)
• Ask your IT department whether github.io is on the blocklist

• Use a personal device on a home or cellular network
• Whitelist mshomper.github.io and fonts.googleapis.com in your browser extension settings
• Request an IT exemption for github.io — the tools are read-only browser apps, no data is transmitted

WebGL requires GPU hardware acceleration. If your browser has it disabled — either manually or by policy — the canvas context fails silently and the viewport renders black or never initialises.

• Remote desktop sessions (Citrix, RDP, VDI) — GPU passthrough is rarely enabled
• Virtual machines without GPU drivers
• Users who previously disabled hardware acceleration in browser settings
• Some older integrated Intel graphics on Windows with outdated drivers

• In Chrome, navigate to chrome://gpu — look for "Hardware accelerated" next to WebGL entries. "Software only" means the GPU is bypassed
• Check if you are on a remote desktop or VDI session — these almost never support GPU passthrough
• Run the self-test above — the GPU renderer field will show "SwiftShader" or "llvmpipe" if software rendering is active

• Chrome / Edge: Settings → System → enable "Use hardware acceleration when available" → relaunch the browser
• Update your GPU drivers — particularly relevant for older Intel integrated graphics on Windows
• If on a remote desktop session: access the tools from a local machine instead
• As a last resort: Chrome allows forcing WebGL with the flag --use-gl=swiftshader, but performance will be very slow