Immuch360 3.3.0-rc.0 build 32, for Android phones, tablets, TVs and the Meta Quest.
- 3D photos from one photo: on a computer, select photos, then "Make 3D (AI)".
- AI relief in the Quest: on a Quest 3 or 3S, the "AI relief" button of a flat photo, in the library or on a share, has the headset estimate the relief itself, with LiteRT, and shows the photo in 3D.
- 3D scenes: "Make 3D (AI)", then "3D scene", rebuilds a scene from one photo, in layers cut where the depth breaks, with the hidden bands filled in:
<name>_scene3D.jpg, a photo that carries the scene. - 360° panoramas: "Make 3D (AI)", then "360° panorama", invents the world around a photo:
<name>_360.jpg, 6144 x 3072, with the real pixels of your photo kept where they were, and, if you tick it, its 3D version<name>_360_3D.jpg. - Panoramas read everywhere: the 360° viewers of the phone, the TV, the Quest and the computers open a generated panorama with the badge "360° AI" and the sentence above, and outline your photo inside it for a few seconds.
- Where the files go: next to the original, never over it.
- The components, downloaded only when you ask
- Licences: Depth Anything V2 Small, LaMa, FLUX.2 klein base 4B, its VAE and Qwen3 4B under Apache 2.0; ONNX Runtime, MoGe-2, MI-GAN, stable-diffusion.cpp and ggml under MIT; Real-ESRGAN x4plus under BSD 3 Clause; LiteRT 2.3.0, inside the Quest APK, under Apache 2.0.
- Not in this build: no panorama without a suitable graphics card; the box keeps the type greyed with its reason, such as "The graphics card has 6.0 GiB of memory, 360° panoramas need 7.5 GiB", "No graphics card with Vulkan found" or "Integrated graphics share the computer's memory: too slow for panoramas" ("Try on integrated graphics (untested)" lets you try anyway).
