Search Issue Tracker
Active
Votes
0
Found in
6.5.0
6.4.2
6.3.5
5.2.2
Issue ID
UUM-138221
Regression
Yes
Using MoveCameraToWorldLocation will make offset planes from the AR Plane Manager
Steps to reproduce:
1. Open the attached user's project "TestVR.zip"
2. Switch to Android
3. Uncheck the "Move Position" property in the "Initializer" GameObject in the "Assets/Scenes/Main VR.unity" Scene
4. Setup space/environment on the Meta Quest device on the settings menu
5. Build to a Quest 3/3S device
6. The app will enable Camera Passthrough once started and a detected plane will be displayed (dotted texture)
7. Place a marker on the detected planes using the HMD (by looking at the dotted plane)
8. Go back to the Editor and toggle the "Move Position" property in the "Initializer" GameObject in the "Assets/Scenes/Main VR.unity" Scene
9. Build again and watch the marker placement on the detected plane
Expected result: All the detected planes are in the right place even after using MoveCameraToWorldLocation and the marker sprite matches the position of the planes
Actual result: After using MoveCameraToWorldLocation, all the detected plane locations are incorrect. The marker cannot be placed at the desired position because of the offset
Reproducible with: Meta OpenXR 2.3.0-pre.2, 2.3.0, 2.4.0-pre.1 (6000.0.62f1, 6000.2.12f1, 6000.3.0b10, 6000.4.0a4)
Not reproducible with: Meta OpenXR 2.2.1 (6000.0.62f1, 6000.2.12f1, 6000.3.0b10, 6000.4.0a4)
Environment tested: Windows 11 24H2
Reproducible with these devices:
VLNQA00644 - Oculus Quest 3S (Quest 3S), CPU: Google Tensor G2, GPU: Adreno 740, OS: 14
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
Add comment