Oculus controller models don't load in XR
See original GitHub issueBugs
Repro playground: https://playground.babylonjs.com/#AM07G2#42
I tested with an Oculus Quest headset. When you enter XR (by clicking the GUI in the scene), you’ll notice that the models for the controllers disappear, and inputs such as teleporting are broken.
Additionally, the gamepadController
on the WebXRController
object is undefined.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
XR how to show oculus quest controller models on player ...
After some further poking around, I have found Oculus > VR > Prefabs contains an OVRControllerPrefab. However, it seems to not be working...
Read more >About the Oculus XR Plugin - Unity - Manual
Note that this currently requires a custom version of the URP provided by Oculus in order to work, and should not be enabled...
Read more >Troubleshooting a controller pairing issue with your Gear VR
It that doesn't work, try restarting your phone. ... Note: Not all games fully support the Gear VR controller. ... Right controller not...
Read more >VR in Unity: Managing Controller Input and Hand Presence ...
Once you have your XR plugins installed from the Package Manager you can access this menu via Window -> Analysis -> XR Interaction...
Read more >XR Interaction Toolkit Setup - MindPort
If you are not using VR Builder, you can set up the XR Interaction Toolkit ... Since no controller model is provided, you...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Assuming you were talking about the motion controller manager… Actually my problem was not directly with the motion controller manager but was similar to https://forum.babylonjs.com/t/web-xr-experience-not-working-in-babylon-4-1/9415, so more to do with the fact that there is a dependency with the babylonjs-loaders. I simply had to add:
import 'babylonjs-loaders';
to my main typescript file to solve it. (I didn’t have any loader before since I create my meshes procedurally in glsl).The moron controller manager should actually be included in your project automatically, this is why you get the generic controller. You can always load the oculus model directly (webXROculusTouchMotionController.ts) but the profiled moron controller should be working out of the box. Did you turn off the online repository?