Search Issue Tracker
Fixed in 2018.2.X
Votes
8
Found in
2018.2.0a4
2018.2.0f2
Issue ID
1061966
Regression
Yes
UnityException is thrown when calling EditorGUIUtility ObjectPicker methods from Custom Editor
How to reproduce:
1. Open the attached "Test1061966.zip" project's SampleScene
2. Select Test GameObject from the Hierarchy
3. Observe the Exceptions in the Console window
Expected result: no Exceptions are thrown when the GameObject is selected
Actual result: UnityException is thrown when the GameObject is selected
Reproducible with: 2018.2.0a4, 2018.2.0f2, 2018.3.0a5
Not reproducible with: 2017.1.5f1, 2017.2.3p2, 2017.4.7f1, 2018.1.9f1, 2018.2.0a3
Note: the issue occurs when calling EditorGUIUtility.GetObjectPickerControlID or EditorGUIUtility.GetObjectPickerObject
Update: fixed in 2018.2.13f1, 2018.3.0a11
Comments (4)
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
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
- Crash on GetOriginalSourceOrVariantRoot when creating a scene from a specific template
SimonDarksideJ
Aug 31, 2018 17:20
Still reproducible in 2018.2.6f1
Nothing reported in the release notes to backup this fix.
FloHal
Aug 31, 2018 17:14
Confirmed, still broken in 2018.2.6f1....
MMOARgames
Aug 31, 2018 16:56
Still broken in 2018.2.6f1
StephenHodgson-Valorem
Aug 24, 2018 16:38
Reproducable all the way up to 2018.2.5f1