Official Unity support for OpenXR in preview

So I seem to be getting some headset jitter/warping when I use my Oculus Quest 2 (In Link mode!) in OpenXR. Anyone else getting this, or is it something I should be looking at more deeply?

 

After upgrading to v 1.1.1 of the plugin it seem like controller rotation has changed for the Touch controller. The forward vector of the controller is now rotated about 45 degrees up. Tested it in a new blank project with a new XR rig. Downgrading to 1.0.3 fixes it.

Is this an intentional change?

 

Hey everyone,
I don't know if anyone else has this problem, but when I click play after setting up everything for openXR the runtime doesn't automatically set to oculus (which is what im using) so my headset stays on the dashboard and doesn't play the app in the editor or build.

It only works when I manually set it to Oculus which is editor only so its only a small fix.
I've followed every tutorial I can find and they all have me do the same thing so I don't know if its a bug or I've missed something.

Also want to note that I changed XR manager to oculus only and that works perfectly so it only happens when I try to use OpenXR

 

The work around doesn't seem to work for WMR-G2 (with no error) & has an error on HTC Vive.
* Do you plan to have some fixes in 2020.3.6 LTS?
* Are any of these fixes in newer non-LTS Unity versions?
* Also WMR without OpenXR has very slow / laggy tracking & G2 doesn't work in it (but haptics do). Anyone know why?

 

I have the G2 working on latest 2020 (LTS) relase (2020.3.5f1) with OpenXR

 

Yes thats correct.

I'm asking the person who had it. Will get back on this.

Haptics are working for you? Can you share some code for how the invocation looks to get it working?
To clarify G2 works with OpenXR just not haptics for me.

 

"What is the error on the HTC vive?"
-- So he didn't get an error either I guess. Just didn't work. Same as WMR G2.

 

Ok got it working. I'm not sure why it didn't work before. Maybe I had the channel set wrong or maybe my amplitude was wrong

 

Hello! Quick question so I am sure I am not making a mistake: we are starting production on a VR project using 2020.3 LTS. We plan on having something out in the next 6 to 8 month. Is it ok to use OpenXR or still too risky with our timeline? Should we stay on the classic steamVR/Oculus plug-in?

 

I'll Bump and reiterate an earlier post I made:

Are there any issues with the Quest 2 in OpenXR in Link Mode? All of my Recent OpenXR builds (using SteamVR as the OpenXR Runtime) have had some serious HMD jitter while using a Quest, but it apparently runs perfectly fine on a Vive or Index from testing reports.

I'm trying to figure out whether this is a Unity Issue, an Oculus Issue, a SteamVR issue, or a combination of all three...

 

Related to this, on the OpenXR Plugin page only WMR and Hololens 2 are shown as "fully test and officially supported". Is there a timeline or process for other platforms (mainly Oculus PC and OpenVR) to be added to this list? Not looking for anything concrete.

 

Sounds good, looking forward to it.

 

There was a discussion earlier on this thread about debugging haptics with OpenXR + G2, does this mean that haptics is available with OpenXR, or am I misreading that?

 

Hi! I'm working on an app for the Hololens 2. I would like to add Visual Effects with the VFX Graph, so I need to use the Universal Render Pipeline (URP). Just as a test I created a new project with the 3D template and followed this tutorial for the setup (I'm new): https://docs.microsoft.com/en-us/wi...ity/tutorials/mr-learning-base-02?tabs=openxr. Instead of using the samples I placed just a cube in the scene, built and deployed it on VS. It worked as expected on the Hololens. For some reason, I had to set the visibility of the spatial awareness to none to see the cube and make it work (default MRTK config files for OpenXR).

Then I added the URP, the URP-Asset and updated the material of the cube. To improve the performance I set the quality level to very low and unchecked the setting Optimize Mesh Data. And once done, I built and deployed on VS again. Well, it doesn't start. After 10 min loading, I decided to stop waiting and tried again with no success.

I'm using:

