Log in or register to post comments

The Position of The Target is in Reverse Direction

August 1, 2018 - 9:51pm #1

Hi, 

 

I've encountered a problem when using image target in HoloLens.

The position of the image target is in reverse direction.

For example, the image target is at (0.0, 0.0, -0.5), while it should be at (0.0. 0.0. 0.5).

Furthermore, when I move my target upward, the position goes downward.

However, it worked fine with the camera of my computer and my smartphone.

Should it be the problem of my project or my HoloLens?

 

I'm using  Unity 2018.1.1f1 and Vuforia 7.2.24.

 

Thank you for any suggestion.

The Position of The Target is in Reverse Direction

September 25, 2018 - 6:52am #3

I've more or less the same issue, the target is 20cm x 20cm, printed perfectly with this dimension. The scale is 0,2 0,2 0,2 in unity and the marker was uploaded with that dimension.

In the editor the model appear pefectly over the Image target, but on device the model is referenced to the origin of the Device Camera, not the World.

This mean that when the target is found, the model's transform.position is (0, 0, -0.5) and same for transform.localposition.

Instead I'm expecting to have differents positions. This value are referenced to the Hololens Device that has his own transform.position respected to the 0,0,0 that is the starting position when the app start.

Did I miss some settings?

I cannot choose "Camera" from the dropdown "WorldCenterMode" like in your video tutorial

I've enabled Device Tracker (Traking mode positional, Optimized for Image Tareget)

 

For the position I've fixed disabling the vuforia tracking when the image is founded, moving the GameObject to the center of the World and positioning it at the Hololens Position + the ImageTarget Poisition.

Now I've some issue abut the rotaion, and the object position is not so precise as I'm expeting.

Any ideas?

Thanks

The Position of The Target is in Reverse Direction

August 2, 2018 - 2:16pm #2

Hello,

Be sure that your printed target's size is the same as what is defined in the dataset. See-through eyewear is sensitive to these size differences, which can manifest itself in incorrect tracking movements.

This is not the case for other device types.

Thanks,

Vuforia Engine Support

Log in or register to post comments