Official Unity support for OpenXR in preview

1.16.8 beta does fix the previous problem with the thumbstick not being recognised, but unfortunately it seems to introduce this new problem where the face buttons and trigger buttons don't get recognised by themselves, but do fire when the thumbstick is clicked.

I gather this is an issue with SteamVR's OpenXR runtime though, and so there isn't much Unity can do about it, is that correct?

 

We can simply check it with XR Interaction Debugger as i did on gif in this post.
Trigger, primary, secondary and menu buttons are not working now.
The stick button activates several other buttons at once.
Grip and stick directions works fine.

Also, android quest build without OpenXR using same input and work a little better.
The stick no longer activates several buttons, but the trigger still does not work.

Is it possible that the mapping profile is not correct?

 

[QUOTE="the_real_apoxol, post: 6899660, member: 6421624]I dont believe there are any known issues with Android / Quest builds involving input not working.[/QUOTE]

Yes indeed. Everything worked on android, my mistake. Sorry.
Now I understand why the error can be on the side of the Valves and not working correctly through Steam VR.

At the moment, those who are developing can use the Oculus plugin + link + XR input. It works well and the all buttons are work.
It also works through VD, we can create a bat file to run a Unity project using Oculus.

Code (CSharp):

1. "C:\Program Files\Virtual Desktop Streamer\VirtualDesktop.Streamer.exe" "U:\UNITY SOFT\Unity Editors\2020.2.1f1\Editor\Unity.exe" -projectpath U:\UNITYPROJECTS\yourprojectfolder -useHub -hubIPC -cloudEnvironment production

@the_real_apoxol thank you for writing to Valve. Now we will wait for them.

 

This is only things that holds me back from upgrading to 2020.2. Good to know that Valve is looking at this issue and will continue to keep a close eye on this.

 

Unfortunately I set up the ActionBasedController and the Vive Menu button and touchpad are still not interactive. This is definitely an issue with the HTC Vive Controller Profile v 0.0.1 in XR Plug-in Management > OpenXR

Tested on:
-Unity 2020.2.7f1
-XR Plugin Management 4.0.1
-OpenXR Plugin 1.0.2
-SteamVR 1.16.8

 

Have you checked the XR itneraction Toolkit's XR Input Debugger?

it seems that there are some other issues with Vive input, that should hopefully be fixed soon.

 

Same here. No matter what I do I can't get the menu button going - it doesn't show up in the XR Interaction Debugger or the Input Debugger, either. Looks like it's not coming through at all

 

When can we expect to see support for PrimaX and other alternative headsets ?

 

It's up to the headset manufacturer to support the OpenXR platform, not the other way around.

 

The hotfix (beta 1.16.9) fixes this for me (Oculus Quest 1, Windows) - thanks!

 

It's out of Unity's hands, Khronos group have not added that to OpenXR yet, you can verify this by checking the current docs here
https://www.khronos.org/registry/OpenXR/specs/1.0/html/xrspec.html#XrObjectType

I will try to contact the team to ask about this as they have their own forums

 

This alludes (to me at least) that the group are doing something about this already- the best I could find was this forum post on their forums, have you had any update on this internally?

https://community.khronos.org/t/support-for-multiple-trackers-with-openxr/106012

 

I can confirm the Quest 2 using Virtual Desktop and SteamVR now works with the controllers and OpenXR...including all of the touch events.

It is awesome.

@the_real_apoxol Did you guys have something to do with this or did Steam just fix it?

 

Hi, i get this warning with OpenXr Plugin 1.0.2
"Could not create a device for 'HP HP Reverb G2 Controller (OpenXR) (XRInputV1)' (exception: System.InvalidOperationException: Cannot find parent 'devicepose' of control 'devicepose/istracked' in layout 'XRInputV1::HP::HPReverbG2ControllerOpenXR'

With the version before i have no problems.

 

Hi, I´m using mixed reality plugin (0.1.4). When i activate g2 in feature sets i get this warning. With 0.1.2 preview there is no warning.
But beside that I have another problem too. I also don't get any position data via Xr Controller (action-based) input. Everything works with the old input system. I wonder if the G2 controllers are not working with the new input systme. I'm probably just missing something.

 

We recently got the bug report on G2 controllers and the error info indicate the pose is not correctly hooked up. We also suspect the bug might leads to pose invalid. We are internally investigating, will ping back when we have more info.

 

Hi all!

I really need help with this..

On my HTC Vive Pro, I'm occasionally getting nothing but a black screen and the console is getting spammed with:

[XR] [OpenXR Input]: [xrLocateSpace] Failed to locate view space relative to app space at time <121124088423011> [ErrorCode: XR_ERROR_TIME_INVALID]

But it doesn't happen all the time - seemingly random and not very frequent. More frequently, I have a tester running a HTC Vive Cosmos and they're getting that same error every time.

As well as spamming the console with 'failed to locate view space..' when OpenXR initializes, it's dumping out this:


[XR] [17392] [18:17:48.052][Info ] OpenXRSession::HandleSessionStateChangedEvent: state XR_SESSION_STATE_UNKNOWN->XR_SESSION_STATE_IDLE session=2657295863264 time=123134288969800
[XR] [17392] [18:17:48.052][Info ] OpenXRSession::HandleSessionStateChangedEvent: state XR_SESSION_STATE_IDLE->XR_SESSION_STATE_READY session=2657295863264 time=123134288984000
[MODES] ModeService[default].RefreshMenus
[MODES] ModeService[default].UpdateModeMenus
[XR] [12468] [18:17:48.557][Error ] XrResult failure [XR_ERROR_TIME_INVALID]
Origin: xrLocateSpace
Source: C:\build\output\unity\xr.sdk.openxr\NativePlugin\Source\unity_input.cpp:2177
Error on graphics thread: 1


Anybody got any suggestions? I've tried a whole bunch of random stuff like moving things around/changing my controller init code .. but I'm getting nowhere with it

Thanks!

 

Hey! I'm running Unity 2020.2.7 with XR Plugin 4.0.1 and OpenXR plugin 1.0.2

 

Oh sorry .. that was silly of me! SteamVR 1.16.8

 

Thanks! I really appreciate it

 

Hi, I am calling TryGetBoundaryPoints and it returns true, but the list is empty. this is for the OpenVR plugin.

thanks

 

We switched to OpenXR Plugin 1.0.2 from OpenVR XR (Valve). With the Plugin from Valve we had the option to select the target eye for the Desktop Mirror (Left/Right/None). Where "None" resultet in Black Desktop Window (No Mirror).

How can I disable the Mirroring with OpenXR Plugin ?

 

Thanks this is what I was looking for.

Btw, the Headset seems to disconnect from displaying anything but SteamHome App when you take the Game binary out of focus for a while and then get it back to foreground, does not reconnect anymore, until you restart the Game. Same in the Editor.

 

We're trying to build on Hololens 2 using this setup.
After building the VS project from Unity, we can build the project from VS 2019 but the application gets stuck at startup with 4 spheres moving, before the Unity logo is shown. VS shows an error when starting the app on the device: DEP6701: Bootstrapping failed with unexpected error: ArgumentNullException - Value cannot be null. Error Parameter name: projectUniqueName [0x80004003]
The scene is a blank scene with just a camera and a cube. Not using MRTK, only the setup linked, the Unity OpenXR plugin and the Unity XR Interaction Toolkit.
Tried several different build configurations, but none of them works.
Anyone got the same issue and/or have any clue on what's happening?
Thanks!

 

Are there plans to add compositor layer features to the OpenXR plugin? There were ways to do this with the Oculus SDK (OVROverlay) and SteamVR. This is useful for lots of things but loading screens is a big one as it is smooth, not impacted by any stutters during load, offers better readability for text, etc. If there is a way to do it now I'm not aware of I'd love to know, I'm trying to go all in with XR. Based on the XR specs it looks like this capability is there in the draft specs?

 

Thanks!

 

For those who is using HP Reverb G2 controller, today we released a new version (0.1.5) of Mixed Reality plugin that fixed issues when using G2 controller. Please upgrade and let us know if this addressed the issue you've seen.

 

Hi, Thank You. I have tested the version with Unity 2020.3 and have not found any errors so far. What I am missing now is a possibility to use a model of the controller as is easily possible with the steamvr plugin. There has to be a model of the controller installed in the system, but how can I use it with Unity and Openxr?

 

I confirm. Thanks. Duplicate : https://forum.unity.com/threads/hp-reverb-g2-controller-openxr.1067711/

 

@UnityGuys
Is there already a bug tracked for that? We could not find it.

 

The SteamVR 1.16 Hotfix remedied my OpenXR Oculus input problems, but the 1.17 beta update broke all inputs. I reverted back to 1.16 and it's back to working order again. Just a heads up for people working with Oculus!

 

Are you aware if the Issue that with OpenXR when you Focus another Programm, after a few sec, the Headset will show a Steam Home Popup containing the Project name and Waiting.... when you click back into the game (focus), this popup will stay forever, not "reconnecting" to the game

This happens in binary and editor.

Unity 2020.3.0f1
SteamVr 1.17.1
OpenXR 1.0.3
URP Project

Edit: Managed to fix it.

 

I can't seem to repro this - are you able to share Editor logs and a SteamVR system report:

 

We've put a fix for the menu in the latest beta 1.17:
https://steamcommunity.com/games/250820/announcements/detail/3032584660736824619

Let me know if this works for you

 

We've had a Shadow Drop of 1.0.3 of the OpenXR plugin...

But the changelog is still at 1.0.2?

 

Can you provide an update on the controller pivot offsets. Are they going to be fixed to not require manual adjustments by users?

As an asset publisher I need to know if I should adding this to my interaction framework like I did for OpenVR adjustments.

Thanks.

Edit: Also any updated timeline on Index finger tracking?