# GalaxyQuest v0.1.11 Fixes Cannon Aiming in Super Mario Galaxy VR Diorama

> GalaxyQuest v0.1.11 fixes cannon aiming in the diorama view for Super Mario Galaxy on Meta Quest headsets.

- Published: 2026-11-19T12:39:02Z
- Score: 8/10
- Tags: wii, vr, decomp, port, ai
- Port / platforms: Wii -> VR headset (Quest) (Port)
- Web page: https://emu-radar.customfw.xyz/news/galaxyquest-v0-1-11-vr-port/
- Sources: https://github.com/bigmak94/GalaxyQuest/releases/tag/v0.1.11

GalaxyQuest v0.1.11, a native virtual reality port of Super Mario Galaxy for Meta Quest headsets written with Claude Opus 5.5 in Claude Code, is out with a fix that lets players aim cannons inside the diorama view.

Built on the Petari decompilation project, GalaxyQuest runs the Wii game as a 3D tabletop diorama or on a virtual screen via OpenXR. The port requires your own disc files and a Meta Quest 2, 3, or 3S headset, and movies are included by default during conversion.

## What Changed in v0.1.11

The update fixes cannon control in the diorama mode with the giant screen off. Previously, a cannon showed from outside with its sight on the HUD panel, making shots hard to judge. Once Mario enters a cannon, the cannon's own view appears on the screen, as on the giant screen. Point at the screen to move the sight (near the edges the view turns), press **A** to fire, or pull the right trigger to climb back out.

## How to Try It

1. Enable developer mode on your Meta Quest headset, connect it via a USB data cable, and allow USB debugging.
2. Download **GalaxyQuest-Installer-windows-x86_64.exe** from the [GitHub release](https://github.com/bigmak94/GalaxyQuest/releases/tag/v0.1.11).
3. Open the installer, choose your Super Mario Galaxy disc image or extracted folder, and click install.

The installer includes the APK, Python, DolphinTool, and Android platform-tools. Allow about 16 GB of free space on your PC (10 GB for an extracted disc) and 7 GB on the headset. Manual installation files for macOS and Linux are available on the release page and covered in the README.
