Official XR Interaction Toolkit Preview Release (0.9)

That sucks, the default for the Oculus Quest (or any 6dof headset) should be RoomScale. Things like these are the reason why I gave up on the "native" Unity XR support and downloaded the Oculus package a while ago.

 

I think the confusion comes from the fact that the toolkit is currently using the legacy VR input package (which does support OpenVR but somewhere above it was stated that this is only temporary and it will move to the new system (for which no ETA for OpenVR has been announced - or even if there is definitely going to be support)

 

Yes that is the standalone OpenVR package that you can still import if you edit the package manifest, see notes about it here https://docs.unity3d.com/Packages/com.unity.xr.openvr.standalone@2.0/manual/index.html

"NOTE: Support for built-in VR integrations will be removed in Unity 2020.1."

 

Yea I guess if you are running the alpha of 2020.1, you're in trouble. I agree that the lack of messaging on the future of OpenVR is pretty lame and hopefully they'll get it together by the time 2020.1 hits beta (lol).

But if you open the sample package with the current release (2019.3), it just works fine without any modifications on OpenVR hardware.

 

Has somebody figured out to delete placed AR-Objects yet?

 

@jackpr Since the menu can be opened and closed repeatedly during the experience I think I'll just continue to have all the interactable GOs under root, with the menu enabling or disabling (rather than triggering destruction and instantiation) Looking forward to updates as your team figures them out.

 

Is there a way to use XRI with the Oculus cross-platform local avatar hands? any examples?

 

@StayTalm_Unity FYI: https://github.com/Unity-Technologies/com.unity.xr.interaction.toolkit is still in the docs, but is private.

 

I guess the reason people think that OpenVR support is lacking is because neither Valve, nor SteamVR, nor HTC is on the list of "officially supported platforms": https://docs.unity3d.com/2019.3/Documentation/Manual/XR.html

Can someone from Unity Technologies please let us know why Valve/SteamVR/OpenVR is missing from that list?

From the outside, that list certainly looks like something going on with politics. Because from a technological / developer perspective, it does not make any sense at all to ignore Valve when it comes to VR.

The Steam/SteamVR ecosystem is huge, and does a lot of things really well. It's also the only one that at least tries to work on Linux and Mac. Also, the Valve Index controllers are currently the most advanced VR controllers ("next-gen" compared to Touch).

SteamVR Input 2.0 has solved not only controller input / action binding in a really good way, but with its skeletal input system also has a really good solution for finger-tracking (as supported by Valve Index controllers, and to a much lesser degree Oculus Touch - but the system also handles all other controllers really well, like the 2016 Vive wands). Valve's skeletal input system should even work really well with Oculus Quest hand tracking, once those things are wired properly.

Honestly, without fully supporting SteamVR/OpenVR, Unity's XR Interaction Toolkit is not "cross-platform" at all ... and Unity is several years behind, technologically (the first version of the SteamVR Interaction system is from 2015 or 2016 and, from the looks of it, had everything Unity's system has, if not more ... like ... proper controller abstractions with the correct controller models loaded during runtime; meanwhile Valve is at 2.5 or their system and it evolved a lot since back then).

Don't get me wrong: I'd love to use a native Unity system and would actually much prefer using such a native system over a third party system. But not if the native system lacks support for the largest and most technologically advanced platform. This does upset me a little because I feel pushed back in time, to 2015, when Unity introduced it's "native VR" support (which also was way behind the SteamVR Unity Plugin at that time, in so many ways and it took several years to catch up).

 

Tonight was my first night to play with this, so I picked up all the latest stuff - Unity 2019.3.0f5, the latest preview packages, the latest XR Interaction Toolkit off of github. A quick preview in my Rift and saw everything working. I then naively set it to an Android build and stuffed it on to my Quest, just to see what would happen. I was pleasantly surprised to find that it worked!

I'm very curious to know why MagicLeap is supported, but not SteamVR. While I prefer Oculus devices (today), I can't disenfranchise all those HTC users. I suspect it's in the "Coming Soon" category, but I'd like to hear that officially.

What I couldn't figure out is why I couldn't open the scene. I see a folder icon where I'd expect to see the normal Unity logo for a scene.

 

Does the oculus local avatar hands integrate with the XRI toolkit? if so, i'd like advise how to get that working. Tia.

 

I just downloaded Unity 2020.1.0a19 and it doesnt even have Player Settings > XR Settings panel at all! So unless they're dropping support OpenVR in Unity 2020.1 altogether (haha!), it's being worked on.

 

Not with XR alone, no, I don't expect so. You still have to have Oculus Integration. The OC6 video from September shows the ecosystem pretty well -- tho the 2nd presenter has WAY too much energy.

 

yes i get that. I've created a new project with both installed and trying to figure out how to use the XRI XR Rig with oculus hands.

 

Is this expected behavior? @jackpr @mfuad @Matt_D_work @StayTalm_Unity

