-
Notifications
You must be signed in to change notification settings - Fork 4
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
Failed to initialize Insight Passthrough. (in Unity Playmode) #3
Comments
TBH, I never tried. Have you deployed it, and does it work on your Quest? |
I couldn't build the apk file. I am currently testing with the Quest 3 with Unity Editor version 2022.3.18f1. I get an error when I build the project for Android. Could you tell me which platform you choose? I think there are two possible reasons for the issue:
|
Yeah, I didn't test with newer Unity versions and yes, it probably uses old packages. As you may have noticed, the project is a bit older than the Oculus Quest 3. I could run the package, but I also got build errors, although different than yours - I get a Gradle error. I am sorry, I don't have solution ATM. I am currently building a new app that should run on Quest as well, so I will probably need to have a look into this subject, and will most likely publish new samples. Later. |
I found a way to connect MRTK3 with Quest 3 passthrough using "OpenXR Meta"😊, but it only works in build mode and not in play mode... |
Thanks for your comment! |
Same problem with v68 on Unity 2023.2.20f1 |
Have you tried building the app and deploy it? |
Hi! I've been enjoying your informative blogs and codes you've been sharing. I think your latest project, connecting MRTK3 with Meta Quest's Passthrough in an OpenXR Platform, is quite remarkable. However, even though I cloned the code and used it as is, I encountered a "Failed to initialize Insight Passthrough" error in play mode. Does this project not support play mode and can only be verified through building? Thanks as always for your help.😊
The text was updated successfully, but these errors were encountered: