Disable occlusion for collaboration debugging?

Hello,

I’m noticing that during a collaborative session anchors created on the host device are appearing in a different location on client devices and it’s making it challenging to test other collaboration logic.

For example, when the client places a textured plane mesh at an anchor placed by the host, this placement can sometimes be considered as behind a surface and it gets clipped by RealityKits mesh occlusion.

I’d prefer if I could see it floating in space when testing so I can see that something is happening.

Im drawing a blank on if there are any debugging options to help me out. Nothing in render or debug options jumped out at me.

Thoughts?

Up vote post of J0hn Down vote post of J0hn
238 views
Posted by
J0hn
Reply
Add a Comment

Accepted Reply

Hey J0hn,

Im drawing a blank on if there are any debugging options to help me out. Nothing in render or debug options jumped out at me. Thoughts?

You were very very close ;), the scene understanding options live in a slightly different location from the render and debug options:

arView.environment.sceneUnderstanding.options = [.physics]

Choosing an option set that omits the occlusion option (and also the default option, because default includes occlusion) will effectively disable occlusion. In this way, you can still utilize the scene reconstruction mesh for collisions and lighting, without occluding anything.

You could also turn sceneReconstruction off altogether (if you don't need it) by manually configuring the underlying ARSession, but assuming you are just doing this for debugging purposes, it probably makes more sense to leave it on and just disable occlusion, that way you also get to debug with performance that is more representative of your actual app.

Posted by
gchiste
Up vote reply of gchiste Down vote reply of gchiste
Post marked as solved

  • So.. if I set my options to just [.physics] then I fail to construct a MultipeerConnectivityService(session: session) because it throws the error: RealityKit.MultipeerConnectivityService.SynchronizationError.sceneUnderstandingCollisionEnabled.

    I don't get this error when I leave sceneUnderstanding options alone. If I set the sceneUnderstanding options to [] or leave it as the default, it constructs fine.

    Also, I noticed that occlusion was still happening even if I set the sceneUnderstanding options of the ARView Environment to []. I discovered that I was setting the ARSession sceneReconstruction to mesh. Disabling that allowed me to see things without occlusion.

    Thank you for getting me closer to the right area.

    —
    J0hn
Add a Comment

Replies

Hey J0hn,

Im drawing a blank on if there are any debugging options to help me out. Nothing in render or debug options jumped out at me. Thoughts?

You were very very close ;), the scene understanding options live in a slightly different location from the render and debug options:

arView.environment.sceneUnderstanding.options = [.physics]

Choosing an option set that omits the occlusion option (and also the default option, because default includes occlusion) will effectively disable occlusion. In this way, you can still utilize the scene reconstruction mesh for collisions and lighting, without occluding anything.

You could also turn sceneReconstruction off altogether (if you don't need it) by manually configuring the underlying ARSession, but assuming you are just doing this for debugging purposes, it probably makes more sense to leave it on and just disable occlusion, that way you also get to debug with performance that is more representative of your actual app.

Posted by
gchiste
Up vote reply of gchiste Down vote reply of gchiste
Post marked as solved

  • So.. if I set my options to just [.physics] then I fail to construct a MultipeerConnectivityService(session: session) because it throws the error: RealityKit.MultipeerConnectivityService.SynchronizationError.sceneUnderstandingCollisionEnabled.

    I don't get this error when I leave sceneUnderstanding options alone. If I set the sceneUnderstanding options to [] or leave it as the default, it constructs fine.

    Also, I noticed that occlusion was still happening even if I set the sceneUnderstanding options of the ARView Environment to []. I discovered that I was setting the ARSession sceneReconstruction to mesh. Disabling that allowed me to see things without occlusion.

    Thank you for getting me closer to the right area.

    —
    J0hn
Add a Comment