Search Issue Tracker
Fixed
Fixed in 2.2.1
Votes
1
Found in [Package]
2.2.0
Issue ID
XRMRT-102
Regression
No
Newly discovered planes ignore visibility toggle setting on Android XR
Steps to reproduce:
- Deploy MR Template to Android XR (see attached for APK).
- Look around to detect at least one plane.
- Use the wrist menu to disable plane visibility.
- Planes vanish; this is good.
- Look around to detect at least one more plane.
Actual results:
Newly detected planes appear, despite visibility being toggled off.
Expected results:
Newly discovered planes should not appear until visibility is toggled back on.
Reproducible with versions:
MR Template 2.2.1 and earlier.
Not reproducible with versions:
Can’t test with versions:
Tested on (OS):
Quest, Android XR.
Notes:
- Previously we saw this issue with the AR Template.
- Does not occur on Quest because Meta does not allow live-updates for planes or bounding boxes after load; they are done during Space Setup only.
- Android XR does live-updates for planes, which MR Template didn't account for.
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:
Fixed live plane and bounding box detection on Android XR devices. Now planes and bounding boxes will show or hide correctly based on visibility settings in the hand menu.