Skip to main content
CorangeD
New Participant
June 2, 2023

scene capture spam an error in the log

  • June 2, 2023
  • 7 replies
  • 2359 views

Hello,

I'm currently working with the scene capture feature (https://developer.oculus.com/documentation/unity/unity-scene-overview/) and i've been able to set it up correctly

but I have a problem with a log which is insanely repeated :

 

 

 Warn OpenXR_Anchor GetComponentStatus: Space does not support 0
 Error OVRPlugin [XRCMD][failure] [XR_ERROR_SPACE_COMPONENT_NOT_SUPPORTED_FB]: xrLocateSpace(*(XrSpace*)space, baseSpace, ToXrTime(GetTimeInSeconds()), &spaceLocation), arvr/projects/integrations/OVRPlugin/Src/Util/CompositorOpenXR.cpp:10267 (arvr/projects/integrations/OVRPlugin/Src\Util/CompositorOpenXR.h:307)

 

 

I am using 

- a Meta Quest Pro

- Unity 2021.3.15f1 with

- XR Plugin Management 4.2.1

- Oculus XR plugin 3.2.23

- Oculus OVR plugin 1.85 (included with the oculus XR Plugin)

The thing is the scene capture work well, and i can access the anchor i have set up, but the log are flooded with the mentioned message, making it unusable, so i would like to get read of it.

 

from what i understood of the error, the scene capture generate a space anchor that is not supported. Reading into the code, it seems to be a "locatable" anchor, but i don't know how such an anchor is generated/how to get rid of it.

 

Do you have any idea?

    7 replies

    Novelab
    New Participant
    July 17, 2023

    Bump, we have the exact same issue and we don't know how to get rid of it.

    Did you find any solution CorangeD ?

      ImpossibleRobert
      New Participant
      August 9, 2023

      Same problem on my end. Did you find any solution? I'll retry clearing all room data and setting it up new now.

        florianbuchholz1988
        florianbuchholz1988
        Inspiring
        January 15, 2024

        The error appears because of the OVRSceneManager trying to get access of the current used room / scene / space and failing to get the transform-data to place the objects of that room.

        It's important to know, that Scene Anchors and Spatial Anchors are not the same thing.
        See Use OVRSceneManager in https://developer.oculus.com/documentation/unity/unity-scene-use-scene-anchors/ for a more detailed explanation.

        On why this bug appears in Unity, I am trying to figure that out as well. It doesn't happen in the app, because there, the positioning of the objects of the room is working, so loading that data of that Scene Anchor seems to work as well.

        cecelu
        Participant
        January 3, 2025

        Hey, I also get the warning in the editor. I suspect that this is why my Meta XR Simulator keeps crashing, which makes testing really annoying.
        Has anyone found a solution to avoid the warning?

        florianbuchholz1988
        florianbuchholz1988
        Inspiring
        January 3, 2025

        Maybe you should post your actual error here first, so somebody can help you. You posted similar responses under two threads who seem to have similar errors, but are different and their solutions are also different.

        See?

        OVRPlugin] [XRCMD][failure] [XR_ERROR_HANDLE_INVALID]: xrLocateSpace(*(XrSpace*)space, baseSpace, ToXrTime(GetTimeInSeconds()), &spaceLocation)


        OVRPlugin [XRCMD][failure] [XR_ERROR_SPACE_COMPONENT_NOT_SUPPORTED_FB]: xrLocateSpace(*(XrSpace*)space, baseSpace, ToXrTime(GetTimeInSeconds())

         

        The one in this thread is because of space component and the other one is a different error, even though it might look the same at first.

        Maybe you even have another, slightly different error?

        Which Meta version are you running? There were issues with dynamic resolution (see here: https://communityforums.atmeta.com/t5/Unity-Development/Updating-Meta-SDK-from-65-to-66-White-Screen-in-XR-Simulator/m-p/1227470)

        If it crashes later but is starting, it could also be anything in the scene, so I suggest you actually post your error here.

          cecelu
          Participant
          January 3, 2025
          Thank you for your quick reply, I wasn't expecting that. 
          Ah, I see the difference... I wrote too quickly. 
           
          I am using Meta version 71 and have already tried to adjust the Dynamic Resolution settings.
          I can start the simulator and interact in it, but after a certain time it crashes.
          I get the following warning: 
          [OVRPlugin] [XRCMD][failure] [XR_ERROR_SPACE_COMPONENT_NOT_SUPPORTED_FB]: xrGetSpaceComponentStatusFB(*(XrSpace*)space, (XrSpaceComponentTypeFB)componentType, &status), arvr\projects\integrations\OVRPlugin\Src\Util\CompositorOpenXR. cpp:14905 (arvr\projects\integrations\OVRPlugin\Src\Util\CompositorOpenXR.h:340)
          UnityEngine.Debug:LogWarning (object)


          florianbuchholz1988
          florianbuchholz1988
          Inspiring
          January 3, 2025

          Okay, so it's the warning regarding the missing confirmation of the anchors. I suspect you get this warning multiple times when starting up the simulator? Depending on the virtual room, the amount of warnings you get differs, because each of the objects in the MRUK room throws that warning, but you can have more or less walls, tables etc.

           

          Is the simulator actually crashing the moment these warnings popup or is it happening later? This is important, because, even though these components-warnings are annoying, they never crashed my simulator before and they can be simply ignored. So it could be your own code that crashes the simulator.

           

          One thing it would try, is:

           

          - Create a new project

          - integrate meta SDK stuff, including simulator

          - start simulator

          (I have this always setup as my test environment and I always test Metas new versions there first, before updating my main project)

          If that also crashes after a while it can be the newest version of meta (haven't tried it yet), external software or even your hardware that causes the problem (not enough ram for example)

           

          If it does not crash, there are specific settings in your own main project right now, that might cause your issues. But then you know, it's not your hardware and it's not Metas standard settings, but something you added or changed.

          Terms & ConditionsAccessibility statement