ARKit AnchorUpdate<ImageAnchor>.event Behavior Changes in visionOS 2.1

Spatial Computing ARKit
Caty OP
Created 1w
Replies 2
Boosts 0
Views 142
Participants 2

In visionOS beta, when using ARKit for image detection, the initially detected AnchorUpdate<ImageAnchor> status is .add, and subsequent detections of the same image are marked as .update. However, after toggling immersiveSpace, the same image is detected with the status .add again. After updating to visionOS 2.1, the first detection status remains `add, and subsequent detections of the same image remain .update, even after toggling immersiveSpace. Could this be due to a change in processing flow?

Replies  2
Boosts  0
Views  142
Participants  2
Vision Pro Engineer OP
Apple
6d

This sounds unexpected. It would be great if you could file a report via Feedback assistant, ideally with more information. E.g.:

  • Does this reproduce every time for you or just sometimes?
  • Have you ever observed this before visionOS 2.1?
0
Caty OP
5d

I would like to understand:

  1. In the case of image detection, is the first detection treated as .add and subsequent detections as .update, regardless of how many times ImmersiveSpace is enabled in between. Or is it
  2. Every time ImmersiveSpace is enabled, is the detection treated as a first-time detection .add (for the same image) Which of these is the expected or normal behavior?

The first scenario is a behavior I only noticed after updating to version 2.1. Initially, I had been designing the program based on the second scenario.

0
ARKit AnchorUpdate&lt;ImageAnchor&gt;.event Behavior Changes in visionOS 2.1
First post date Last post date
 
 
Q