Unity Unity support for OpenXR in preview

I'm testing with Oculus Rift now, and it seems that the input from the thumbstick isn't passing values through, as it won't show in the controllerSample at all. I've even tried adding the OpenVR variant but nothing, as shown in the picture. I cannot get any values through the XR interaction toolkit either, whereas with the Vive 1 everything else works except the haptic and socket hovering as mentioned prior.

I got VR hands working and reading trigger and grip values with Rift, but for some reason these values don't get passed to the toolkit through references.

 

I just tested this, no change. And that would be strange anyway as the Oculus Touch feature profile in the documentation specifies the action should be mapped to thumbstick on the controller. And yes of course I have the profile on, as I already tested Vive with its profile and it works. What I mean is, even when I open the "ControllerSample" scene which comes with OpenXR, and you have the controller mockups which display all inputs, the joystick is not recorded even in there on the default InputActions, and specifying the action to oculus touch controller as I've tried still brings no change.

All the other bindings DO work though in the controller sample, I get input for the primary and secondary Oculus Touch buttons, trigger and grip normally. Only thing that does not go through is input from the joystick, so I assume it is something to do with that specifically. Although binding these other controls to the XR interaction toolkit still doesn't work very well, but there is some level of registering at least. Without the joystick cannot do locomotion/snap turning at all though, which makes testing very difficult.

In the image I show how I changed the input the way you told to, with no better results. The way I understood the actions is that adding more bindings to an action won't negatively affect the functionality of the existing ones, correct? Also is the suggested method to always just have a reference to the XRController or not, as I've been trying to add the more specific inputs like the documentation suggested.

 

Not the OP, but I also observed that when using SteamVR, sticks are not detected, but when using Oculus, they are detected (Rift CV1).


Filed two bug reports this morning, posting here for visibility to other users in case anyone has found fixes.

• 1304188: When using Oculus with OpenXR and a Rift CV1, a black circle appears on screen.
  Edit: Duh.
  
• 1304190: OpenXR: SteamVR renders a distorted view to the HMD (Oculus Rift CV1)

Really exciting to see cross platform XR support, super pumped about this

 

Hey, I did some more testing. It actually works fine if I build for pc. The issue arises when trying to debug with Unity play mode. It looks like the image is duplicated down the middle. It's like looking at a VR display without any lenses. I tried to take a screenshot but oculus screenshot tool just gives a black screenshot in Unity play mode.

 

Yes, I was indeed using SteamVR runtime, just swapped to Oculus and it tracks, so that was the problem. Hopefully that can be fixed in the next version.

Can also confirm this black box appearing when using Oculus as Iron-Warrior said. And I also meant to report about the distorted view with SteamVR and Oculus as well.

 

DId the black circle disappear when disabling the occlusion mesh? I just did XRSettings.useOcclusionMesh = false, but the black circle remains. Also as the stick won't work in SteamVR runtime, do you know how to change the runtime to Oculus also in the build, as the settings in the OpenXR only affect the editor instance?

 

I am using MRTK 2.5.3. and the update OpenXR Plugin Version 0.1.2-preview.2 is not tracking any device (HMD or controller) (preview.1 is fine).

 

Yeah it does. I'm using MRTK if that helps. I also have to restart unity sometimes to get it to work at all.

Edit: steamvr works but there is weird warping on both quest 1 and rift s. like there is motion blur.

 

Yes, that was it! Thanks!

 

Hi,

Since upgrading my project from 2019.x to 2020.2 and setting up OpenXR I can no longer access the Primary Button on a Vive controller (above the thumbpad, to be clear). All other Vive inputs are fine, build for Oculus too, all inputs work. Not sure why, its the only button not working for Vive. I've provided images of my projects XR settings below.

I am using the below CommonUsages, which worked in 2019.

Code (CSharp):

1. if (Controller.inputDevice.TryGetFeatureValue(CommonUsages.primaryButton, out bool primaryButton))

Spoiler: Images

 

Hi I think I figured out what caused the issue. My project was set to "verify saves" which kept prompting to save every single time something changed.

 

Does "Unity XR Input" still work with this OpenXR plugin?

https://docs.unity3d.com/Manual/xr_input.html

My game uses XR Input and the old input manager to query the input states, what I found so far is that the buttons on the VR controllers (Oculus Quest through Link) seem working fine but the axis input are missing. Is this expected?

Also when enabling Open XR in XR settings, the Oculus toggle is grayed out, and it seems to be launching steam VR instead of Oculus when the game starts, is there a way to let it select the most propriate runtime?

 

OpenXR only works with the new Unity action input system as far as Im aware. You’ll want to switch over to that in all regards to input.

 

Will this come to Unity 2019.4 LTS too? Any rough estimate when that will be the case? Either preview or final.

 

I don't think so. Scroll up (first few) and you will see the discussion and it doesn't look that way.

I recently upgraded my 2019.4 LTS to 2020.2 just to accommodate this package. I was reluctant at first, but I learned that 2020 will go LTS fairly soon.

You might want to carefully examine the effects before upgrading to 2020 though as some assets and features might not work properly in 2020. In my case everything seems to be working OK and it was well worth it.

 

So we’ve found there are some issues with the OpenXR and Index in the grip readout. The index grip seems to be highly sensitive, a light touch gets you to the full 1 value. Is there anyway around this?

 

Is XRInputSubsystem.TryRecenter() not doing anything a bug or should we use some replacement from the new Input System?

 

I have a Quest 2 with Virtual Desktop. I have SteamVR Beta 1.16.1 and have many SteamVR games that work great.

I am trying to get OpenXR in Unity working with this setup. In theory it should work.

I followed this great video: How to Setup XR Toolkit's Action-Based Input in Unity - YouTube that shows how the Action Based Input works.

The end result is when I hit play in the editor, it opens SteamVR and I enter my scene. The head tracking works great, but the controllers do not.

When I look at the properties of the controllers in the rig they have all the actions set up from the Presets that the video walks you through setting up. I also have the rig itself set up with the input script on it mentioned in the video.

Supposedly the 1.16.1 SteamVR beta passes all of the OpenXR tests for 1.0.

UPDATE: I decided to try the Oculus link cable and get the same results do it isn't specific to virtual desktop.

UPDATE 2: Just for reference here is a picture of the SteamVR window. It shows the headset and controllers are tracking. When I hover the mouse over the icons that is what they say.

https://drive.google.com/file/d/1l5afV1mSR4DI4lvE0k2pGPtW2C28AZ41/view?usp=sharing

Any ideas why the controllers don't work?

 

ive seen 2 people post about the index grip issue, it wont let me make a post so im posting it again here. index controller grip is considered gripping on any touch at all, so if you are just holding the controllers it will grip, and it is very hard to drop items. if anyone found a solution help plz.

 

This is what I am doing:

Code (CSharp):

1.  
2.  
3. [SerializeField]
4. private float grabActivationThreashold = 0.5f;
5.  
6. private bool IsGrabButtonActive => grabAction.action.ReadValue<float>() > grabActivationThreashold;
7.  
8.  

If you are using

isTriggered 

then maybe but as far as I can tell (with float) it is NOT all or nothing. It seems to work its way from the bottom of the grip to the top. The more fingers you put on the grip, the higher this value will be, ending at 1. I can swear it takes pressure into consideration too, but I haven't tested this out. Just try it out.

 

How do you turn off occlusion mesh? I've tried setting:

XRSettings.useOcclusionMesh = false;

and it doesn't do anything about the black box in the upper right.