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.

You may need to register your component. That helped me around that.

Thank you very much! I appreciate how responsive you guys are on RealityKit topics. Modifying meshes was going to be my original approach until I saw how easy stuff was in Reality Composer. I haven't made it to the 2021 vids yet, but I'll take a look at that one next.

Hey thanks, that's really helpful. It been tricky figuring out the right "google-foo" to learning this stuff. I'll stick with RealityKit. I'm actually not interested in the "capturing" aspects of RealityKit that seem to be really popular from last year. I'm mostly curious about the higher-level APIs for anchoring objects and coaching users through the AR setup.

I’m really curious about how to do this correctly too. I would prefer not to rigidly define my cell heights and would also prefer to style them for their available height if a larger cell makes the row bigger.