Search Issue Tracker
By Design
Votes
1
Found in
6000.0.50f1
6000.1.4f1
6000.2.0b3
6000.3.0a1
Issue ID
UUM-107476
Regression
No
“GetAllOverlapping failed…” error when clicking a GameObject during a custom picking pass in the Scene view for the second time
Reproduction steps
1. Open the attached “IN-102642.zip” project
2. Open the “ReproduceBugScene” Scene
3. From the Hierarchy, locate the “WrongBehaviour” GameObject
4. In the Scene view, click on the “WrongBehaviour” GameObject
5. Observe no errors in the Console
6. Repeat the 4th step
7. Observe the Console
Expected result: No errors are thrown on subsequent clicks
Actual result: “GetAllOverlapping failed, could not ignore game object 'WrongBehaviour (UnityEngine.GameObject) (0)' when picking UnityEditor.EditorApplication:Internal_CallGlobalEventHandler ()” error is thrown
Reproducible with: 6000.0.50f1, 6000.1.4f1, 6000.2.0b3
Couldn’t test with: 2022.3.62f1 (Assets\PickingTest.cs(32,13): error CS0246:…)
Reproducible on: Windows 10 (User reported), Windows 11
Not reproducible on: No other environment tested
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:
The error is from is from incorrect usage in the user project. When using a custom picking pass, the user must check all pickable GameObjects against the exclude list of `RenderPickingArg`, but the for loop in `PickingTest.OnRenderPicking` is skipping the first game object. Furthermore, `PickingUtility.TryGetMeshAndMaterial` should call `gameObject.TryGetComponent` rather than `GetComponent` to avoid error messages when calling on a game object without these components.
Resolution Note:
Postpone for 7