Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Delayed Initialization Image Target Offset Hololens 2 #172

Open
davidjbain opened this issue Dec 27, 2024 · 1 comment
Open

Delayed Initialization Image Target Offset Hololens 2 #172

davidjbain opened this issue Dec 27, 2024 · 1 comment
Labels
bug-report Bugs and issues

Comments

@davidjbain
Copy link

Summarize the bug:
I recently upgraded from vuforia 9.8.13 to 10.28.4. I am having issues getting delayed initialization to work properly for image targets in this newer version. I am using unity version 2022.3.44f1, open XR, building to a hololens 2. When I use delayed initialization the image targets appear to have a random offset when observed.

Observed problem
When you delay initialization, then start vuforia after the scene loads, you will notice the image target overlay is offset compared to the actual physical image when you observe it.

Expected result
Being able to start the vuforia engine later and still be able to get accurate image overlays just like I was able to do with vuforia version 9.8.13.

Reproducible steps
Steps to reproduce the behavior:

  1. Follow this tutorial specified for the hololens 2, unity version 2022.3, (import vuforia, mrtk3 packages ect.)
    https://developer.vuforia.com/library/platform-support/vuforia-digital-eyewear-sample
  2. Go to Window/Vuforia configuration, check the box next to "Delayed Initialization"
  3. Open the 1-ImageTargets scene
  4. Add a script to the scene that calls VuforiaApplication.Instance.Initialize() after a short delay (e.g., a couple of seconds).
  5. Build that scene to your hololens and notice the offset to the images.

Affected Vuforia Engine version:
10.28.4

Affected platform:

  • Workstation OS: Windows
  • Platform Unity
  • Platform version [2022.3.44f1]

Affected device:

  • Name: [Hololens 2]
  • OS: [Windows 10]

Additional comments
The point of being able to do this is because I don't want the camera constantly running. I really only need to use image recognition at a brief certain point, I don't need it constantly running, just trying to optimize performance and battery life. Let me know if there is any more information you need, or anything I should try first. Thank you for your time

@davidjbain davidjbain added the bug-report Bugs and issues label Dec 27, 2024
@ptc-emaggio
Copy link
Collaborator

@davidjbain thanks for the report. We will look into the issue and contact you in case we need more information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug-report Bugs and issues
Projects
None yet
Development

No branches or pull requests

2 participants