If there isn't a mesh for the XR raycast to hit (somewhere in the scene behind the UI canvas) the Valid Color Line Visual won't trigger, regardless of if you're hitting the UI element on the canvas. You can still interact with the UI, but the line visual won't change to indicate that you're able to.

This can be seen in the included demo (UI CANVAS) by disabling the 'LowPolyIsland' gameObject. The 'sphere' ground mesh is what allows the Valid line to show in this case.

This doesn't feel like expected behavior since assuming there will always be a mesh behind UI seems like a big assumption for features to work. Shouldn't the UI itself trigger whether the interaction is valid?

 

If you'd like to fix it locally in your package code, it's in XRRayInteractor.cs: Line 319
Change

Code (CSharp):

1. if (raycastPointIndex < positionInLine || ((raycastPointIndex == rayIndex) && (raycastHit.distance <= distance)))

To

Code (CSharp):

1. if (raycastPointIndex < rayIndex || ((raycastPointIndex == rayIndex) && (result.distance <= distance)))

 

I am trying to place a AR cube programmatically at (0,1,0) with C# using the XR Interaction Toolkit. There is an example AR file "PlaceOnPlane.cs" included in the example github ( https://github.com/Unity-Technologies/XR-Interaction-Toolkit-Examples ) repository but it does not seem to work? It is not attached to any of the example's Game Objects? Also, the PlacementInteractive seems to completely override the Place On Plane script when it I attach it to a Game Object?

Code (CSharp):

1. using System.Collections.Generic;
2. using UnityEngine;
3. using UnityEngine.XR.ARFoundation;
4. using UnityEngine.XR.ARSubsystems;
5. //using UnityEngine.InputSystem;
6.  
7. /// <summary>
8. /// Listens for touch events and performs an AR raycast from the screen touch point.
9. /// AR raycasts will only hit detected trackables like feature points and planes.
10. ///
11. /// If a raycast hits a trackable, the <see cref="placedPrefab"/> is instantiated
12. /// and moved to the hit position.
13. /// </summary>
14. [RequireComponent(typeof(ARRaycastManager))]
15. public class PlaceOnPlane : MonoBehaviour
16. {
17.     [SerializeField]
18.     [Tooltip("Instantiates this prefab on a plane at the touch location.")]
19.     GameObject m_PlacedPrefab;
20.  
21.     /// <summary>
22.     /// The prefab to instantiate on touch.
23.     /// </summary>
24.     public GameObject placedPrefab
25.     {
26.         get { return m_PlacedPrefab; }
27.         set { m_PlacedPrefab = value; }
28.     }
29.    
30.     /// <summary>
31.     /// The object instantiated as a result of a successful raycast intersection with a plane.
32.     /// </summary>
33.     public GameObject spawnedObject { get; private set; }
34.  
35.     void Awake()
36.     {
37.         m_RaycastManager = GetComponent<ARRaycastManager>();
38.     }
39.  
40.     void Update()
41.     {
42.         if (Input.touchCount == 0)
43.             return;
44.  
45.         var touch = Input.GetTouch(0);
46.  
47.         if (m_RaycastManager.Raycast(touch.position, s_Hits, TrackableType.PlaneWithinPolygon))
48.         {
49.             // Raycast hits are sorted by distance, so the first one
50.             // will be the closest hit.
51.             var hitPose = s_Hits[0].pose;
52.  
53.             if (spawnedObject == null)
54.             {
55.                 spawnedObject = Instantiate(m_PlacedPrefab, hitPose.position, hitPose.rotation);
56.             }
57.             else
58.             {
59.                 spawnedObject.transform.position = hitPose.position;
60.             }
61.         }
62.     }
63.  
64.     static List<ARRaycastHit> s_Hits = new List<ARRaycastHit>();
65.  
66.     ARRaycastManager m_RaycastManager;
67. }

 

Under XR management the "Must add at least one installed plugin provider to use this platform for XR" warning should also be shown in the console.

 

I just tested it out and it was nicely done but I am wondering about the performance difference. And if there are any future plans to use DOTS with it.

 

Any plans to integrate object movement with the grab mechanic? Currently ray touches object, object snaps on grip pull or touch. How would I implement object movement at the end of the ray on grip, joystick brings object closer or moves it farther away, trigger snaps object to controller like original remote grip selection.

 

I think all of my problems stem from ARRaycastManager API calls not working in the Unity Editor?

Does anyone have a work around for this?

I remember there was this solution from a while ago but it is no longer working.

https://forum.unity.com/threads/mock-ar-device-for-in-editor-simulation.546703/

 

Hello mfuad,

In that coming blog post is there going to be anything now on simulated planes and testing in the Unity Editor? I have been dead in the water because it does not look like ARRaycastManager calls work in the editor?

 