• Visual Studio Community 2019 16.9.4
  
  
• Unity 2020.3.1f1 (LTS)
  
  
• MRTK v1.0.2103.3 beta (MRT-Fundation 2.7.0. preview 3)
  
  
• MR OpenXR Plugin 0.9.2 preview
  

I would really appreciate some help! I do not understand why the Hololens can't load the project. It is just a cube! Does URP work with OpenXR?

Thank you very much in advance.

Laura

 

Does this mean OpenXR plugin supports Steam VR devices, such as HTC Vive and Valve Index, out of the box without requiring OpenVR/SteamVR plugins ? Last time I tried, I could not get input (with Unity new input system) work for SteamVR devices (HTC Vive) without mentioned plugins

 

Would it be possible to change the FOV in openXR ?

 

Hello.
Primary 2d axis click does not work in input system for Oculus Quest.
According to https://docs.unity3d.com/Packages/c...al/features/oculustouchcontrollerprofile.html
primary 2d axis is not listed although it works for control. But pressing the joystick does not respond.
XR Interaction Debbuger shows primary 2d axis click correctly.

 

Thanks,

thumbstickClicked

works!
So it is better to use a

thumbstick

instead of a

primary2Daxis

too?

 

Je ne pense pas que le plugin SteamVR utilise OpenXR - le runtime SteamVR OpenXR n'est pas encore hors de l'aperçu du développeur.










192.168.100.1 192.168.1.1

 

Couple questions:

• We can select a preferred Editor OpenXR runtime in the OpenXR tab of Project Settings...is it possible to expose this functionality to builds/users? One use case is just so we can select the runtime in builds ourselves to test that they both work, as well as allowing users to pick their preferred runtime.
• Is there a clean way to have both OpenXR and Oculus plugins available to a project? When I select OpenXR as a plug in provider it greys out Oculus. The purpose here is that long term we'd like to use OpenXR and would like to be able to mainly use it right now, but until Quest support is available use Oculus for Quest builds (I'm guessing I could probably toggle them on/off in my build script, but figured I'd ask here first).

 

@Iron-Warrior
To specify the runtime, set the json path of the runtime in either the registry or an environment variable before initializing OpenXR. Therefore, Unity does not have that feature.

https://docs.unity3d.com/Packages/com.unity.xr.management@4.0/manual/EndUser.html
https://github.com/KhronosGroup/OpenXR-SDK-Source/blob/master/specification/loader/runtime.adoc

It depends on the current runtime, but it is a bit more convenient to use my library.
https://forum.unity.com/threads/unity-support-for-openxr-in-preview.1023613/page-5#post-6972887

 

Any updates on fixing the offset VR controller models when using OpenXR vs. the Oculus / Steam plugins?

 

I'm not entirely sure what you're saying here. Are you saying that because selection of runtime happens before OpenXR is initialized, including the ability to do so in the OpenXR package would be out of Unity's scope? I'm thinking that's not quite what you mean, since you linked your library below that does exactly that.

Looks like it will help with our problem, nice work

Runtime selection and querying would definitely be valuable, since it seems like from the user end switching the active runtime isn't necessarily straightforward.

From a practical point of view for our use case I'm just attempting to replicate how the legacy 2019.4 VR stuff worked, where it would attempt to initialize Oculus if it is available, then fallback to OpenVR.

Ahh duh, of course.

This has been a problem for us in both OpenXR and legacy VR. Planning to look into a workaround for this, but would be good to have an official fix. Can be demonstrated in the ControllerSample by switching from Oculus to SteamVR runtimes.

 

Hi!
At first I had:
Unity 2020.3.3
HDRP 10.4.0
XR plugin 4.0.5
OpenXR 1.1.1
SteamVR 1.16.10
SRanipal 1.3.2.0
TobiiXR 2.0.0.174

It used to work just fine and without anything really changing my Vive Pro Eye suddenly did not show the Unity scene anymore. Just the default SteamVR black surrounding with the concentric circles. The headset seems to work fine and every once in a while it does work!
Checked Windows (10) for updates. Checked my drivers (see above). Rebooted. Nothing seems to help. Frustrating as it always worked. The only thing I change in my code in the project was some math for some number transformation. Nothing to do with XR or eye tracking.

