-
Notifications
You must be signed in to change notification settings - Fork 25
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
app won't read Qr codes on second launch #21
Comments
Mmm. Not sure. What do you mean with "turn off" or "close the app". If you just leave it, for the home menu, it might stay active and not properly initialize anymore. What branch have you been using? There are quite some variants now, see. |
I leave for the menu and close the tab that is popping up. |
So i managed to make it work, I used the debug logger and saw that it was detecting the Qr code but it was not creating the marker. I can't say for sure where the real problem was but working with your code will allow me to further understand it and maybe i'll come back with the solution another time :) Thanks again!! |
@MattLsc ah yes... In this article https://localjoost.github.io/Positioning-QR-codes-in-space-with-HoloLens-2-building-a-'poor-man's-Vuforia'/ there's a video in which I try various sizes. 10x10 is almost instant success - 9cm works also okay, below that the success rate rapidly drops off. Glad you were able to fix it it yourself. Have fun and good luck! |
Hello,
First of all, thanks for the code and the explanation on you blog it's really helpful for beginners like me :)
I'm having a problem using the MRTK3 project.
It's building fine and it's working perfectly on the first launch (the one where it's asking for permissions) but after i close the app or turn off the hololens 2 and try to launch it again it seems unable to read the Qr code again.
I checked and the app still have the permissions to use the camera, it seems to be running correctly (I can press the reset button) but still it doesn't read the Qr code.
Any suggestion on how to fix this problem ? Thanks a lot!
The text was updated successfully, but these errors were encountered: