Hi,
in my app, the world center seems to be off.
I'm using MRTK 2.7.0 with OpenXR 1.0.0 and Vuforia 9.8.8
On the Hololens, the Image Target gets recognized, but its position has a random fixed offset after the App initializes. The Setup is similar to the hololens2 Samples from the Asset store, but I cannot verify that the samples works as intended, because it doesn't compile.
I suspect, that the WorldCenterMode "Device" wich is enforced does not work properly? Extended Tracking and "Track Device Pose" are enabled.
the MRTK Maincamera under the Playspace has the VuforiaBehaviour and DefaultInitializationErrorHandler script attached. the Image marker are separate like in your samples.
running the app in the Editor with a Webcam works as expected. With that random offset on the Hololens, the ImageTargets are basically useless for me.
EDIT: I think I found the Culprit: OpenXR. Switching back to Windows Mixed Reality in the Project settings and using a default mixed reality profile in the MRTK solved the issue. This cost me hours! As far as I have understood, OpenXR is supposed to replace windows mixed reality in the future, which is why i opted for it.
tldr: DO NOT USE OPENXR!!!!!!!!!!!!!!!!!!!!!!!!!!
br
Laurenz
Hi,
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.
Hey there,
Hey there,
I am also having issues with
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.
I have the same issue and
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.
Hey there,
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.
I also have the same problem.
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!
Hey everyone,
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.
Does the problem only occur
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 there,
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
Spent the whole day with
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
Hello @bpuladi,
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.
Sadly it does not, the only
@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
Thanks for highlighting. I
Thanks for highlighting. I will check out the provided reproducible steps and come back to you.
Kind regards,
Patrick Scheper
Technical Community Manager
Can confirm tracking offset
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.
Well, for me the problem
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?
Hi everyone,
Hi everyone,
Patrick as has been pointed
-
Hey everyone,
Hey everyone,
Thank you for the great feedback that was provided over the past months. Because of your feedback we fixed the offset issue by officially supporting the OpenXR plugin with the newest Vuforia Engine release (v10.4.4)!
Hi,
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.
Hey there,
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
Hello
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.