Alpha Release

OrcaXR

The spatial 3D printing slicer.

OrcaXR is web-native: use it in a desktop web browser or try the experimental spatial shell on an XR device such as the Galaxy XR. XR input and workflow qualification is still in progress.

Powered by XRBlocks

Launch Web App View GitHub
🌐

Web Native

Run directly in your browser. No installation required, instant access everywhere.

🥽

Experimental XR Shell

Try spatial controls on devices like the Samsung Galaxy XR while input and workflow qualification continues.

⚡

Powered by XRBlocks

Built on the robust XRBlocks framework for seamless 3D interactions and UI.

Advanced Usage

Connecting to a Printer

Chrome 142+ can connect directly to local HTTP Moonraker after Local Network Access permission:

  1. Add the OrcaXR page's exact origin to Moonraker cors_domains and restart Moonraker. For this hosted app, use https://orcaxr.martinez.fyi.
  2. Enter the full printer URL, such as http://192.168.1.50 or http://printer.local:7125.
  3. Approve Chrome's Local Network Access prompt. Use HTTP only on a trusted LAN because traffic and uploaded G-code are unencrypted.
  4. Fallback: use an HTTPS reverse proxy, or join the headset and printer to the same tailnet and use Extended Firmware with tailscale serve --bg http://127.0.0.1:80. Then enter the resulting https://printer.tailnet-name.ts.net URL.

External Slicer (Docker)

The in-browser WebAssembly (WASM) slicer has a hard memory limit of 4GB, which can cause out-of-memory crashes on extremely large or complex models.

To solve this, you can run the External Slicer via Docker. This offloads slicing to a dedicated server and uses a native CLI built from the pinned Snapmaker Orca v2.3.4 source instead of the browser WASM runtime. See the /server directory on GitHub for setup instructions. Chrome 142+ can connect to a trusted-LAN HTTP server after Local Network Access permission; use HTTPS for remote or untrusted networks.