Forum Discussion
Solved
Local Space can not be loaded from Quest to Unity
I am trying to load a Scene / Room from a Quest 3 into unity. The objects are being loaded, but their transform isn't. This seems to happen since Update 60. MetaStoreHelp Is this a known error and...
And you want to know what? I also found the real problem!
It's the HTC Vive Business Streaming software! No wonder nobody else has this issue, because who would work with HTC and Meta at the same time? But right after installing the "Vive Business Streaming", I get the same issue, so it seems like it interferes with the OVR / OpenXR - version / level / software / sdk / whatever on a fundementally level.
The reason I installed that software a while ago was because I wanted to use the new Ultimate Trackers in my application, but on a different system, without any HTC-Headset. Who would have thought, that this software also interferes with OVR...
Uninstalling THAT software and restarting resolves the issue!
What do you mean by "the object is being loaded, but the transform isn't"? I'm assuming that you have a OVRSceneManager and loader script in the scene, and you have setup prefabs for your scene objects and THESE are what are getting loaded, correct? Do your prefabs have "OVRSceneAnchor" scripts on them? If not, that might be the reason they aren't keeping position in your room space.
Also - you have enabled "Scene Support" in your OVRManager settings, yes?
Hi Jeff,
yes, I have the OVRSceneManager and Loader in the scene. To be exact, I have the same issue with the Basic Example Scene of the new "Mixed Reality Utility Kit", that was introduced in V.60. And since the Gameobjects are being imported from the Meta Quest directly, all the objects then have an OVRSceneAnchor attached by design. Otherwise, I wouldn't get the warning, triggered by the OVRSceneAnchor:
"[OVRSceneAnchor] [9321a5b7-80ae-b131-9fb5-2ef32da70e08] TryLocateSpace failed."
So, that is not the issue. Have you tried importing this data from the Quest into Unity yourself?
Just to be clear, the Transform works fine as a Build in the Quest, so it seems to fail while transferring that Transform-Data into Unity.
And yes, Scene Support is enabled as well as any other Settings on the Quest 3, the Oculus Application for Oculus Link as well as any other developer mode settings, sharing point cloud data and so on and on.
Like I said, even the basic example fails to load the position / Transform data of the imported Room Model data.
I am not talking about Gameobjects I created myself and added the scripts myself. I import the room from the Quest, that I set there with the room setup option on the Quest. I can see all the imported Gameobjects of that predefined room, they just don't have any transform-data (apart from (0,0,0)).
So if you know any other ideas that might resolve that issue (maybe a deeply hidden setting?) I am open to new ideas.
MetaStoreHelpYou guys have any more insight into that issue?
Greetings
Florian