Forum Discussion
Solved
MR Utility Kit 63.0 - Scene Does Not Load From Device
Configuration: Meta Quest 3 UE5.3.2 (Windows x64) Mixed Reality Utility Kit Plugin 63.0 MetaXR Plugin 63.0 I just started using the MR Utility Kit and am having some problems with the sample pro...
Long story short, it is working now!
I have used the MQDH before and looked at the device logs, but didn't know you could filter by app name, so hadn't found these logs very helpful in the past. So thanks for that!
Using the MQDH device logs and filtering on my app name, I noticed that there was some kind of trust issue with the app, which made me think maybe it was needing to connect to a Meta or Unreal server online. I develop in an environment where the headset is offline. So I went down to our lab, connected it to WIFI, and ran the sample project app and my VRTemplate app. After launching them multiple times, both failed to load the Scene, same as before. Disappointed, I went back to my desk to continue working offline. The headset had lost its Boundary, so I had to create a new one. I launched my test app, and voila, the Scene suddenly loaded. I reinstalled the app to start over fresh and see if I would need to go back to the lab and get online or recreate the Boundary again, but the Scene loaded fine without having to resort to any tricks. So not exactly sure which action fixed the problem, but I'm guessing it was launching the app while connected to the internet. Hopefully my journey here can help some other poor soul out there. 🙂
I appreciate you helping me think through this. It was very helpful!
I'm using the sample project that comes zipped up in the Utility Kit v63 download. I also added the Meta plugins (MetaXR and MRUK) to a brand new VR Template project, and it behaves the same way (Scene data loads in VR Preview and PCVR, but not with APK). I tried rolling back both plugins to v62, and still the same behavior. Permissions seem to be fine; Unreal just fails to load the Scene data. I have not had the need to debug an APK on the headset before, so that is a bit new to me. Haven't really figured out where to find the relevant information that might explain the load failure.
Glad the delegate helped! I modified mine slightly to let it work with VR Preview. It was hanging at the delegate because the Permissions dialog does not appear while working via Link, so this let it bypass the delegate in VR Preview, which apparently doesn't need permission, probably because "Spatial Data over Meta Quest Link" is enabled in the Oculus client app.
Super strange man. Yeah, might be time to bring out debugging the headset. Easiest way I've found is to install the developer hub (https://developer.oculus.com/meta-quest-developer-hub/). You probably already know how but just in case, go to the Devices tab and click the Device Logs button on the right and then start the app on the headset. You can filter the logs by the app name and see what's going on. Hope you get some resolution here.