Search Issue Tracker
Fixed in 2018.2.X
Votes
1
Found in
2018.1.0b8
Issue ID
1008162
Regression
No
[XR] TrackedPoseDriver does not work with Daydream
How to Reproduce:
1) Add a cube to a new scene.
2) Attach a trackedPoseDriver to the cube.
3) Set the trackedPoseDriver's device field to 'Generic XR Controller'.
4) Set the trackedPoseDriver's pose source to 'Right Controller'.
5) Build and deploy to a Daydream capable device.
6) Run the app and observe that the cube's transform is unaffected by the trackedPoseDriver when a controller is connected.
7) Retry with 'Left Controller' and 'Remote' fields for the trackedPoseDriver and verify the same incorrect results.
Expected result: The cube should follow the daydream controller's rotation.
Actual result: The transform remain static regardless of controller orientation.
Reproducible in: 2018.1.0b8, 2017.3.0p4, 2017.2.1p3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Screen position out of view frustum...” errors are thrown when zooming out in the Scene view after creating UI GameObject
- CurveTexture is not being released when unloading AssetBundle containing a Scene with ColorCurves post-processing component in Global Volume
- Crash on ExtractActiveCasterInfo when navigating the scene view in a project with specific lighting data
- Build Profile name increments when numeric suffix is removed from duplicate Profile name
- "Unrecognized block header in profiler data file, stopping deserialization" error is shown and no more profiler data is recorded when the Player is connected and profiler recording is enabled/disabled few times
Add comment