@FrankZielen Hmm, Yeah addChild should work for that. Content.add will add the attachment View relative to the 0,0,0 position of the realityView. If you add it to a parent entity it will be added relative to the 0,0,0 position of that entity. Is it possible its inside the parent entity?

I suspect Apple may keep those tools locked down to prevent Unreal from gaining tractions on the platform.

Are Apple employees allowed to file feedbacks on behalf of the community?

I am going to mark this as the accepted answer. While I don’t like needing to place and manage my own Collision-enabled Entities, it enables both a SpatialTapGesture and raycast solution.

I was hoping there was a way that did not involve manually creating and managing plane collision shapes as the PlaneAnchors change size and location. Also, I think if I did manage my own collision shapes, I could use a simpler TapGesture to detect the tap and 3D location of the tap instead of using a recast.

" For example, data about the other personas (outside of their immersion status) is not exposed via APIs. I am guessing this is for privacy reasons (?)." Could each persona share it's world anchor and keep it updated within the SharePlay session?

Only work around I could think of was requesting a dev kit. iOS and VisionOS have enough differences with ARKit, that I'm not sure it's worth it for me to deal with that for a hobby project. If I don't get a dev kit, or the simulator doesn't get updated, I'm probably SOL for a few years.

I will also add that despite Vision Pro being designed to not keep the user isolated from the world around them, shareplay experiences don’t seem to consider users as being in the same space. I’d bet it’s being saved as a 2.0 thing. Shareplay this year even feels like a 2.0 version of multipeersharing.

I don't have experience with Maya blend shapes, but I've manipulated Blender armature components programmatically, and you can do so through a Model's joint transforms.

lol! Yes! So much nicer

That I don’t know and I don’t think I have a use case where a window would need to not open in front of the user, either. if you need an accessory window, maybe try a custom ornament view?

I’ve observed that opening a window with a matching value and ID does not bring a window to the front on VisionOS and instead makes a new window

@ZeTof If this works for you, please mark this as an answer so people outside this post know to visit.

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

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.