Quest 3 Controllers Not Showing

Hi,

I am currently trying to explore the VR possibilities with Meta Quest 3 in Omniverse. I have loaded the relevant xr extensions that gives me both the VR and AR tab in Omniverse. I can successfully stream the Omniverse scene to the Quest 3 by using either SteamVR or Quest link. However, the controllers are not showing, which means that I cannot interact with the scene or walk around. After spending a day searching for solutions I am now hoping to get receive some help from the community. In an official video from NVIDIA’s youtube channel the host seem to have the same problem as me, but instead of solving the issue they simply continued with their agenda. The “situation” can be seen around 19:09 where she mentions to a guest that the controllers are not working. Beside that I actually am in an immersive state, I think the problem is the same.

Have any of you had the same problem or an idea to how to fix it?

Video:

This video is VERY old. You really need to make sure you are fully up to date with the latest kit 108 install of USD Composer. GitHub - NVIDIA-Omniverse/kit-app-template: Omniverse Kit App Template

You need to use the OPENXR configuration. Do not use the STEAM or the Quest. It must be OPENXR.

Install the “XR CORE” from the Extension Manager

Hi Richard,

Sadly, it didn’t help to update my Kit App Template version to 108. I have XR Core installed and I can still immerse myself into the world through the headset. However, the controllers are still not appearing (I have checked the “show controllers” option).

Do I need to have any specific extension for the Quest 3 controllers?
Alternatively, how would you suggest I work around this issue?

Please include all of these 5 extensions in your kit file and rebuild to make sure these are all working.

“omni.kit.xr.ui.window.profile” = {}
“omni.kit.xr.ui.window.viewport” = {}
“omni.kit.xr.ui.stage” = {}
“omni.kit.xr.system.openxr” = {}
“omni.kit.xr.system.simulatedxr” = {}

I want to confirm I have the exact same issue. I first installed omni.kit.xr.bundle.apple_vision_pro which I believe added the extensions Richard mentioned. I did explicitly add those 5 extensions to my kit file just in case, but I don’t think anything extra was installed after building.

It’s also worth mentioning I’m only able to connect my Quest to a remote Omniverse instance using the ‘System OpenXR Runtime’ setting, and not via the ‘CloudXR Runtime (5.0)’ setting. If my understanding is correct, CloudXR Runtime support is out only for AVP (via CloudXR Framework) at the moment, but not for Quest. If that’s not the case, I’d love to learn how to build a Quest client for the CloudXR Framework vs the good ol’ CloudXR way.

I have a different set of issues on my AVP, but this is a story for another post.

I hope I’m just doing something silly and there’s an easy resoluton.

Cheers,
Krasi

I have recently learned that the AVP bundle intentionally disables the controllers, because an AVP does not have them. So you may want to flush that build and start over. Then just install those 5 extensions again.

Thank you Richard, now the controllers work. I can confirm these 5 extensions are what’s needed to enable VR with controllers on Quest:

“omni.kit.xr.ui.window.profile” = {}
“omni.kit.xr.ui.window.viewport” = {}
“omni.kit.xr.ui.stage” = {}
“omni.kit.xr.system.openxr” = {}
“omni.kit.xr.system.simulatedxr” = {}

I couldn’t see this documented anywhere, especially on GitHub. Perhaps it would be useful to have a section about XR. In any case, this was very helpful, thanks again.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.