Log in or register to post comments

Marker only registering larger movements of Marker

January 23, 2017 - 6:37am #1

Hi

i compiled and deployed the Hololens Vuforia example.

The marker as suggested has extended tracking on.

Unfortunately it does not register smaller marker movements, therefore making it really difficult to use it for fine alignment.

Notice though  that because of extended tracking the object can persist even after the marker is removed.

Can we fine tune somehow the extended tracking to perceive also these small movements?

Can there be a metric to switch extended tracking on off for small movement calibration?

Here is a video which shows what I am saying.

https://youtu.be/L5ECPAV3cLo

 

Thanks

Dimi

Marker only registering larger movements of Marker

January 25, 2017 - 3:37am #3

Hi

thanks for the reply.

I did some testing where i disabled the extended tracking. If you disable extended tracking there is no lag at all. But the hologram disappears as soon as you loose you view of the marker.

I think the problem with the Extended tracking that mention is not due to lag. Because even if you wait for longer periods the hologram is never updated when you do small movements. What I mean is that if it were lag, I would move the marker a little and after a few seconds i would see the hologram update its position.

Right now it never updates, unless you move or rotate the marker a significant amount. Its as if Vuforia has a threshold under which it does not send updates to Hololens. This is why I was asking if there would be a way to adjust this.

 

Thanks

 

 

Marker only registering larger movements of Marker

January 23, 2017 - 12:18pm #2

Hello,

Extended tracking allows the HoloLens spacial tracker to work with Vuforia's detection algorithms. The lag you are seeing is because Vuforia is only able to provide updates to the HoloLens tracker every 1 second or so. This is the positional lag you are seeing.

Vuforia is actively working with the HoloLens team to improve tracking performance, but at this time there is no way at the SDK level to adjust it.

Thanks.

Log in or register to post comments