Hey there,

This issue was solved in v10.4.4. I wasn't able to reproduce any issues with our latest samples. If you're experiencing similar issues as described below I recommend creating a new post with all details regarding the issue. 

Kind regards,

Patrick Scheper

Technical Community Manager

Is the Vuforia and OpenXR problem still not resolved? Would love to have an official answer from PTC on this as this is decisive for our next development cycle.

Thanks

Hey,

My project was made using Windows Mixed Reality, Vuforia (before 10.4.4) and Unity 2021.1.20f1. I updated Vuforia and MRTK to latest version (MRTK from github not from package). After Unity Update to latest Version I have to use Open XR and there we are. Offset still exists.

Regards

Łukasz

Hello

I'm not able to share my project but I can tell you that I'm using latest release of MRTK from Github - copied code - not from package.

I'm using Vuforia 10.5.5 which was updated from previous versions, If there is something which I can check to see if Vuforia is fully up to date, please tell me how can I do this.

I'm loading model targets at runtime from different databases.

Regards

Łukasz

Hey there,

Would you be able to provide reproducible steps for us to be able to test? The issue presumably was fixed in v10.4.4. 

Kind regards,

Patrick Scheper

Technical Community Manager

Hi,

the issue seems to persist even after 10.5.5.

There seems to be a same issue described below when using OpenXR.

Using Unity 2020.3. 

Hi,

The problem seems to still exists. I have Hololens 2 app with OpenXR, Vuforia updated to 10.4.4, Unity 2021.2.11 and the offset still exists.

What can I do?

Regards

Lucas

Thanks for highlighting. I will check out the provided reproducible steps and come back to you.

Kind regards,

Patrick Scheper

Technical Community Manager

@medabit, @pscheper, sadly it does not work with the standard example and Windows Mixed Reality either.

This is what does not work with Unity 2020, Vuforia 10.3.2, and gives an offset

• Bug 1: OpenXR (did not test myself)
• Bug 2: Windows Mixed Reality, with the basis 0-main example. This one does not use MRTK. To reproduce: create a new Unity project, import Vuforia Engine, import Vuforia sample for HoloLens 1 + 2, loaded scene 0-main, activated that in the build settings, and build.
• Bug 3: Windows Mixed Reality, with WorldLocking enabled. This is a major issue, because this is the only remaining method for anchor management in Unity 2020.

This is what does work:

• Windows Mixed Reality with the example 0-ManagerScene. This one uses the MRTK.
• Windows Mixed Reality with WorldLocking disabled.

So this is pretty bad and makes Unity 2020, Vuforia 10.3.2 not workable for HoloLens 2.

-

Hi everyone,

We are continuously working with Microsoft to fix the issue that has been described here when using Vuforia Engine and OpenXR. There will be a fix for the issue in the next couple of releases of Vuforia Engine. The world origin changed in OpenXR which wasn't supported with Vuforia Engine, yet. This will be changed. 

Until then there's sadly no workaround when using OpenXR with Vuforia Engine but wait for the fix to release. I am sorry about that, but I am happy that we'll be able to provide a fix soon.

Thanks! 

Kind regards,

Patrick Scheper

Technical Community Manager

Hello @bpuladi,

So the Engine Unity Samples for HoloLens do not work? This is built and tested with each release, so our expectation is that if you build it as-is, it will work.

https://assetstore.unity.com/packages/templates/packs/vuforia-hololens-1-2-sample-for-unity-2021-1-and-later-183725

Thanks,

Vuforia Engine Support

Spent the whole day with Unity and Vuforia and the HoloLens 2. So I can't find a combination that is runnable. Does anyone have any project that runs correctly?

Best regards

Well, for me the problem occurs independently of OpenXR. This is a general problem with HoloLens 2.

Is there any news in the meantime? I mean, it worked well for so long, why not suddenly now?

Is there a Vuforia version where it works?

Thanks for the feedback :-)

Hey there,

Unless someone else knows otherwise, the latest I know is that this only happens when using OpenXR.

Hope that helps for your trials next week. Good luck! 

Kind regards,

Patrick Scheper

Technical Community Manager

Does the problem only occur with OpenXR? Or on the entire Hololens 2? That would be very important for me, since we have to do another trial this week.

Hey everyone,

Your feedback is very important, so keep it coming!

Sadly this is a deeper issue where no temporary fix has been found yet. Our R&D team has been working with Microsoft to find a solution and is still working on it.

Kind regards,

Patrick Scheper

Technical Community Manager

I also have the same problem. It can not be a setting problem? I tried it with both Vuforia 10 and 9 on a HoloLens 2. It's really messy.

When do you plan to solve the problem? Will it work this year?

Thank you very much!

Can confirm tracking offset with Vuforia and OpenXR.
The offset seems to be random or at least dependent
on when and where the image comes into sight.
Orientation seems to roughly match, but location is offset by
anywhere between a few centimeters and a couple of meters.

Setup:
Unity 2020.3.17
Vuforia 10.1.4
MRTK 2.7.2
OpenXR 1.2.8
(for Hololens 2)

Hey there,

First of all, I'm sorry that all of you are currently being affected by this issue. It's recognized and look at internally by our R&D team.

In the meantime I am trying to find out if we can provide a temporary solution for all of you working with OpenXR.

Kind regards,

Patrick Scheper

Technical Community Manager

I have the same issue and would really appreciate some reactions from PTC. The problem is probably easily fixed, it's just an offset from the original position, depending on the distance between user and target, as it seems to me. Since we have to switch to OpenXR, a quick solution would be great!

I am also having issues with OpenXR and vuforia, when using model targets. Since Windows Mixed Reality is not recommended for new projects I hope that this is being looked at.

Hey there,

Until now! I've seen multiple requests pop up and I have been seeing internally if anyone has tried integrating OpenXR. I cannot say for certain why this issue occurs, but it seems to be constantly regarding drift and offsets. Anyone else that runs into this issue, it would be helpful to comment in this same thread. Also any other findings or solutions are appreciated!

Hi,

I have the same issue, using OpenXR and I had to switch back to Windows Mixed Reality. As it is marked as deprecated, it is a shame, that the issue still exists and there is no answer from PTC.