Search Issue Tracker
By Design
Votes
0
Found in [Package]
4.2.2
Issue ID
1388163
Regression
No
ARPlanes stop detecting clicks after pausing and unpausing
Reproduction steps:
1. Open attached project "arfoundation-samples-main"
2. Build and Run
3. In the app, click on the "Simple AR" button and allow camera permissions
4. Look around the room until you find an orange plane and click on it to create a cube
5. Click the Pause button on the bottom of the screen and wait until the screen turns black
6. Click the Resume button and click on the same plane with the cube on it
Expected result: The click is detected and a new cube is created
Actual result: The click is not detected and a new cube is not created
Reproducible with: 4.2.0-pre.7, 4.2.2 (2020.3.27f1, 2021.1.28f1, 2021.2.10f1, 2022.1.0b5, 2022.2.0a3)
Could not test with: 4.2.2 (2019.4.35f1 - Editor not responsive), 4.2.0-pre.6 (Compilation errors), 5.0.0-pre.5 (Compilation errors)
Compilation errors I am getting:
Assets/Scripts/MakeAppearOnPlane.cs(43,37): error CS1061: 'ARSessionOrigin' does not contain a definition for 'MakeContentAppearAt' and no accessible extension method 'MakeContentAppearAt' accepting a first argument of type 'ARSessionOrigin' could be found (are you missing a using directive or an assembly reference?)
Reproducible with these devices:
VLNQA00321 - Xiaomi MI 9 (MI 9), OS: 10.0.0, CPU: Snapdragon 855 SM8150, GPU: Adreno 640
VLNQA00414 - Galaxy Note10+ 5G (SM-N976V), OS: 9, CPU: Snapdragon 855 SM8150, GPU: Adreno 640
VLNQA00331 - HUAWEI P20 lite (ANE-LX1), OS: 9, CPU: HiSilicon Kirin 659, GPU: Mali-T830
VLNQA00122 - Samsung Galaxy S9 (SM-G960F), OS: 10.0.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72
Note: It's not 100% reproducible, sometimes you have to pause and unpause a couple of times, for the best results, don't turn away from the plane when pausing and unpausing
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
- GPU utilization increases by 20% on Meta Quest headsets when Render Graph is enabled on 6000.0.16f1 and higher
- Value on Slider (Int) control in UI Builder displays as default when saving UI Document
- Color mismatch in UI Builders Library panel when the Editors theme is set to Light Mode
- [Android ] "AndroidJNI.ToBooleanArray" returns a random non-zero value instead of "IntPtr.Zero" when the method argument is null
- Non-HDR color picker opens when selecting material color with HDR enabled
Resolution Note:
On further inspection, AR Foundation is working as expected. The behavior of planes between iOS and Android is different. The strange behavior that the user is observing has to do with the fact that the planes are in TrackingState.Limited when resuming the ARSession. In ARCore, planes that are in TrackingState.Limited are not raycastable. In order to avoid this confusion in the future, I have added a script for clarity that highlights planes red when they are in TrackingState.Limited in ARFoundation samples SimpleAR scene, with some information added to the README. This will be available in the next releases of AR Foundation samples.