Yeah, that's not what I would expect given the code you posted either. Could be a good idea to file a feedback with the modified demo project.

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.

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.

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.

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

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.

This is useful if you're wanting to use the relative shape as a clipping shape (meaning it needs to retain its shape-ness) Otherwise you can use a spacing of 0 and using .padding(3) instead if .inset(by:3) in this example

It even feels kind of scammy if they’re going to charge per hour and use slower machines.

Oh gosh, Notification Center sounds like it could actually work. Idk why that didn’t pop into my head. I tried sticking the openwindow object into a singleton and it definitely broke the rest of my opens windowing functionality for unknown reasons. (literally just the act of passing the instance into the singleton cause open window commands from a context menu to fail)

Also now discovering that backgrounding and foregrounding my app after launch seems to break openWindow in a more general sense and this could be the source of me not discovering any solutions for this.

Yeah! This can make a lot of sense too, but my app is a Multi-Window app, so while I have an App-level AppState object, I also have A WindowGroup level SceneState. Can you think of any ideas to grab the "right" window state that the intent opens when it brings the app to the foreground? Like I said in a comment above, I think using "App's" "openWindow" environment property is the right solution in that case, but there appears to be a bug in the beta that causes it to not work atm.

I did not. I rewrote the application to be SwiftUI+AppKit. This has the advantage of unlocking the swiftUI window-size APIs that are hidden from catalyst as well. I think Apple is spread too thin and SwiftUI+UIKit+Catalyst is slipping through the cracks.

If you've got a concise sample project for this already built out, please submit it in a feedback and let us know if there's an answer!

Correct. An immersive space will take the device out of “multi-app productivity mode“ and into a “single app focus mode” of sorts. Perhaps you can create a Volume with a RealityView+attachment but you run the risk of the user rotating your window out of view. ”Billboarding” the attachment so it always faces the user could b disorienting. Also, Volumes do not scale the way windows do. If a user moves a window far from them, it gets bigger to maintain the same visual size. Volumes do not.

Unless the APIs change, this seems like a use case Apple does not want to entertain for 1.0. ”file feedbacks“, etc.