search

PTCInc / vuforia-engine

Bug and feedback issue tracker for the Vuforia Engine SDK
https://developer.vuforia.com
20 stars 0 forks source link

MRTK3 Support #66

Closed ottersity closed 5 months ago

ottersity commented 1 year ago

Summarize your feature feedback Compatibility with MRTK3

Describe your feature Compatibility with MRTK3

Use-case description I think MRTK3 has a lot of cool new features that are important for some of our future use cases, so compatibility with it would be appreciated.

Business impact Easier Object Tracking to place match physical objects with virtual ones.

Workaround No

Additional context I can install vuforia and then mrkt3. After attaching the Vuforia Behavior.cs and Default Initializiation Error Handler.cs to the Main Camera of MRTK XR Rig I can deploy to hololens 2 without any errors. MRKT3 works fine, but vuforia don't detect my imagetarget (astronaut). There are no errors in the UnityPlayer.log. I used the same procedure which was working for me with MRKT2 and Vuforia.

ptc-pscheper commented 1 year ago

As you noticed, we don't officially support MRTK3 as of today. Thank you for the feedback as we're continuously looking to improve the SDK. I know our team has been looking into it, but at the moment nothing is concrete. Could you highlight which features of MRTK3 are important for some of your (future) use-cases which are not found in the older versions?

ottersity commented 1 year ago

For us as research institute rapid prototyping is really important and mrkt3 has lots of improvement which makes building e.g. UIs much easier/faster because it is based on the Unity-UI system. In addtion mrtk3 is finally based on Unity XRI which really improves the cross-platform support. Furthermore, mrtk2 will not be supported anymore so at some point we will be locked with an old unity version, to avoid this we would like to switch to mrkt3 as fast as possible - especially for new prototypes :-)

ptc-epassaro commented 9 months ago

Hi @ottersity, while we keep looking into this, there is a potential workaround for MRTK3 Support:

Make sure to follow the expected MRTK steps in our documentation. After adding the VuforiaBehaviour and the DefaultInitializationErrorHandler components to the Main Camera in the MRTK XR Rig, select the Camera Offset GameObject and set its Position in the Transform to (0, 0, 0) and the Camera Y Offset value in the XR Origin component to 0.

This should correctly display the augmentations at the appropriate position on the targets. If you try this, please let us know if it works for you!

ottersity commented 9 months ago

Hello :-)

thank you for the feedback. I will try it next week 👍

anjelomerte commented 9 months ago

Hi:) Just to clarify, are there any actual compatibility issues in terms of MRTK3 + Vuforia? I have been doing just that what @ptc-epassaro described for a couple of months now, working with image targets only though. Would be good to know if there is potential for further problems so I could plan in advance whether to use MRTK3 indeed or switch to MRTK2.

ptc-pscheper commented 9 months ago

@anjelomerte If you have applied the steps above, you should be good without issues. We're looking into switching to MRTK3 in one of our future releases. So if you're interested in using MRTK3, the above workaround should be sufficient as a workaround!

Faith012 commented 8 months ago

Hi! I tried to apply the steps described above and Vuforia is detecting my image, but for some reasons, in the first moment after my image is recognized I can see my game object which has to be just above my image, but after a very small amount of time, gameobject is going somewhere from his coordinates. In the console I can see that my image is still tracked normally but gameobject is missing from its position and is very far away. What could be the problem? Thanks!

ptc-epassaro commented 8 months ago

Hi @Faith012, which versions of Unity, OpenXR and MRTK3 are you using? Also, are you sure that the camera Y offset and the position of the CameraOffset GameObject are set to 0 and don't change?

Faith012 commented 8 months ago

Hi @ptc-epassaro I am using Unity 2022.3.17f1, MRTK3 (the latest versions for all packages) and OpenXR Plugin 1.10.0. This are the latest for now from the Microsoft MR Feature Tool). Regarding the camera Y offset and other stuff you described I set them up as in the sollutions provided above.

SangonomiyaSakunovi commented 8 months ago

I also meet this trouble, why the position of my gameobject isn`t above my image? Really strange, maybe need more configs?

ptc-epassaro commented 7 months ago

Hi @SangonomiyaSakunovi, we have identified the problem and currently the recommendation is to keep the MRTKInputSimulator deactivated when testing Vuforia features in PlayMode. Please check out the conversation in this thread for more details: https://github.com/PTCInc/vuforia-engine/issues/108

ashfaqueck commented 5 months ago

So the discussion here seems like about Hololens...

Can MRTK 3 and vuforia combined work in MagicLeap 2?

@ptc-epassaro @ptc-pscheper

ptc-epassaro commented 5 months ago

Hi @ashfaqueck, thank you for your question. Vuforia can work with MRTK3 on both HoloLens 2 and MagicLeap 2 when combined with OpenXR. The Vuforia documentation will soon be updated to show how to do exactly that.

We will post in this thread as soon as the updated documentation is online.

ptc-thesbyro commented 5 months ago

With the release of Vuforia Engine 10.24, MRTK3 is now fully supported for Magic Leap and HoloLens via a new Vuforia Digital Eyewear Unity sample. Check it out here: Vuforia Digital Eyewear Sample

Thank you all for your feedback,