Search Issue Tracker
By Design
By Design in 5.0.X
Votes
0
Found in [Package]
5.0.0-pre.10
Issue ID
ARFB-33
Regression
No
AR Simulation detects planes that exceed geometry bounds
Summary
While using AR Simulation to navigate in Play mode in the PlaneOcclusion Samples scene, the walls occlude the checkered cubes as expected. However, the detected plane for the image marker cube is larger than its actual geometry. See the cubes indicated by red arrows in OversizePlane.png attached.
To See the Bug
Open the ARF Samples project in the Editor.
Open the PlaneOcclusion scene.
In Build settings, select desktop platforms.
Enable XR Simulation in Project settings.
In Scene view, use the AR Simulation overlay to select DefaultSimulationEnvironment.
Enter Play mode.
This scene includes a cube with the Simulation Image Marker component; it is scaled to look more like a quad.
Navigate in Game view so that the Image Marker cube is in view.
Click on the Image Marker cube.
This generates checkered cubes.
Navigate so that the edges of the Image Marker cube occlude some of the checkered cubes. The occlusion region extends beyond the Image Marker cube in some places. This is the bug.
Configuration
2021.3.0f1.2 (2021.3/staging 6eacc8284459)
MacOS 12.0.1, MacBook Pro (15-inch, 2019), 2.4 GHz 8-Core Intel Core i9
AR Foundation 5.0.0-pre.10 (f6569c5)
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
- Specular lighting visible in a camera with Path Tracing when Preserve specular lighting is disabled in observed material
- Cinemachine package throws CS1061 errors in the Console when installed in a project that has HDRP and URP installed
- Editor.log file size grows rapidly when a scene exceeds the "Maximum Shadow on Screen" limit setting in the HDRP Asset
- Player build freezes after calling Application.Quit() when the scripting backend is set to IL2CPP
- Texture is not applied on a Custom Render Texture when a Cubemap is selected as the texture
Resolution Note:
I verified that this behavior is adjustable via Project settings > XR Plug-in Management > XR Simulation > Plane Finding Params
Resolution Note (5.0.X):
I verified that this behavior is adjustable via Project settings > XR Plug-in Management > XR Simulation > Plane Finding Params