Search Issue Tracker
Not Reproducible
Not Reproducible in 3.2.X
Votes
0
Found in [Package]
3.2.0-pre.1
Issue ID
XRIT-278
Regression
No
UI in World Space UI Sample Demo Scene doesn't work on Oculus Quest device
Steps to reproduce:
- Open the attached Unity project "OculusWorldUI" from provided Google Drive link
- Open "DemoScene" (Assets > Samples > XR Interaction Toolkit > 3.2.0-pre.1 > World Space UI)
- Enter the Play mode on Quest device
- Try interacting with XRI + UI Toolkit elements in the Scene
Actual results: Unable to interact with UI elements using Quest Controllers
Expected results: User is able to interact with UI elements using Quest Controllers
Reproducible with versions: 3.2.0-pre.1 / 6000.2.0b2 (d4c40f50eb81): 6000.2.0b2 (d4c40f50eb81) - unityhub://6000.2.0b2/d4c40f50eb81
Not Reproducible with versions: 6000.2.0b2 (2bdac9ac0d74) - unityhub://6000.2.0b2/2bdac9ac0d74
Tested on (OS): Windows 11
Reproducible with these devices: Oculus Quest (Quest), CPU: Snapdragon 835 MSM8998, GPU: Adreno 540, OS: 10
Notes:
- When adding XR Hands and trying to interact with the UI elements in the Scene also doesn't work
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
I have tried on Quest 2 and Quest 3 with an unmodified project and UI Toolkit works without an issue. I'm not sure if using a Quest 1 has anything to do with it, but I don't feel like it does. Either way, perhaps someone could try with a Quest 2 or 3 on your end?
Resolution Note (3.2.X):
I have tried on Quest 2 and Quest 3 with an unmodified project and UI Toolkit works without an issue. I'm not sure if using a Quest 1 has anything to do with it, but I don't feel like it does. Either way, perhaps someone could try with a Quest 2 or 3 on your end?