Official XR Plugins and Subsystems

I installed Unity 2019.2.0b6 (under Windows), but see no "XR Management" package inside the Package Manager. Nor do I see the new "XR" category under Project Settings. I do see that there is a "Built-in package" titled "XR", but this does not seem related to the "XR Management" tool cited above. Do I need a different (alpha?) build of 2019.2 for this? I tried 2019.3.0a5 as well. No sign of the XR Management package.

 

same question, where to start when trying to build a VR project. there is no lightweight VR template nor is the documentation leading anywhere, see question concerning the XR Management

 

Does the normal Oculus (Android) package support native virtual reality for the Quest?' Or will the support for the Quest with native VR only be available through this workflow?

 

Was able to get the package installed and the loader downloaded/selected, and the tracked pose driver set up, but when i attempt to play I get 'Unable to start XR SDK Oculus" and some failed messages. Also tried doing a build and the app just crashes.

Using 2019.3.0a6 in a new project.
Oculus@0.8.4-preview


Is there some setup I'm missing?

 

I don't even have it installed on my desktop. Working on deploying to the GO.

 

So asking about the desktop prompted me to check my XR plugin management settings for desktop, i had the Oculus Loader in there and in the android. i removed the desktop one, and the errors dont show up anymore, but deploying to the GO the app still crashes before anything shows. click app -> black screen -> app to app selection

 

Sanity checked myself, brand new project, install xr package manager, download oculus loader, add tracked pose driver, build, install. app started, head is tracking, but there was no splash logos.

 

should we get both ARCore and Google Cardboard VR support for 6dof on mobile devices?

 

How will hand gestures be handled for the different platforms be handled by the new InputSystem?

 

Is it possible to create our own XRSubsystem for e.g. custom hardware prototyping?

Edit: I've done some research and it doesn't yet seem to be fully possible. I've taken a look at the WMR implementation because that's the platform I'm most familiar with, and some of the things (e.g. XRDisplaySubsystem) seem to be implemented in native code with no documented public interface.

Now the question is, what's the roadmap for this? Are you planning to expose this to developers so we can create e.g. our own display subsystem to take advantage of the stereo rendering stack and other Unity XR features?

 

I created an empty project of 2019.2.0b7 on Mac OS. Installed XR Management. Downloaded Oculus Loader and it is showing an error :"Legacy XR is currently disabled. Unity has detected that you have one or more XR SDK Provider packages installed. Legacy XR is incompatible with XR SDK. Remove all XR SDK Packages from your project to re-enable legacy XR".

"Virtual Reality Supported" checkbox under Player->XR Settings has been disabled due to the same error...

 

Just to get this right: this package doesn't support Steam VR yet?

 

External developers are currently still not able to create their own plugins for custom hardware that would plug into Unity's XR system, right?

Related to @holo-krzysztof 's question.

 

Sure, hopefully this feedback is of use and any suggestions would be welcomed - difference in inputs between controllers with/without touch pad - like the Windows mixed reality controllers have touch pad and analog sticks whereas the vive controllers have touchpads only which lead to issues with our teleportation/movement mechanisms as WMR controls usually rely on you snapping the analog stick forward to see the teleportation arc then you let go of the analog stick so it snaps back and you teleport.

With WMR and Quest analog sticks, they are very sensitive to input, VRTK v4 teleportation by default has a rotational ability where once you have held the stick forward, you can rotate the way to face once teleported before letting the analog stick snap back to default position by letting go of it. The issue with the Quest is the analog stick snaps back and slightly moves over to the opposite side so you often end up facing 180 degrees off your intended direction(!). Further to this, the WMR analog sticks are just as sensitive and prone to this also. We are thinking of just removing VRTK v4 and writing something custom or adding a deadzone to all analog stick input vectors.

Sometimes the tracked pose driver for left and right controllers just picks up the left and right controller by default when left as a 'Generic XR' device with the Vive, on some other headsets like the Quest or WMR Lenovo Explorer, it often assigns both devices to be the left controller, or none at all so nothing works. The workaround for this seems to be to set both left and right trackables to be the Left and right hand control devices respectively.

When we used to start unity projects, a 'VR LWRP' preset existed with a nice little VR setup, in 2019 that seems to be gone - will this be replaced by some sort of VR template? Unreal Engine has an easy VR setup with some very basic preset teleportation and analog stick free move defaults which would be very handy to have for quick set up of VR projects. Whereas any time we make a new project we start from scratch, have to use something like VRTK or other community made solutions that could have support or documentation dropped/unfinished (like VRTK v4)

 

Moved this to a new thread here, if you did have time to respond that would be greatly appreciated
https://forum.unity.com/threads/xr-input-system-for-vr-with-native-vrtk-v4-gripes.719483/

 

Being unable to test AR projects in the editor by using a web cam(Vuforia supports this) or the camera from the phone, i emphasize, directly in the editor, is a deal breaker for me in using AR Foundation.

Will this be addressed? building to a device every time i need to check something is not practical.

 

Interested in seeing OpenVR support!

 

Edit: Logged this as Case 1173593

Getting 4 errors about 'The type or namespace name 'XRSessionSubsystem' could not be found (are you missing a using directive or an assembly reference?)' when importing Oculus Loader in 2019.3.0.a10 - submitting a but report for it now but is there a fix?

 

Is there any word as to when the Rift S issues will be resolved? Presently, it's our headset of of choice enterprise production

 

So under this new package-based approach, how do we do something like enable fixed foveated rendering on Oculus Quest now?

 

I can not find XR Button in eidt->project settings, after installed XR management, can anyone help?

 

