Forum Discussion

🚨 This forum is archived and read-only. To submit a forum post, please visit our new Developer Forum. 🚨
robk.spacialxr's avatar
robk.spacialxr
Honored Guest
2 years ago

"MRUK couldn't load any scene data" in SDK v65

  • I'm using Unity version 2022.3.29f. 
  • My Meta Quest Link has "Spatial Data over Meta Quest Link" set to true.
  • Using SDK v64, I was/am able to load scene data in editor. 
  • Using SDK v65,  I am not able to load scene data in editor and receive the standard error:

"MRUK couldn't load any scene data. Scene capture does not work over Link or XR Sim.
If using Link please capture a scene with the HMD in standalone mode, then access the scene model over Link.
If a scene model has already been captured, make sure the spatial data feature has been enabled in Meta Quest Link (Settings > Beta > Spatial Data over Meta Quest Link).
If using XR Sim, make sure you have a synthetic environment loaded that has scene data associated with it."

 

5 Replies

Replies have been turned off for this discussion
  • We also have this issue on 2/3 of our machines. Any luck finding a solution?

    • robk.spacialxr's avatar
      robk.spacialxr
      Honored Guest

      Sadly, no.  We're 3/3 on our machines.  I'm surprised it works for 1 of your machines at all.  Maybe there's a clue there?

      I had hoped someone from Meta might answer this...

  • same. I have to change the SDK back to v64(in the unity package manager), and things went back to normal.

  • same happened to me today, but it was working fine before.

    workaround solution : 
    -in your headset remove all spatial data (parameters > physical space > space configuration )and redefine your room again with walls and furnitures.
    works after that.

    sidenote : this usually happens when the headset loose the guardian and you have to redefine it.

  • All of a sudden I am experiencing this error in my project. I am on v74. The link settings are configured. Resetting the physical space and regenerating doesn't work. Anyone else experiencing this? Seems there was an update to the headset which broke things but I cannot be certain.