-
Notifications
You must be signed in to change notification settings - Fork 96
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
Application keeps asking for Room Setup #7
Comments
@rolandsmeenk could you please let me know what device and OS you are using to do this. OS can be found either in settings>device Info or the Oculus App under settings. |
Device Version info seems to be available under Settings > System > Software Update Software Update Version Runtime Version OS Version |
@rolandsmeenk Thank you for the quick reply. |
@rolandsmeenk sorry I had thought I gave an update. I also wanted to make sure if you are trying this on Overlink aka pc link. If so room set up does not work overlink at this time. Last known option is to make room set before using overlink |
You have to configure your room setup before installing the app. Afterwards, uninstall and install the app again. |
I am in the exact same situation. The world beyond launched from the applab execute flawlessly. But when i build it in unity (same version than project), i have the same behavior described by rolandsmeenk. Configuring room setup prior to installation does not solve the issue. I am not using overlink. |
Coming here to say I have the same issue, quest 2 software up to date. Installed after room setup, still asks for room setup, hit done, throws error. A note is that I also installed Arkio (another app that uses scene data) and it is also unable to load the room data so it might be that the apps aren't being allowed access? |
I found a solution for me. I had the same issue of the app requesting a room scan despite having one. Once I used com.oculus.samples.theworldbeyond2 instead of com.oculus.samples.theworldbeyond, it worked fine. |
The same issues occur with just a regular installation off the store, so I don't think the key issue is this? It's weird that a rename would fix it though |
Thank you for pointing out the concerns. We are looking into it. I will update once something is found. |
I am having the same problem, any updates?
This unfortunately didn't work for me. I can load the scene over link, but fails on built application. |
Thank you for let us know. I was not able to get the issue. I can say yes changing package name is an option and in the works to be fixed. If you are trying to run in editor over pc link then room set up must be completed prior to launching pc link. Also be aware room capture is not designed to work on pc link. |
I'm stuck into the same problem that all run well in editor via Quest link but fail to load scene data in built apk in HMD. Have anyone figured out this problem? |
I ran into this as well. It turned out it was a missing permissions problem. Add this line to the AndroidManifest.xml file: |
Hey davyloots, so glad to see your comment, but I seem to be unable to see the content that you mentioned needs to be added in the AndroidManifest.xml file. Could you please send it again? Thanks! |
iiijasdf, sorry, the brackets hid the line in the comment, I've fixed it. Unfortunately, the issue reappeared for me just now, so it's probably not a full proof solution. But it definitely appears to be a permissions issue. |
have same issue, the add permission and change apk package name not work for me. |
After starting the application it shows a dialog with "Room Setup Complete", I select "Done" and then it shows a dialog with "The World Beyond requires Scene data. Please run Room Setup in Settings."
I've done Room Setup several times. My first room setup was triggered from inside the Meta Spark Player app, but I've also tried from Settings > Experimental Features > Room Setup. I've tried different sizes of room setups and clearing the previous setup, but that makes no difference. I've tried both the app from AppLab and the app built from this GitHub repo and the results are the same.
The text was updated successfully, but these errors were encountered: