Unity 2020.1 release - AR/VR updates

Unity 2020.1 is now available; more information on this release can be found in our blog post. Starting with Unity 2020.1, XR Plug-in Management in Project Settings is the only way to enable AR/VR in your project.

Unity 2019 LTS remains the recommended version for projects in production. For those who are interested in upgrading their projects to Unity 2020.1, refer to our upgrade guide (including an FAQ) to help assist you.

1 Like

That’s a nice, clear, doc - thanks.

There are some typos and bits where I think more info would be helpful - but your doc is configured to block all copying of text :frowning: :frowning: :frowning: so I can’t tell you which bits. I’ve never blocked copy/paste on a google doc before, but I’d recommend removing that if possible - it’s not cool having to take screenshots and email them to colleagues instead of just copy/paste.

Hi, we still need OculusIntegration to work with OculusQuest HandTracking, am I right?
How can we install it in Unity 2020.x, if there there is no AssetStore window, and PackegeManager doesn’t list it? Moreover, OculusIntegration worked by enabling Oculus support via ProjectSettings/Player/XR section… that in Unity 2020.x is not supported. How can we handle that?
Thank you

Try reloading the doc, you should be able to copy text now. Feel free to DM me where you think there are typos and sections that could use more information.

1 Like

That is correct, you still need the Oculus Integration package to enable hand tracking on the Oculus Quest. Hand tracking is not yet supported in Unity’s XR Interaction Toolkit. Here are the steps you’ll need to take:

  • Install the Oculus Integration package from the Asset Store. Download the package in your project by going to Window > Package Manager and select My Assets.
  • Select Oculus under the Android tab in Project Settings > XR Plug-in Management. Note that you’ll need to have the Android build module installed for the Android tab to appear.
  • Refer to Oculus documentation on how to set up hand tracking, add hands to scene, and configure OVRHandPrefab.

Enabling Oculus support via Project Settings > Player > XR is no longer a supported path in 2020.1 and later. Instead, you’ll need to select Oculus in Project Settings > XR Plug-in Management. Once selected, Unity will install the Oculus XR Plug-in for you, which has replaced the deprecated built-in Oculus packages (Oculus Android & Oculus Desktop).

2 Likes

““Single pass” is no longer supported in 2020.1 as “single pass instanced” is most performant???”

Just great. Half the assets I bought from the asset store don’t work with single pass instanced :frowning:

How would I get the Oculus Spatializer working with XR Management? Do I still need to include the Oculus Integration package?

More info here - Oculus and Microsoft Spatializer missing and manual states the opposite

Are there any guides for upgrading from Multipass/Single Pass to Single Pass instanced? Need to do it for a bunch of my shaders.

1 Like

Since 2020.1, I keep getting warnings that “Virtual Reality Support is enabled…landscape left will be used.blah blah” and it should be disabled, see attached screenshot. I searched everywhere for the tick box for this with no luck. Anyone know where this is?

d9c19c30319d87adaa19f25f30a7063f371df440.jpeg

Once you click “Ok”, built-in VR will automatically be disabled. Are you still getting the notification after you click “Ok”?

Have a look at this page which describes the shader macros we use to support Single-Pass Instancing (which also take care of all the other modes as well). (and please ignore the out-of-date goop at the top of the page :hushed:)

5 Likes

I’ve seen the popup a few times, but not tracked when it appears, my focus was on trying to turn VR off. I will try and figure out when it appears. I’m using MRTK and I think it does something re VR settings when it first runs, but then the option no longer appear subsequently.

There is permanent warning in Project Settings → Player. See attached.

6149719--671716--AndroidVRWarning.jpg

Yes, you still need to include the Oculus Integration package (make sure you’re using the latest version). See the previous comment I made on how to install the package.

1 Like

I’ve had that too. Unity was disableing the obsolete built-in VR, and SteamVR Unity intergation was enabling it back automatically, creating an annoying loop.

Hope it helps.

I have the message popup on every play press, so indeed very annoying. Think must by MRTK, but it removes config of options after first application, so not worked out, how to change it.

It may be wise to wait for all the asset you use to support 2020.1 before switching Unity version.

When will hand tracking be available in XR interaction Toolkit? No updates to fuctionality since April! Is this feature on the horizon or have Unity lost interest? not a dig just genuine concern. Legacy interactions are being deprecated left right and centre.

3 Likes

I upgraded my project from version 2019.4.5 to version 2020.1.3 and now i cant see Oculus rift mirror to pc screen, i can see the scene only in Oculus rift visor.
Before upgrade all works ok, my scene were visible in Oculus visor and on pc monitor.

All these years of complaining about not being able to install packages that are already downloaded without needing to be online to do so and now they finally say “You can no longer even ACCESS the Asset Store now. From now on, just use the package manager instead of the Asset Store”

… and then they complete the sentence with “but just be sure you are online if you want to browse which assets are on your hard drive.”

…and add to that “Also, we only fetch your content in batches so be prepared for lots of clicks to just see your local content. Also, if you change tabs from your content to installed content and back to your content, be advised that we need to fetch all that info about your local content from online again, starting with only the first 25 assets”

What an improvement.

1 Like

Unity has me confused on how you want the VR system to work - but I think it’s mostly a documentation and examples issue, rather than fundamental problems. I’m using 2020.1.6f1 at this moment while writing this. The instructions Unity - Manual: Getting started with VR development in Unity imply that we need to separately download the plugins for Oculus, OpenVR, etc - I’d hope that the XR plugin would either download the most common ones for us, or would tell us within Unity that we should download them. XR Plug-in Management is in Project Settings; use the checkboxes in that menu to trigger the downloads for those individual plugins and manage any version issues. And the “OpenVR Loader” label is confusing - is that for OpenVR overall, or is the loader only one specific component and thus I need to add more?

Next, in probably the most critical step in the documentation (Unity - Manual: Configuring your Unity Project for XR), “From Unity’s main menu, go to GameObject > XR > Add XR Rig” - that option doesn’t exist. There is a “Convert main camera to XR Rig” option, but no “Add XR Rig” option. I’m using the HDRP pipeline, and I’ve tried this with both the default sample scene and a brand new one, and there is no “Add XR Rig” option, just the convert option.

This creates the problem that the camera conversion doesn’t add any additional trackers like hand controllers or tracking pucks. Maybe the “Add XR Rig” functionality would create a prefab that includes those trackers, maybe not, I can’t tell. And I don’t see any such prefab anywhere in the project files. So, in order to add the hand trackers, I had to take guesses - it seems that adding extra TrackedPoseDrivers may be the correct option. It would be great if there was a way to get the button input from these controllers (that documentation seems to be under Legacy Input Helpers, and “Legacy” generally means it’s not the current suggested method, so I have no ideas on that one), or to have prefabs with models for the most common controllers. A real, proper sample scene, or implementation of that “Add XR Rig” option and clearer documentation, would go a long way.

By the way, the functionality in the “Convert main camera to XR Rig” tool should update the Clipping Plane of the camera. The default minimum of 0.3 meters is far too high; it will hide your own hand controller from you. It should be set to 0.05 meters or less, preferably less. Further, the documentation references Preview packages, but it seems that the process to show those has disappeared - someone changed the workflow to display preview packages, and the control is now a checkbox in Project Settings → Package Manager. In my opinion, the workflow described in the documentation is superior.

I hope this isn’t too much of a rant, but these are issues that I encountered over the last two days when trying to set up a new VR project. I got the basics working, but it is a puzzle with jumbled pieces.

3 Likes