Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2020.3.X, 2021.1.X
Votes
0
Found in
2020.2.0a8
2020.2.1f1
2021.1
2021.2
Issue ID
1309768
Regression
Yes
Mouse selection in Physics Debugger prioritizes Mesh GameObjects over GameObjects with colliders
Reproduction steps:
1. Open user's project "PysicsSelectionTestProject.zip"
2. Open "SampleScene" Scene
3. In the Hierarchy window, notice how "3d object" has a child "physicsObject" that is a GameObject with Box Collider
4. Open Physics Debugger in Toolbar -> Window -> Analysis
5. In Scene View, make sure "Collisions Geometry" and "Mouse Select" are both enabled in Physics Debug
6. Angle the camera so that "physicsObject" is in front of "Cube"
7. Try selecting the "Cube" GameObject through "physicsObject"
Expected result: The "physicsObject" is selected first
Actual result: The "Cube" is selected first, ignoring the "physicsObject" in front of it
Reproducible with: 2020.2.0a8, 2020.2.3f1, 2021.1.0b4, 2021.2.0a3
Not reproducible with: 2018.4.31f1, 2019.4.19f1, 2020.2.0a7
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
- Objects near the screen edge are not culled when using GPU Occlusion Culling
- InvalidCastException is thrown when hovering over a Tilemap with a saved Random Brush pick containing empty cells
- [VisionOS] Animating a material property results in artifacts when the app mode is set to RealityKit and shader modifies the Vertex Shader
- "DirectoryNotFoundException" is thrown and Shader Graph does not open when opening a .shadegraph from a long path
- "Undo: Already found nextRootTransform, but with different state cached" error thrown when undoing changes made to the Hierarchy using a script
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0a8
Resolution Note (fix version 2021.1):
Fixed in 2021.1.3f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.3f1