stereolabs/zed-unity

Vive Tracker Accuracy

QUTRossBrown opened this issue · 1 comments

QUTRossBrown commented

Preliminary Checks

  • This issue is not a duplicate. Before opening a new issue, please search existing issues.
  • This issue is not a question, feature request, or anything other than a bug report directly related to this project.

Description

When using the Vive Tracker via the Zed Controller Tracker script, the location is always lower in Y than the other controllers. I cannot see why in my scripts.

A video is found here: https://youtu.be/0hZhRyvAcSY

Otherwise the unity framework is fine.

Steps to Reproduce

  1. Unity 2019.4.8f1
  2. Zed Unity - 3.1.2

...

Expected Result

I would expect the Vive Trackers to be mapped as well as the controllers. I feel the tracker y deviation is a bug in the code, as the controllers work very well in mixed reality mode.

Actual Result

Vive tracker has a consistent y deviation in camera space. Different to the Vive controllers

ZED Camera model

ZED Mini

Environment

Windows 10
Unity 2019.4.8f1
Zed Unity - 3.1.2

Anything else?

Cannot find this in any issues listed on GitHub, which I find odd, as it seems to be an error that should occur often with other AR framework users. I am not doing anything special, just using the "Zed Controller Tracker" script attached to a GameObject.

github-actions commented

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment otherwise it will be automatically closed in 5 days