Search Issue Tracker
Third Party Issue
Third Party Issue in 2.0.X
Votes
0
Found in [Package]
2.0.0-pre.11
Issue ID
AVPB-801
Regression
No
[PolySpatial] Billboard component prevent from manipulating uGUI when billboard becomes flat horizontally
Reproduction steps:
1. Open the attached “Polyspatial2_0_Test“ project
2. Open the “Assets/Scenes/MR_BillboardSample.unity“ Scene
3. Play with “Play To Device” or Build & Install app to Apple Vision Pro
4. Move your body and look down at the UI
5. Then please try to manipulate uGUI components
Expected result: uGUI components can be manibulated/interacted with
Actual result: uGUI doesn’t respond
Reproducible with: 2.0.4 (6000.0.26f1)
Reproducible on: Apple Vision Pro device (reported by User), visionOS 2.2 Simulator
Not reproducible on: No other environment tested
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Context menu item checkmark updates only after reopening twice when using Menu.SetChecked on component context menu items
- Long Property names are not truncated in the Add Property dropdown in the Animation window when the Long Property name does not fit
- [iOS] High CPU load when device keyboard is open
- Selected Animation clip in the Animation window changes when the Domain Reload is triggered
- Animation window scrollbar keeps resetting when the scrollbar width is changed after adding an event
Resolution Note:
The billboard component directly exposes the capabilities of the RealityKit billboard component, and as such is limited purely to orienting visual content, not input.
In order to orient for input, users must first use a mode that exposes head position (eg. an immersive/unbounded space) then manually orient both the visual elements and corresponding colliders toward the user manually.
Resolution Note (2.0.X):
The billboard component directly exposes the capabilities of the RealityKit billboard component, and as such is limited purely to orienting visual content, not input.
In order to orient for input, users must first use a mode that exposes head position (eg. an immersive/unbounded space) then manually orient both the visual elements and corresponding colliders toward the user manually.