TrackedPoseDriver in 2019.1

Where has TrackedPoseDriver gone in 2019.1? Am I supposed to use something else instead? It's even gone from the docs with the entire UnityEngine.SpatialTracking namespace

 

Ah. Apparently it's moved to the "XR Legacy Input Helpers" Package. But what am I supposed to use instead?

 

Will there be an equivalent component that allows to track position in a similar way? In which version of Unity do you think it will be removed? (asking because I'm using it in a training, and would like to know when we will need to update this material)

 

I ran into the same issue, and gradually pieced together the steps I needed to take. I am using Unity 2019.1.0b9. With the package manager I installed XR Legacy Input Helpers (2.0.2). I can see it correctly listed in manifest.json.

In my class which uses the TrackedPoseDriver, the " using UnityEngine.SpatialTracking; " still doesn't compile. "The type or namespace name 'SpatialTracking' does not exist in the namespace 'UnityEngine' (are you missing an assembly reference?)". I cannot find a reference to the TrackedPoseDriver or SpatialTracking in any other assembly.

This makes me feel incredibly frustrated. I have tried everything I can think of to try to understand what's happening here, or where the problem is, but have come to a dead end (including an install of 2019.2).

Please... what do I need to do to be able to use the TrackedPoseDriver in Unity 2019?!?!?

 

So, many issues seem to come back to the same origin. If you are one of the unicorns who actually unit tests in Unity, you'll be specifying your own assemblies. What happens then is that you'll need to look in your project (in the IDE) where you'll find a Packages folder in the project pane (you learn something new everyday). In there you'll find the XR Legacy Input Handlers folder, and buried inside there (Runtime->TrackedPoseDriver) the UnityEngine.SpatialTracking assembly. Find the assembly where you have a problematic assembly, and add a reference to this SpatialTracking assembly and it'll work.

Couldn't this have been documented somewhere?

 

In case it helps anyone, I was trying to get EditorXR working and getting the namespace error on SpatialTracking as well. Here's the relatively simple steps I followed to resolve it, from scratch of a new project:

1. Install the EditorXR Unity package and the XR Legacy Input from Package Manager. The error will show up.
2. Navigate to the Library/ScriptAssemblies folder of your project, and copy the UnityEngine.SpatialTracking.dll file. I'm not sure if they're needed, but I also grabbed the UnityEditor.SpatialTracking.dll file and both the .pdb files of same name
3. Create an Assets/Plugins folder in your project and paste the files into that.

This got me past the error and let me continue on with the troublesome journey of getting the rest of EditorXR to work.

 

Bless you, I've been trying to get this working all evening. I'd run in to this before when I tried out the PR to remove the SteamVR and Oculus dependencies in EditorXR. But then, all I had to do was import the Legacy package. I'm glad you posted the extra steps!

 

According to the very sparse docs, the InputFeatureUsage<Vector3> centerEyePosition is supposed to give me "The position of the center eye on this device." However, in relation to what? I can deduce that it is not world view because when I place an object at the returned position it's nowhere near where my head is in the VR game. It also doesn't seem to be an exact offset to the camera obj or the camera's parent, so how can I use it to replace the deprecated tracked pose driver on the camera?

 

Glad to hear about the incorporation of tracking origin.

I have a fair amount of experience developing for CAVE type systems. Any plans to integrate general purpose tracking systems (Eg. OptiTrack, ART, Vicon, Motion Analysis) or device aggregators like TrackD or VRPN? I've written a TrackD interface for Unity. Just started looking at the new input system. Is it extensible so that I can add new devices that aren't supported natively?

Setup is even a little more complicated when dealing with fixed position displays like projection walls where the relationship between the users (tracked) eyes and display surfaces are constantly changing. There's usually coordinate systems for the display space, tracking space, and virtual world space that need to be coordinated. I have scripts to manipulate the camera and projection settings, but I'd like to see some native XR support for those systems.

 

Do you have a map of what is new, what you want us to be using and so on? sorry to say even with 35+ years development I'm finding this a complete mess, throughout.

It is 100% unreasonable for customers to be wading through that without at least a map. I am attempting to use the latest XR.* packages but keep walking into what-ifs, random dev comments and even non-deprecated things that will be deprecated, or just plain not working. This of course is fine with the deprecated or soon to be deprecated stuff, but you're telling us not to use that, and I'm really trying but there's no really solid results.

Quite a lot of customer stress.

Just trying to even understand what I should be doing to get proper height (quest) - something that was a 2 min job in UE4. As it is, I'm really feeling confused!

 

Hey! thanks for reply. Well, I'd love a clear and concrete example of seeing the basic unity character controller doing a simple move with floor tracking on quest - I imagine this fulfils what most people need to decipher getting up and running with the new API.

So long as the basic height tracking is sorted. For the life of me i'm not getting consistent results, will have to sleep on it

 

Is there an example for https://docs.unity3d.com/2019.3/Doc...RInputSubsystem.TrySetTrackingOriginMode.html ?

I can't seem to get it to work.

 

I've noticed that there's a new Tracked Pose Driver (New Input System) in the Input System package. Are we supposed to use that instead? It wasn't obvious, since the Unity Manual recommends using the auto XR rig creation thing, and the default XR rig uses the Legacy Tracked Pose Driver.

The only way I found this out was by searching in the Components menu, after realising that the Tracked Pose Driver from the XR rig linked to the Legacy Helper package documentation after pressing the (?) button. There seems to be no documentation on this new component, aside from a scripting reference page in the Input System package documentation. There's no mention of this new component in the Unity Manual at all either.

The component seems to work for now though!

Edit: I'm on Unity 2020.2, if that helps!

 

Here's my super simple pose tracker:

Code (CSharp):

1. using System;
2. using UnityEngine;
3. using UnityEngine.InputSystem;
4.  
5. [Serializable]
6. [AddComponentMenu("Simple Tracked Pose Driver")]
7. public class MyTrackedPose : MonoBehaviour
8. {
9.     public InputActionReference centerPosition;
10.     public InputActionReference centerRotation;
11.  
12.     void Start() {
13.         if (centerPosition != null)
14.             centerPosition.action.Enable();
15.  
16.         if (centerRotation)
17.             centerRotation.action.Enable();
18.     }
19.  
20.     void Update()
21.     {
22.         if (centerPosition != null)
23.             transform.localPosition = centerPosition.action.ReadValue<Vector3>();
24.  
25.         if (centerRotation != null)
26.             transform.localRotation = centerRotation.action.ReadValue<Quaternion>();
27.     }
28. }

(parameters are input events of centerEye-Position & -Rotation)