Search Issue Tracker
By Design
Votes
1
Found in [Package]
4.1.0-preview.6
Issue ID
1266976
Regression
No
[AR Foundation] [Mobile] Tracked Image is placed too close to the camera
Reproduction steps:
1. Print or open "QRCode.jpg" in a device different from the one you will be testing
2. Open customer's attached project in "arfoundation-samples.zip"
3. Build the project for iOS and Deploy it to an iOS device
4. Select Image Tracking and allow Camera access if prompted
5. View/film the QR image with the Camera (on a piece of paper or phone)
6. Once the image is tracked a Game Object with the same image will be created above it
7. Place some Cubes directly on the QR code by tapping the Screen
8. Move the Camera around the QR and inspect the QR code's position
Expected result: QR code will not be seen because it is covered by cubes
Actual result: most of the time QR is really high in the vertical axis and is above the cubes
Reproducible with: AR Foundation 4.1.0-preview.6 (2019.4.7f1, 2020.2.0a20)
Could not test with 2018.4 because could not resolve package related errors
Devices tested (reproducible):
VLNQA00310 iPad Pro 12.9 1st gen (iOS 13.4.1)
OnePlus A5000, Android 10, Adreno 540, Snapdragon 835
Notes:
1. Some images are attached
2. A good way to notice where the image is placed to quickly change the camera's position
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
This is the expected behavior. The user must provide the correct physical dimensions for the image. If they do not match, then the resulting image is assumed to be either closer or farther from its actual position. See https://github.com/Unity-Technologies/arfoundation-samples/issues/568#issuecomment-693735111 for a complete explanation.