Godot's Android XR Story Just Got Real. The OpenXR Vendors Plugin v5.1 Is the Update That Closes the Gap.

Godot just shipped version 5.1 of its OpenXR Vendors plugin, and for anyone watching open-source XR development, this is the release that finally puts Android XR support on equal footing with Meta Quest inside the engine. The update landed on May 19, with maintainers Bastiaan Olij, David Snopek, and Fredia Huya-Kouadio (the same trio who have been carrying the Godot XR roadmap for years) bundling in trackables, dynamic resolution, unbounded reference space, automatic streaming-client launch for Direct Preview, and the new XR_ANDROID_mouse_interaction extension. It is a focused, deeply technical release, and it lands at exactly the right moment.

What the OpenXR Vendors plugin actually does

For anyone new to the Godot XR stack, here is the short version. Godot ships with OpenXR support in core, which gets you cross-vendor rendering, head and controller tracking, and the standard input model. The OpenXR Vendors plugin is a separate GDExtension that wraps vendor-specific extensions on top of that core, so you can opt into features that only one runtime supports without bloating the main engine. Meta passthrough, scene understanding, Pico-specific eye tracking, HTC face tracking. All of that lives in the Vendors plugin.

Until recently, the Android XR side of the plugin was sparse. Samsung Galaxy XR shipped late last year and XREAL's Project Aura is on the calendar for the back half of 2026, but Godot developers targeting either platform had to write a lot of workarounds for missing extensions. Version 5.1 closes most of that gap in a single push.

The features that actually matter

Trackables is the headline. The new XR_ANDROID_trackables wrapper exposes information about the physical space the user is in, including planes, anchors, and meshes representing real-world surfaces. This is the foundation for any mixed reality experience that needs to place virtual objects on real floors, walls, or tables, and the lack of it has been the single biggest reason indie Android XR development has felt incomplete. With v5.1, a Godot project can query the runtime for spatial geometry the same way it would on Meta Quest, with the same scene-understanding mental model.

Dynamic resolution is the performance feature. Android XR runs on a mix of hardware tiers, from Samsung's Snapdragon XR2 Gen 2 in the Galaxy XR down to whatever ships inside Project Aura's tethered configuration. Dynamic resolution lets the runtime scale the render target down when the GPU is under load and back up when it has headroom, so a developer targeting variable hardware does not have to lock to the lowest common denominator. This is the same trick Meta exposes through its own dynamic resolution extension on Quest. Having it as a one-line opt-in for Android XR through the same plugin is exactly the kind of consistency that makes cross-platform development work.

Unbounded reference space is the third spatial feature. It tells the runtime that the user is not confined to a fixed playspace, which matters for AR-style apps where someone might walk across a room or down a hall. The OpenXR specification has had this concept for a while, but vendor implementations vary. Godot v5.1 wraps the Android XR version cleanly so developers do not have to special-case it.

Direct Preview is the quiet workflow upgrade

The feature that XR developers will probably appreciate most day to day is the automatic streaming-client launch for Direct Preview. Direct Preview is Android XR's equivalent of Meta's Quest Link or Pico's Streaming Assistant, the desktop-to-headset development mode that lets you iterate without rebuilding and reinstalling the APK every time. Before v5.1, getting Direct Preview running with Godot required manual setup steps. The new version handles the streaming client launch automatically when you start a Direct Preview session from the editor.

That sounds boring on paper, but anyone who has done VR development knows the truth. Build, deploy, test, fix, repeat is the actual work, and every minute shaved off that loop compounds across the lifetime of a project. Plugging Direct Preview directly into Godot's editor workflow means an indie developer can iterate on Android XR at roughly the same speed as iterating on Quest. That has not been true for the past six months.

Mouse interaction is the canary

The XR_ANDROID_mouse_interaction extension is the smallest feature in the release and arguably the most informative. It exposes mouse input to XR applications, so a developer can build apps that respond to a Bluetooth mouse paired with a headset or glasses. On the surface this looks like a productivity-app feature, and that is where it will appear first. Spreadsheets, documents, anything where mid-air pinch gestures are slower than a real mouse.

What it tells you is more interesting. Android XR is being shaped to accept any input modality, not just hand tracking and controllers. That is a signal about where Google sees the platform going. Audio glasses, display glasses, and headsets are all under the same OS, and the input layer is being abstracted to accommodate all of them. The Vendors plugin picking up mouse support this release is one piece of that broader picture landing on the open-source side of the stack.

Why this lands the same week as the Catalyst Program

Two days before v5.1 dropped, Google opened applications for the Android XR Developer Catalyst Program, which explicitly lists Godot alongside Unity, Unreal, and Kotlin as a supported toolchain. The timing is not a coincidence. The Catalyst Program needs Godot developers to actually have shippable tooling. The Vendors plugin v5.1 makes sure they do.

That timing matters for indie XR teams in particular. Unity has well-documented friction around pricing and seat licensing. Unreal's royalty model is awkward for small VR economics. Godot is the engine that costs nothing and asks nothing back, and it now ships with first-class Android XR support funded in part by the same coalition (Google, the Godot Foundation, and W4 Games) that committed publicly in November 2025 to bringing Godot up to platform parity.

If you have been waiting for the moment when open-source XR development becomes a real path on Android XR rather than an aspirational one, this is it. The plugin is available from the Godot Asset Store, the Asset Library, or the GitHub release page. The minimum supported Godot version is 4.6.