@StayTalm_Unity If you create a XR Grab Interactable, then add an interaction event but have it missing its connected gameobject, it will throw lots of errors once you try to pick it up or interact with it.

Can be recreated in the example scenes by adding an interactable event one a prefab in a scene with something assigned to the interactable event then trying to use that prefab in another scene where the event will be missing its assignment.

 

Hi, this seems weird to me too and I'm having to completely rethink the way my scene/app is architected. Is this always going to be this way? Did you get any answers to your above question? Thanks!

 

Yeah @scrant ::

 

YES!! Thank you again @ROBYER1

@jackpr @mfuad @Matt_D_work @StayTalm_Unity can someone confirm that this has been noted on your end? I'd hate to have it overwritten when your team pushes updates.

 

It's been acknowledged on their end and coming in the next update

 

Why is OnDeactivate not visible in the XR Grab Interactable component in Inspector? (and Custom Reticle). Whereas both are visible in XR Simple Interactable? both derived from XRBaseInteractable.

 

Drag and Angular Drag are zeroed on OnSelectEnter and they are not restored after OnSelectExit. It's pretty straightforward to fix it editing the XRGrabInteractable class, but it would be good to have it fixed soon.

 

@StayTalm_Unity In the WoldInteractionDemo scene, if you set the teleporter interaction usages from 'Trigger' to something like primary or secondary 2d axis, there is no way to get it to teleport using the axis values.

I dove in and debugged but the interaction handler event is never sprung despite the axis value being higher than the Axis threshold on the XR Controller script here:

**Edit: I have found that for some reason HandleInteractionAction is only called for the Trigger and Grip buttons, for anything else like PrimaryAxis2D or SecondaryAxis2D it doesn't get called

Code (CSharp):

1.         void HandleInteractionAction(XRNode node, string usage, ref InteractionState interactionState)
2.         {
3.             float value = 0.0f;
4.             if (inputDevice.isValid && inputDevice.TryGetFeatureValue(new InputFeatureUsage<float>(usage), out value) &&
5.                 value >= m_AxisToPressThreshold)
6.             {
7.                 if (!interactionState.active)
8.                 {
9.                     interactionState.activatedThisFrame = true;
10.                     interactionState.active = true;
11.                 }
12.             }

 

"Support for the new Input System is on the short term roadmap." - will this new release include that? This is very much needed, as other parts (e.g. ARFoundation) are moving more and more to deprecating the "old" Input System. Currently different parts are totally incompatible with each other.

@d4n3x: https://github.com/Unity-Technologi...lkit-Examples/issues/8#issuecomment-578129590

 

XR Ray Interactor never shows its states with respect to UI, despite it working just fine at clicking the UI itself.

The ray interactor says it is always 'Hover Active', however none of the 'On Hover Enter' or 'On Hover Exit' Interactor events we have set up are ever triggered.

Are we wrong in thinking that UI should be considered an Interactable? As it doesn't behave as one of show up in the XR Interaction Debugger as an Interactable.

The XR Interactor Line Visual knows that it is hovering over UI which is annoying as we want to use the hover state of the UI to trigger events.

 

"OpenVR is no longer a Unity supported platform in 2019.3 and beyond. Valve is currently developing their OpenVR XR Plugin, and they will share more information on where to access it once it is available."

oh crap.

 

OpenVR Support - This thread https://forum.unity.com/threads/xr-plugins-and-subsystems.693463/ is probably the best to keep up-to-date on the conversation [and focus it into]...

 

I wish the documentation would state that clearly, I managed to work around it by using a script with OnEnable/OnDisable attached to a custom cursor/reticle spawned by the interactor on the UI.

I mostly found it misleading as the raycaster changes colour over UI - something is exposed there even as simple as on hover/off hover that changes the colour of the line. We wanted to use that to trigger events, could it be exposed?

 

When you say “OpenVR is no longer a Unity supported platform in 2019.3 and beyond. Valve is currently developing their OpenVR XR Plugin” does that mean, when available, their plugin will work with XR Interaction Toolkit like other Unity supported plugins?

 

@Matt_D_work would be great to get a reply to my post above asking about input system support - thanks!

 

Unrelated to my previous questions - I just tried to show someone how the new XR Management stuff is supposed to work. Turns out, the samples referenced from the blog post, found here on GitHub, don't work. After looking into the issues, someone broke it with a PR 2 days ago, and QA approved, probably by only testing against a yet-unreleased version of the XR Interaction Toolkit (downloading an older commit from the samples works).
(Please, in the future use a "development" branch for stuff like that.)
...
Good timing with the blog post about XR Management, which drives more people into testing this!

 

How does one programmatically have an ARInteractable selected in code? For the life of me can’t figure this out. Don’t see any options in interactables, interactors, or interaction manager. Need to have the toolkit select something at various points in AR.

 

I noticed that on friday, and was hoping to have another release out but alas there's one last thing i need to fix first will hoepfully be monday!