Correct. You can place your own plane, give it a collision shape, and use that to test for the time being.

As VisionOS is not yet a "Released" OS, it is not available in the non-beta versions of Xcode. Like the other poster said, you need to open up a beta version like the release notes say.

I believe you can generate a collision Shape from a mesh. Thats the recommendation for creating entities when using a SceneReconstruction provider, for example. See the raycasting portion ARKit and spatial computing WWDC video for slightly more.

All I know is that you won’t be able to use “hover” states to detect if the users eyes are actually resting on ad content. Other than that I have not heard of any limitations. I‘m looking forward to apps that can put black squares over billboards in real life. :D

I think searching with skybox may help you find your answer, but I’ve never personally done this.

Same problem. Would love to know the right way to implement this pattern with @observable

Yeah, I get the same behavior. There are a few posts here of others finding the same behavior too. I think you can only get location information relative to the AnchorEntity’s origin from that entity and its children. In addition, AnchorEntities and their children cannot behave in physics based interactions outside of that anchors hierarchy and that includes ray casting. I’ve been endeavoring to never use an AnchorEntoty because of these limitations. Thankfully the plane provider that works on device doesn’t require those entities or else I would be sunk.

Vision OS does not expose the location a user is looking via the API.

I could be wrong, but if something is positioned between the limb and the headset, I don’t think it should be occluded. I did not hear back about debits, though, so I don’t know for sure.

I believe the “update” method of your RealityView will fire when your entity appears in the scene. You could check the .scene property of your entity at that time and observe it is non-nil.

I would also like the option to purchase a cable-connector for Vision Pro so I can avoid problems associated with wireless debugging.

@eskimo This is likely to remain a more annoying problem on Vision Pro where binary sizes could be larger and there is no hardware connection on the consumer device. What's the right feedback categorization for requesting a purchasable connector?

You can anchor to the head targeted AnchorEntity, which tracks the user’s head. However some users, for accessibility reasons, rely on head movements to interact with items. You should provide an alternative when those flags are true.

You can deploy and debug wirelessly. The dongle is available for developers of applications with large assets, unstable WiFi, or corporate network policies.

For loops are not a valid means of constructing a repeated sequence of views. You'll want to use the SwiftUI view named "ForEach". https://developer.apple.com/documentation/swiftui/foreach