Forum Discussion
Can't get the SceneModel
Hey guys.
I'm having an issue of pulling the SceneModel (Room that I have Setup) from any of the scenes in the The World beyond that use the OVRSceneManager to load the SceneModel. I've been using TheWorldBeyond (https://github.com/oculus-samples/Unity-TheWorldBeyond) to try and get this running. I have also created several new projects on many different versions of Unity (2020.3.18f, 2021.3.18f & 2022) and tried the VirtualFurniture Scenes from the Oculus Integration SDK - receiving the exact same issue as below.
I've tried default/different combinations of Build Settings, Package versions and Platform types (PC/Mac/Android) and still had no luck. I've attempted some of the solutions in this thread (https://communityforums.atmeta.com/t5/Unity-VR-Development/OVRSceneManager-can-t-query-scene/td-p/98...
I tried this on Windows 11 and Windows 10 and got the same error message.
Anchor support is set to Enabled as per the project default.
No matter what I've tried, I always receive the same error message - I'm just unable to pull the Room I've setup:
(PassthroughPet Scene)
(PassthroughRoom)
(TheWorldBeyond Scene)
I have tried building the scenes using both a PC and a Mac, and each time I load into the scene, it says "The World Beyond requires Scene Data. Please run Room Setup". I've ran the Room Setup around 30-40 times, trying different variations of wall numbers/desks/doors - still no luck of retrieving that data or even running The World Beyond build. HOWEVER, strangely, when I download the The World Beyond straight from the Oculus Store, it runs absolutely fine, it finds the room I've mapped and lets me continue with the experience. This seems to be a Unity only issue?
I contacted a friend who tested this on his Quest 2, and he was able to simply download the The World Beyond Unity code and click Play and have instant working access to the SceneModel. He was also able to build The World Beyond and go straight into the experience without the message above coming into play.
As mentioned, I've tried it on a PC and a Mac, still the same issue. I bought a second Quest 2 headset today to test this out, and still received the same issue.
The only visible difference between my two Quest 2 headsets, and my friends Quest 2 headset, is that my versions are 49.0.0.207 and his version is 49.0.0.186 (an earlier one by a few weeks I think?).
Can you give me a hand getting this resolved?
Message if there is any more detail needed.
Cheers guys
8 Replies
You just gotta love how they redirect you here to not ever reply to you again.
I'm having the same issue friend, did you manage to solve it?
Hey man! Yep I managed to resolve it, I ended doing a lot of troubleshooting so I'm not sure if it's a concrete solution, which is why I didn't put it up on here.
Add me on discord zeo #2699 and I can try and help out. That goes for anyone else too 😁
This is the same person who made the thread by the way, I've just had to make a new Meta developer account
great man, thanks! Adding you know
It's Been 2 Weeks I am stuck with this Problem. Please help. For me it's working fine when I make a build but its not working in Unity Editor.
Hey! I ended up fixing it by changing to a test account in the headset. You can create test users / accounts from the Oculus Dashboard.
Good luck!
PS: I factory reset the headset in the process, but I'm not sure if that is necessary. Maybe you can just add the test account.
Thank you so much, I will try and let you know.
Hello, it's now fixed, and I want to thank you for your help. Although I'm unsure how it was resolved, I tried adding a test account to my headset, but it didn't work. Next, I logged in to that same account on the Oculus desktop app, but it still didn't work. Later on, an update for the Oculus desktop app became available, so I updated it and restarted everything. After enabling all the features in the Oculus desktop app Beta Tab, the issue was finally resolved.
It could be the update or any of these steps.
