Any example of the new 2019.1 XR input system?

What is it today? With 1.40, Oculus removed that entry in the manifest. Are we still going to need that proposed checkbox?

Also, am I right in that if I import the Oculus Integration asset, I'm overriding the Oculus libraries in the Unity Package Manager?

That was from May. Are the XR Legacy Input Helpers still recommended?

I'd like to avoid tying myself irrevocably to Oculus, so I'd like to make a purely XR app even tho right now I've only a Rift and Quest to work with.

 

Hi, I'm new to this new XR input system. Do I need to install "XR Management" and "Oculus XR Plugin" to use it?
Instead of the legacy TrackedPoseDriver, what component should I be adding to our left and right controller objects?
I'm on 2019.3.0b4. Thanks in advance.

 

Thanks. It works. One question: Is there a new way to get controller velocity or is XRNodeState.TryGetVelocity() the most current?

 

Many thanks for the quick response.

 

There's a bug in the angular velocity of a tracked controller. It doesn't take into account the rotation of the tracked object. In effect, it reports the same angular velocity no matter what direction you point the controller. Adding the rotation of the controller to reported angular velocity fixes it.

 

I think I'm talking about the bug you refer to. I'm using the Oculus SDK. Angular velocity seems to be in local space. Adding the rotation of the controller, ie. converting to global space, works.

Question: if the controllers are missing at init time, do you recommend subscribing to XRDevice.deviceLoaded to discover them later? Is there a better alternative?

Thanks,

 

Hi Tom,

Regarding getting or setting the origin mode flags - when I try to access the InputDevice's subsystem, it's always returning null. Am I doing something incorrectly? (I'm on 2019.3.0b3, building for the Quest)

Code (CSharp):

1.  
2.     private void OnEnable() {
3.         InputDevices.deviceConnected += OnDeviceConnected;
4.     }
5.  
6.     private void OnDisable() {
7.         InputDevices.deviceConnected -= OnDeviceConnected;
8.     }
9.  
10.     private void OnDeviceConnected(InputDevice device) {
11.         if (device.characteristics.Is(InputDeviceCharacteristics.TrackedDevice | InputDeviceCharacteristics.HeadMounted)) {
12.             if (device.subsystem == null) {
13.                 Debug.Log("Subsystem is null");
14.             } else {
15.                 Debug.Log(device.subsystem.GetTrackingOriginMode().ToString());
16.             }
17.         }
18.  

 

@StayTalm_Unity - So I went ahead and switched from the built-in Oculus SDK to the Oculus XR Plugin, and also added the manifest (which was needed to prevent the Quest from being seen as a Go).

It works, but now positional tracking for the controllers has a considerable amount of jitter.

When I switch back to the built-in SDK (and remove the manifest), the jitter goes away. I am not using the Oculus Integration in either case, and was using Tracked Pose Driver.

Is this a bug, or is it something on my end?

 

Yes. roomera's post answered my question immediately. Thank you. I ran into problems making the new XR Input work with the vive so I went back to using SteamVR plugin for vive, and the new XR Input for oculus. Hope to revisit it in a couple months.

 

Still no able to switch Quest to floor tracking. Every game on the store seems fine but mine has this weird offset. Any advice?

 

Sorry didn't see your post. I'd posted here in the meantime: https://forum.unity.com/threads/bug-floor-height-useless-on-quest.758183/

But it should be relative to 0,0,0 local or world space?

 

Hi Matt! Thank you for replying.

Yep got exactly that so far:

Camera, Left Hand and Right Hand have a TrackedPoseDriver component, and are locally positioned at 0,0,0
The parent (Camera Rig) is currently 0,0,0 and it is that which I'm trying to get an offset from so I can move the Rig up a little or down so that perceptually in VR, the controller would be at my feet if I put it down.

I realise now starting in roomscale vs sitting makes the device decide to use completely different coordinates, so I need to figure out how to do that. I wanted to go with Oculus's Unity's recommendation to use XR instead of the oculus stuff but there is no documentation for it and massive holes in my knowledge.

From what I am reading from you, I should be looking for some kind of event or callback and modifying the Camera Rig (offset in in your example) Height each time the user changes that, as it will be often different, even while app is running.

I am not using relative because it's marked as deprecated and I want to do everything exactly correct for the latest recommendations by Unity. I don't want to use anything that's going to be deprecated.

So how do I a) know when the tracking changes from say roomscale to seated, and b) how do I get the offset to the floor for the Camera Offset ?

It's really confusing just finding those things. Or polling for changes. I honestly don't know where to look first since there's what seems to be 3 different API's each time I google...

 

I can't get trigger values from hardware trackers even though the vive trackers have that functionality via their pogo pins. Is there a reason why this is missing or should it work? I ran TryGetFeatureUsage on the hardware tracker input device and it didn't return trigger so I'm guessing it wasn't implemented. I'd like to switch to XR but this is a blocker for me. We run 4 trackers at the same time, each with custom hardware and I need to get trigger input from them.

Any chance we can get this @StayTalm_Unity or @Matt_D_work?

 

I was about to build a new VR project and I realised this new changes.

I am using VRTK developing my project and the camera that I use is the UnityCameraRig which set as stationary mode. After changing into this new XR input system, the camera shift up to what it suppose to do. And I cannot reset it using InputTracking.Recenter().

VS tells me to use XRInputSubSystem instead. So I type in XRInputSubSystem. but no available function comes on editor. How do I set the mode back to Stationary Mode again and recenter the headset when needed? Do I need to attach a new XRInputSubSystem component or what?

 

Sorry, I found what I need from other thread:

Code (CSharp):

1.  
2. List<XRInputSubsystem> subsystems = new List<XRInputSubsystem>();
3. SubsystemManager.GetInstances<XRInputSubsystem>(subsystems);
4. for (int i = 0; i < subsystems.Count; i++)
5. {
6.    subsystems[i].TrySetTrackingOriginMode(TrackingOriginModeFlags.Device);
7.    subsystems[i].TryRecenter();
8. }
9.  

Here is what you need if you want to reset camera or set tracking mode.

 

I've been using SteamVR but I'm trying to transition to XR Input. I've started by using TryGetFeatureValue(CommonUsages.devicePosition... to place objects representing my Vive trackers which seems to work fine.

My problem is when I need to move the player to specific place. Using SteamVR I just move the camera rig object, and the trackers follow along.

If I try the same approach in the XR Interaction toolkit demo, they don't move when you move the XR Rig despite being child objects.

Is there a way to do this or am I just missing something?

 

If you place your camera AND controllers under a gameobject without the components that use the tracking code. You can move the parent game object it's children, the tracked objects. should follow along.

 

Thanks for confirming you can do that. Double checked and I was using transform.position instead of localPosition

 

This does not work with OpenVR headsets, and it seems InputTracking.Recenter() no longer works either.

https://forum.unity.com/threads/steam-vr-plugin-reset-position-and-orientation.389588/

Is there a solution for OpenVR headsets, since there is no OpenVR plugin for the new system?

 

Sorry you are correct, it does still work but its marked as deprecated. What should we use for OpenVR if this API is going to be removed and there is no OpenVR plugin for the new system?

 

@StayTalm_Unity :
Is there any chance we'll see Valve Index + bone hierarchies working W/O SteamVRInput 2.0 in the next year or two?
It seems like these bone hierarchies should be a pretty standard framework moving forward - it seems universally generic to me, since it's modeling anatomical characteristics.

 

@StayTalm_Unity :
Cool. Yeah I've been playing with your hand framework a bit but trailed off after realizing the relevant Index Controller features are walled off like that. It doesn't feel right having to implement SteamVRInput 2.0 solely for the purpose of gaining access to finger tracking on the Index when the remainder of the input data is entirely available through Unity.
Like you said: "The data is there", but it's a bit scattered and lacks cohesiveness at the moment. I'm sure I'm preaching to the choir

Thanks for the info.

 

Anyone else having difficulty getting accurate readings from touchpad controls? I've set up a fairly straightforward script to detect click direction on the an oculus go touchpad and it seems to be reporting the wrong vectors after a few clicks. (The same problem occurs with primay2DAxisTouch as well, in case you're wondering). Maybe the scripting is wrong? Suggestions or insights welcome.

Code (CSharp):

1. using System.Collections.Generic;
2. using UnityEngine;
3. using UnityEngine.Events;
4. using UnityEngine.XR;
5.  
6. public class Touchpad : MonoBehaviour
7. {
8.     private bool lastPressState = false;
9.  
10.     private List<InputDevice> devicesWithPrimary2DAxis;
11.  
12.     // to check whether it's being pressed
13.     public bool IsPressed { get; private set; }
14.  
15.     [Tooltip("Event when the button starts being pressed")]
16.     public UnityEvent OnPress;
17.  
18.     [Tooltip("Event when the button is released")]
19.     public UnityEvent OnRelease;
20.  
21.     private void Awake()
22.     {
23.         devicesWithPrimary2DAxis = new List<InputDevice>();
24.     }
25.  
26.     void OnEnable()
27.     {
28.         List<InputDevice> allDevices = new List<InputDevice>();
29.         InputDevices.GetDevices(allDevices);
30.         foreach (InputDevice device in allDevices)
31.             InputDevices_deviceConnected(device);
32.  
33.         InputDevices.deviceConnected += InputDevices_deviceConnected;
34.         InputDevices.deviceDisconnected += InputDevices_deviceDisconnected;
35.     }
36.  
37.     private void OnDisable()
38.     {
39.         InputDevices.deviceConnected -= InputDevices_deviceConnected;
40.         InputDevices.deviceDisconnected -= InputDevices_deviceDisconnected;
41.         devicesWithPrimary2DAxis.Clear();
42.     }
43.  
44.     private void InputDevices_deviceConnected(InputDevice device)
45.     {
46.         Vector2 discardedValue;
47.         if (device.TryGetFeatureValue(CommonUsages.primary2DAxis, out discardedValue))
48.         {
49.             devicesWithPrimary2DAxis.Add(device); // Add any devices that have a 2D axis.
50.         }
51.     }
52.  
53.     private void InputDevices_deviceDisconnected(InputDevice device)
54.     {
55.         if (devicesWithPrimary2DAxis.Contains(device))
56.             devicesWithPrimary2DAxis.Remove(device);
57.     }
58.  
59.     void Update()
60.     {
61.         bool tempState = false;
62.         Vector2 axis = Vector2.zero;
63.         foreach (var device in devicesWithPrimary2DAxis)
64.         {
65.             device.TryGetFeatureValue(CommonUsages.primary2DAxis, out axis);
66.  
67.             bool primaryPressState = false;
68.             tempState = device.TryGetFeatureValue(CommonUsages.primary2DAxisClick, out primaryPressState) // did get a value
69.                         && primaryPressState // the value we got
70.                         || tempState; // cumulative result from other controllers
71.         }
72.  
73.         if (tempState != lastPressState) // Button state changed since last frame
74.         {
75.             if (!IsPressed)
76.             {
77.                 IsPressed = true;
78.  
79.                 OnPress.Invoke();
80.                 Debug.Log("OnPress: " + GetDirection(axis));
81.             }
82.             else if (IsPressed)
83.             {
84.                 IsPressed = false;
85.  
86.                 OnRelease.Invoke();
87.                 // Debug.Log("OnRelease");
88.             }
89.             lastPressState = tempState;
90.         }
91.     }
92.  
93.     public enum Direction { up, right, down, left, none };
94.  
95.     public Direction GetDirection(Vector2 input)
96.     {
97.         Vector2[] directions = new Vector2[] {
98.                 Vector2.up,
99.                 Vector2.right,
100.                 Vector2.down,
101.                 Vector2.left
102.             };
103.  
104.         Vector2 dir = Vector2.zero;
105.         float max = Mathf.NegativeInfinity;
106.  
107.         foreach (Vector2 vec in directions)
108.         {
109.             float dot = Vector2.Dot(vec, input.normalized);
110.  
111.             if (dot > max)
112.             {
113.                 dir = vec;
114.                 max = dot;
115.             }
116.         }
117.         if (dir == Vector2.up)
118.         {
119.             return Direction.up;
120.         }
121.         else if (dir == Vector2.right)
122.         {
123.             return Direction.right;
124.         }
125.         else if (dir == Vector2.down)
126.         {
127.             return Direction.down;
128.         }
129.         else if (dir == Vector2.left)
130.         {
131.             return Direction.left;
132.         } else {
133.             return Direction.none;
134.         }
135.     }
136. }

 

quick question

Problem: When my controllers [Vive Wands] are off and I run my game, then in-game turn on the controller, I don't get input from the controller. If the controllers are on before the game starts the input is read fine.

The input debugger shows input coming into both controllers, but the scripts I have on the loaded controller model won't register the input.

I set my input device at start:

Code (CSharp):

1. m_Controller = GetComponentInParent<XRController>();
2. m_Node = m_Controller.controllerNode;
3. m_InputDevice = InputDevices.GetDeviceAtXRNode(m_Node);

and use TryGetFeatureValue calls during the Update loop:

Code (CSharp):

1. m_InputDevice.TryGetFeatureValue(CommonUsages.trigger, out m_TriggerValue);
2. m_InputDevice.TryGetFeatureValue(new InputFeatureUsage<bool>("TriggerButton"), out m_TriggerButtonStatus);

If unplugged, I get no value for m_InputDevice (GetDeviceAtXRNode), which leads me to believe I need to register to the InputDevices.deviceConnected event?? to set the device when it loads... Is this correct? and if so, is there a recommended way to do so in general?

***
What I'm doing now to get this to work is moving the GetDeviceAtXRNode call into a function "InitializeDevice()" which I then call anytime InputDevices.deviceConnected or InputDevices.deviceDisconnected is triggered (via OnEnable OnDisable) - it seems to work but I don't know if there's a better way to solve this issue

 

Is there a hard limit on the amount of input devices unity can detect? Seems to be 9? Someone posted the same question here but no reply https://forum.unity.com/threads/unityengine-xr-openvr-maximum-9-input-devices.721715/

I'm using XR Input to detect where on the body my 3 vive trackers are. This works fine, but if I'm in a room with 4 steam lighthouses, then I have 10 devices total and Unity wont detect 1 of the 3 trackers. Is there any way around this? Cheers.

 

I just double checked my setup using the SteamVR plugin, all trackers working as expected. Our apps need vive trackers in a room with many lighthouses. I'll have to stick with the old OpenVR set up for now, will test again when/if the new plugin arrives.

 

Getting input of the Cosmos controllers using the XR input system always returns false for everything if SteamVR is part of the project, and I couldn't strip it off, had to start a clean project and re-import all the assets.
Just a heads up for anyone encountering this.

 

I'm having issues with the BackButton for the Oculus GO.

Code (CSharp):

1. Controller.TryGetFeatureValue(CommonUsages.menuButton, out backButtonPressed);

It is not being reliable, it returns false intermittently and I can't figure out how to get around it.

Here is the code I'm using to test it( this works great on the Oculus Quest BTW) so it seems to be something specific to the GO controller, even if I change it to lefthand I see the same issue.

Code (CSharp):

1. void Update()
2.     {
3.         if (rightController.isValid)
4.         {
5.             bool backButtonPressed;
6.             rightController.TryGetFeatureValue(CommonUsages.menuButton, out backButtonPressed);
7.             if (backButtonPressed)
8.             {
9.                 buttonPressed.text = "MenuButton Pressed";
10.             }
11.             rightController.TryGetFeatureValue(CommonUsages.triggerButton, out backButtonPressed);
12.             if (backButtonPressed)
13.             {
14.                 //reset the text with the trigger
15.                 buttonPressed.text = "";
16.             }
17.         }
18.         if (leftController.isValid)
19.         {
20.             bool backButtonPressed;
21.             leftController.TryGetFeatureValue(CommonUsages.menuButton, out backButtonPressed);
22.             if (backButtonPressed)
23.             {
24.                 buttonPressed.text = "MenuButton Pressed";
25.             }
26.             leftController.TryGetFeatureValue(CommonUsages.triggerButton, out backButtonPressed);
27.             if (backButtonPressed)
28.             {
29.                 //reset the text with the trigger
30.                 buttonPressed.text = "";
31.             }
32.         }
33.     }

