Steam Frame (VR) and Godot

With the first hardware in the hands of some tech youtubers and open registration for the headset on steam, what is the state of VR in Godot?
Are there any issues with the VR controllers or the Steam Controller in Godot?
The headset running Linux is a huge plus, definitely one of the most interesting things about it to me.
I own two old Oculus Rifts, but since Meta bought them, they’ve just been paperweights to me. Never wanted to set up a Meta account. I have build some prototypes in Unity for the HMDs.
Thinking about getting back into VR experiments, only in Godot this time. Anyone here have any early experience with the Steam Frame yet?

Will the foveated rendering be available in Godot?

I’m impressed, that Half Life Alex will run on the device. Some interesting background infos in this video:

Bastiaan Olij, the main XR maintainer, had access to the Steam Frame ~8 months ago:

And here’s the steam documentation:

So, there’s your answer :wink:

4 Likes

Took me way to long to set it up under Linux with an older kernel. But now it’s working fine. I love that the frame is a standalone Linux device, really open for tinkering with it. Wireless streaming works like a charm for PCVR.

Other devs here building for VR with Godot?

@mux213 What are your suggestions to dive into development for the Frame? It’s all a little bit overwhelming and that with some Linux and VR background in my bag.

For now I’m just gaming … fatal that there is a steam sale at the moment. Not tested Godot or Blender yet, native on the device or streamed.

It’s crazy and little bit concerning, how many mods there are popping up, to inject VR into old titles.
That’s only possible because of AI. It’s not all vibe coded, but AI can do all the boring stuff to reverse engineer and to build the api interface. Before it wasn’t feasible to tackle such a task with only a few people.

We have an XR section here on the forum with information, and an XR channel on the godot Discord which is a good resource as well.

For running Godot on the Steam Frame, watch: https://www.youtube.com/watch?v=frFVHA4Orhw
And this video still is a decent getting started video: https://www.youtube.com/watch?v=shbHGhkh4NM

There is loads of info to be found in our manual

As for AI, I would be careful there. XR is still fairly new ground with not a lot of resources for AIs to be trained on. It’s just as likely to give you horrible implementations as good ones, and with more and more people using AI, it’ll learn on its own horrible output.
It is probably a userful tool for the investigation stage of modding, but I wager that any good mod is written by people with the required experience.

1 Like

Thanks for your links.
Yeah, I’m more on the skeptic side of AI, when I run tests it’s on a dedicated system and I’m cautious with mods that I run on my systems. I don’t want to vibe code Godot VR apps. It was just an observation of the development in the modding scene and the usage (with a lot success) of such agentic systems. They are a little bit too capable for my liking. It’s crazy what they can generate.

I’m currently developing and testing my “CyberDeck XR” on Linux targeting the Steam Frame (both streamed PCVR via Steam Link and standalone ARM64 builds) on Godot 4.7.2.stable. The OpenXR pipeline and Steam Frame controller bindings run remarkably smooth!
During application shutdown (via get_tree().quit(0)), I noticed two exit diagnostics:

  1. The disconnect error during OpenXR extension teardown (Issue #122238):
    “Attempt to disconnect a nonexistent connection from ‘’. Signal: ‘spatial_discovery_recommended’, callable: ‘OpenXRSpatialMarkerTrackingCapability::_on_spatial_discovery_recommended’.”

  2. The InteractionProfile RID leak at exit:
    “ERROR: 4 RID allocations of type ‘OpenXRAPI::InteractionProfile’ were leaked at exit.” (matching the 4 profiles registered in our openxr_action_map.tres).

I know these are harmless shutdown-order diagnostics that don’t affect runtime gameplay, but with 4.7.3 currently in beta / preparation, I was wondering if the teardown lifecycle fixes (like PR #123908) are already scheduled or backported for 4.7.3, or planned for 4.8?

Thanks for all your outstanding work on the OpenXR integration!

Both are indeed very minor and harmless issues, just haven’t bubbled to the top of the priority list yet.

1 Like