PresentationComponent loses gaze targeting or dismisses in a volumetric window

Spatial Computing General
mesqueeb OP
Created 5h
Replies 2
Boosts 0
Views 31
Participants 2

On visionOS 26.6 and 27 latest beta:

PresentationComponent in a volumetric WindowGroup, when looking at the volume from a specific lower/back region create two bugs:

  • buttons inside the presentation have their gaze obstructed by hand presence, no button shows any hover highlight
  • hand movement in that specific area auto dismisses the presentation

The focused public repro uses a thin ModelEntity with InputTargetComponent and ordinary SwiftUI buttons. Its README includes two clearer videos: https://github.com/mesqueeb/PresentationAutoCloseInBackOfVolume

1. Gaze obstructed on buttons when hand is at specific location

(see "Test Action" has no hover highlight, even though i look at it)

2. Hover state restored on buttons when hand is gone

(see "Test Action" has hover highlight)

3. Presentation auto closed when hand comes back

The weirdest part:

This only happens at a specific location, when walking to the back of the volume, then turning around and interacting with the volume from the lower right back side.

Any workaround or fix guidance would be appreciated. Feedback Assistant: FB24569418.

Replies  2
Boosts  0
Views  31
Participants  2
Vision Pro Engineer OP
Apple
2h

@mesqueeb Thank you for your question! I was able to take a look on my end.

One issue that you may be having is that your hand is physically very close to both the menu (which has its own colliders for buttons and things) and also the collider on the box. When your hand gets very close to an input target, the system begins to expect a direct input (actually "touching" the button) rather than an indirect input (look and tap). When I tested your example project, I was able to reproduce the issue with the missing highlight by putting my hand very close to the menu, but if moved the volumetric window further away, I could no longer reproduce the highlight issue.

I would recommend two things:

  1. Try to allow your users to interact indirectly with menus further away.
  2. (more of a guess) Try placing more separation between the box collider and the presentation ui. For example, have it raised a little higher above the collider. This may alleviate some issues with undesired behavior when unintentionally interacting with a nearby collider.

You can check out our video from WWDC23 Design for spatial inputs to learn more about Apple's guidance for indirect vs direct input.

Let me know if that helps! Thank you very much for your feedback ticket, I'll make sure it is being seen by the right people.
mesqueeb OP
1h

@Vision Pro Engineer There is clearly something else going on. But I thought a better video is worth a thousand words.

I have made it extremely clear in this reproduction.

  • it happens even when far away from the presentation component as you can see now

please watch this 1 min video at https://github.com/mesqueeb/PresentationAutoCloseInBackOfVolume

The code used there is pushed to the github repo.

PresentationComponent loses gaze targeting or dismisses in a volumetric window
First post date Last post date
 
 
Q