Search Issue Tracker
By Design
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
- Rendering locks up when not looking at a transparent material on Meta Quest 2
- Volumetrics break when using a Custom Pass to create a Thickness Buffer for Alpha Clipping
- All tests are run instead of only the failed ones when the "Rerun Failed" button is pressed
- GameObject is not masked when the "Render PostProcessing Effects" pass executes with a resolved non-MSAA Color target and MSAA DepthStencil target
- [Android] Gfx.WaitForGfxCommandsFromMainThread high performance usage and inconsistency when built Player scene has Canvas GameObject on a specific Project
Resolution Note:
I verified that this behavior is adjustable via Project settings > XR Plug-in Management > XR Simulation > Plane Finding Params