@StayTalm_Unity any idea how to get around this issue? Maybe a higher-level event I can hook into?

Really appreciate any help here,
Thanks!

 

Hi all,

I've been following this thread with interest and finally tried synthesizing some of the information into a single github. It contains examples based on the work of @icave_user @fariazz and @dilmer , plus the results of some additional work on my own. Hope it's helpful-- please feel free to improve upon it!
https://github.com/ibrews/XRInputExamples

 

Also, does anyone know what the current simplest way is to Recenter the user, both in position and
rotation? TryRecenter() seems to be a bit of a hassle.

https://docs.unity3d.com/2020.1/Documentation/ScriptReference/XR.XRInputSubsystem.TryRecenter.html

 

Using XR interaction toolkit, I set up a Teleportation request to the teleportation controller and teleport the user to world position 0,0,0 and rotation 0,0,0. Easy!

 

The reporting from

Code (CSharp):

1. InputDevices.deviceConnected

on the Quest has changed for some devices.

One, running versions 15.x of the OS & run-time, are presenting as Oculus Touch Controller whilst another, running 14.x, still shows Oculus Quest Controller.

Any insights would be appreciated.

 

Why not just map "joystick button 15" to a new button called "Triggered" in the input manager and check if its higher then 0 and make a if statement during a update call
Input.GetAxis("Triggered") > 0

 

Thanks for the quick reply. It's OK, our controller profiles are set up for all variations so it'll handle either.

 

I'm having the same issue. I'm getting no back button at all most of the time. I believe maybe like 1 out of 20 if I press it very rapidly I get a back button pressed, but like you said just for what looks like one frame. I do have a bug reported here: https://fogbugz.unity3d.com/default.asp?1239095_s4bfqrphq79lhr35

 

@joshb08 I was able to get it working checking for the Escape key instead, it reports every event and you can easily calculate long-press, long-press cancel, and short press. Hope this helps.

Code (CSharp):

1. private float timeElapsed;
2.     void CheckForBackButton()
3.     {
4.         if (Input.GetKeyDown(KeyCode.Escape))
5.         {
6.             timeElapsed = 0f;
7.         }
8.         else if (Input.GetKey(KeyCode.Escape))
9.         {
10.             timeElapsed += Time.deltaTime;
11.             if (timeElapsed > .75f)
12.             {
13.                 //long press
14.                 OVRManager.PlatformUIConfirmQuit();
15.             }
16.         }
17.         else if (Input.GetKeyUp(KeyCode.Escape))
18.         {
19.             if (timeElapsed < .25f)
20.             {
21.                 //short press
22.             }
23.             else
24.             {
25.                 //long-press cancel
26.             }
27.         }
28.     }

 

Hey, I've started playing around with XR coming from making regular games and I'm really struggling to understand this input system. I'm trying to check whether a button is pressed and it all just seems extremely complicated compared to the "Input.GetButton()" that I'm used to with the old input manager.

Here's me trying to get the state of the X button on an oculus controller, trying to follow the examples in the manual:

Code (CSharp):

1. void Start()
2.     {
3.         var leftHandDevices = new List<InputDevice>();
4.         InputDevices.GetDevicesAtXRNode(XRNode.LeftHand, leftHandDevices);
5.  
6.         if (leftHandDevices.Count == 1)
7.         {
8.             leftDevice = leftHandDevices[0];
9.         }
10.         else if (leftHandDevices.Count > 1)
11.         {
12.             Debug.Log("Found more than one left hand!");
13.         }
14.     }
15.  
16.     void Update()
17.     {
18.         if(leftDevice.TryGetFeatureValue(CommonUsages.gripButton, out buttonX)){
19.  
20.             print(buttonX);
21.         }
22. }

Doesn't register the button press for me. Could I please get some feedback on where I'm going wrong with this?