I'm new to VR and wanted to try out development with this new system. I have a Oculus CV1 w/ touch.

I start a brand new LWRP 2019.2.1 project. I download the XR Management package (2.0.0-preview26), and upgrade the XR Legacy Input Handlers to 2.0.6. I go into the ProjectSettings for XR, download the Oculus loader, add the Oculus plugin. Add a pose tracker to the main camera in the sample scene. Set it to be center eye. Hit play.
Get a bunch of errors about IsMatrixValid, MinMaxAABB errors in my log. I only see out of my left eye.
I change to single pass, and I can see stereo now, but everything is upside down and I still receive those errors.
I remove the post process script from the camera. Everything is right-side up, but obviously the shadows are messed up.

I realize I'm being verbose, but these are the hurdles that you're expecting your users to jump through to just get a basic camera attached to the HMD right now. I haven't even started with hand presence. How are you expecting users to interact with this system for the first time to get started? What happened to the VR template? How do I get rid of the assertions and errors? I don't mind some problems doing something more obscure, but this is basic first user setup and I've already hit some pretty obvious roadblocks. Please document your first setup and make sure it works without errors/problems.

 

Same case for me on Windows. Just followed the instructions and had the same error. It's crazy...

 

Absolutely agree... I just started a project trying to build for Oculus Go, followed the guidelines and didn't manage to build so far. As basic as a Camera and a Cube in scene... It's insane. Did someone in Unity tested this before testing?

 

Hello
So I'm just trying to build a simple cardboard app for Android (sphere & solid coloured camera) with this new system. To no avail.
I get these errors repeating in the logcat
E/GvrShimUnity: getControllerConnectionStatus device 0 api status:
E/GvrShimUnity: getControllerConnectionStatus device 1 api status:
App hangs at Unity splash screen

Switch to Android build
I installed XR Management package
Downloaded the Loader for Google VR Cardboard
Selected it from Available
Hi create new to create Google VR Settings (do I need to do this)
Added Tracked Pose Driver to the main Camera

Am I missing something?

 

This does not work for Google Cardboard.

 

I am having problem creating IL2CPP APK build with ARCoreFoundation in it, MONO works fine but ILCPP gives an error

I have attached screenshots.
Please let me know if anyone has found the solution.

 

I have one question here.
What is Unity plan for OpenXR integration? Is Unity planning to integrate OpenXR runtime parallel with UnityXR? So C# XR Subsystems could use OpenXR instead of UnityXR to load device plugin?
This would help future device providers to do only one implementation and support all graphic engines which has OpenXR integration.
So for me as a new device provider, I would prefer to implement OpenXR from the begin.

Thank you for an answer.

 

I'm also interested by OpenXR integration. It's already available in UE4 since 4.22 and works pretty well.
What are the limitation to integrate it into Unity?

 

This issue does not happen on the latest 2019.3 beta, please upgrade to it (I wasted time trying to see if this issue happened on 2019.3 beta as well so you owe me)

 

Actually the problem was in preview packages if you use stable packages then the issue won't happen. (So I don't owe you ;-) )

 

Can somebody help me to understand how cross platform development works with this new approach?
So let's say I want to write an App that works with an Oculus Rift as well as for Windows Mixed Reality.

Which packages can I use in this case?
Once I use the "Oculus XR Plugin" ... then I'm stuck with Oculus?
So what packages are cross platform? And what is the best way to set this up for cross platform?

 

> Once I use the "Oculus XR Plugin" ... then I'm stuck with Oculus?

Oculus AND OpenVR are both cross-platform across PC VR (with a few caveats).

However Oculus also works on the Quest (and the Go if you care about that) whilst OpenVR doesn't

 

I too would be interested to know how to make sure that separate plugins are only built out per platform where needed

 

Ok thanks. So when I use the new Oculus XR Plugin, I will also be able to run it on Windows MR?
Currently I'm using only the build in UnityEngine.XR stuff, and that works also for quest. But did not do any extensive tests so far. Just basics.

I think it would be great to have an overview, about what plugin is compatible with what headset and also some example about how to setup a pure cross-platform project, even if it is missing some functionality.

 

@matthewr_unity I have messaged you about this directly also but it may be useful to respond back here to help others - I can see that you also mention here the Oculus Integration package is not fully supported with this XR Subsystem workflow, the issue there being that we can only set the Fixed Foveated Rendering level through the Oculus Integration package through the OVRPlugin. If we could have some documentation or advice on how to set it through the XR Subsystem Oculus Loader or any other native XR platform features through this integration, it would save us having to import those heavy example SDK packs like Oculus Integration.

Please let us know if or how we can do this?

@Matt_D_work

 

Can you give more details on that? Right now I can use the native unity xr support and I can build to OpenVR and run the application on steam.
This will not be possible anymore with the new approach?
Will there be a "native unity xr plugin" in the future?

Or can you give an example, about how to setup a project that uses the new cross platform stuff shown in this oculus talk:

How do I setup a project, that uses this new XR Interaction Package and that runs on Windows MR, Oculus Rift, Oculus Quest and any other possible platform?
Will this be possible?

 

Hi Matt, do you have any information on my question above Skeketor23's question? What we are asking about isn't documented at all and we are looking to activate Fixed Foveated Rendering on the Oculus Quest/Go without using the Oculus Integration off the asset store, as is recommended in this thread where it is stated that Oculus Integration doesn't work with the Oculus Loader.

You response would be really appreciated

 

@Matt_D_work Any any when the interactors/interactables stuff shown here

is going to be available? We're currently stuck trying to decide whether to reimplement some OpenVR stuff on the Oculus SDK and a peek at this would be really helpful in knowing whether to hold off for now.