So I decided to upgrade:
Unity 2020.3.7
HDRP 10.40
XR plugin 4.0.5
OpenXR 1.1.1
SteamVR 1.16.10
SRanipal 1.3.2.0
TobiiXR 2.1.1.177

Now throws an error on the SRanipal that it cannot find the device Initial Eye. And no image in the headset after that.

Any ideas what to try to get my headset working again??

Marco

 

I tried to use the OpenXR plugin today (Unity 2020.3.6f1) with the XR Interaction toolkit preview package (latest) and if I use the Gameobject>XR>Convert camera to XR Rig, I seem to get a working rig. If I use the interaction toolkit menu options and select Room-scale XR Rig (Action-based) the tracking fails (no console errors). If I try the Room-scale XR rig (device based) the tracking works fine.

The issue seems to be the action-based tracked pose driver, as its the only thing that really changes on the camera between the 3 rigs. The two that work use the normal tracked pose driver.

First gen HTC Vive
SteamVR 1.16.10

 

I have set up the controller input actions based on the interaction toolkit sample and my interactions are working just fine. But I had to replace the action based Tracked Pose Driver with the device based one to get tracking of the head to work. I checked the XR interaction debugger and it is picking up position and rotation changes for the centerEye device (under Head Tracking - OpenXR) but image in headset remains locked to the initial frame.

 

I'm having an issue with my Vive Pro Eye in a Unity 2020.3.3 project.
The project uses HDRP (10.4.0), XR Plugin (4.0.5 with OpenXR selected, Single Pass Instance, OpenXR runtime to either SystemDefault or SteamVR and the HTC Vive Controller profile selected even though I do not use the controllers in the app), OpenXR 1.0.3. Also running the 1.3.3.0 SRanipal eye tracking driver in the background.
The project uses the SRanipal Eye Framework prefab to initialize the eye tracking and the TobiiXR Initializer to initialize the Tobii system.
Running on Windows 10 with SteamVR 1.16.10.

Often when starting the application (in the Editor) the view in the headset remains the default view (the black space with circles and the two lighthouses visible). It runs fine on the monitor.
Ever so often the view does work and everything works fine.
Using UnityEngine.XR.OpenXR.OpenXRRuntime.name reports steamvr. So the link to SteamVR is there.
Both the Tobii and the SRanipal plugins report working in the Console.

Just the image isn't rendered and the problem is intermittent, but more often than not.

I have my own camera in the scene (simple setup), but I also tried the XR->XRRig without changing anything. Same results.
I've tried uninstalling all Vive, Steam and SRanipal software and reinstalling it (rebooting). Same results.
I've tried upgrading Unity to 2020.3.7 and also downgrading the OpenXR and XR Plugins to a few versions back. Same results.

The only thing that seems to work is to disconnect my Vive (pressing the blue button on the break-out box) and reconnecting it. Then the image is rendered. However, then my sound is gone!

Anyone any ideas?

Marco

 

Yes, I make sure the sensor is covered so the display in the Vive is actually active before starting the scene in the Unity Editor.

I seem to have found a work-around that works for now (and for me). It has to do with the SRanipal driver and service for the Vive Pro Eye eye tracking. Might be a bug in the latest 1.3.3.0 version. This is what I do:
- Whilst Unity (2020.3.3) is open with my project loaded
- Open the Windows Services window (use the search box)
- Find the SRanipalService, right-click and Stop it
- Press CTRL-ALT-DEL and open the Task Manager
- Find the Vive_Super_Reality_SR_Runtime and End this Task
- Now restart the SRanipal program (using Windows search bar or in my case double-click the icon on my desktop)
- Now go back to the Services window and right-click the SRanipalService and select Start

After that it all seems to work for me and kept working for several Play sessions at least. Weird, but as long as it works I'm not complaining!

 

I encounter the same issue I think. How did you manage to fix it ?

 

What is legal, for example?

 

Any idea whats happening with finger-tracking on the index? That's basically the last thing OpenXR needs before it can become the defecto standard for all devices.