Search Issue Tracker
Fixed in 2018.1.X
Votes
0
Found in
2017.3.0b8
Issue ID
968111
Regression
No
InputTracking.GetLocalPosition/Rotation(XRNode.HardwareTracker) does not return correct values
Steps to reproduce:
1. Download and open the attached project
2. Make sure you have a headset and controllers c
2. Enter Playmode
Expected result: Logs for HardwareTracker output real values
Actual result: HardwareTracker values are always 0
Reproduced on 2017.2.0b1, 2017.2.0p1, 2017.3.0b9, 2018.1.0a3
Feature introduced in 2017.2
Dev notes:
Updated documentation in changeset cc1c900032d6 for 2018.2.
It still won't actually return a value for the Hardware Tracker, but this is by design. I added documentation and a warning in the console that explains that GameController, TrackingReference, and HardwareTracker XRNode types are not singleton nodes (there could be multiple of them), and so you need to use InputTracking.GetNodeStates to get data on them. GetLocalPosition/Rotation is to be used with nodes that there can be only 1 of (Left Eye, Left Hand, Head, etc..) because there is no way to indicate which actual node you want on these older APIs.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment