Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.2.0b5
Issue ID
1042480
Regression
No
OnSceneGUI isn't called for a game object when the inspector is locked on a different game object/asset
Repro steps:
1. Open user attached project "OnSceneGUINotCalled"
2. Open scene "SampleScene"
3. Select "Test Object" in the Hierarchy and observe the Scene View and the Console
4. Select "Main Camera" or "Directional Light" in the Hierarchy
5. Lock the Inspector Window
6. Reselect "Test Object" and observe the Scene View and the Console
Expected: Lines are drawn around the game object and "OnSceneGUI called" messages are generated in the Console
Actual: OnSceneGUI isn't called and no lines are drawn
Reproducible with: 2017.1.4f1, 2017.2.3p1, 2017.4.4f1, 2018.1.2f1, 2018.2.0b6
Notes: When you lock the inspector on the "Test Object" and select other game objects the lines are always drawn and OnSceneGUI is called constantly.
Comments (2)
-
rfcrocha
Sep 25, 2019 15:24
Just lost 3 hours of work because of this. Shame it won't be fixed since it really breaks the workflow.
-
Grosnus
Mar 26, 2019 09:10
It's a shame this issue won't be fixed since it breaks a lot of workflows with custom layouts and there seem to be no workaround for this.
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
- Inspector elements are rendered twice when the script component is added via drag-and-drop while the HideFlags.HideInInspector property is set
- Error "Light baking failed with error code 5 (Convergence data not available while rendering lightmaps)" thrown in Console when generating lighting for specific GameObjects
- Copy and Paste options for an Animation Property value are disabled in the Right click contextual menu
- Asset is not found when searching the Label "NewLabel" in Search Window
- "Compute dispatch: missing texture ID..." and "Compute dispatch: missing UAV ID..." warnings are thrown after changing the platform in High Definition 3D template
Resolution Note:
due to low priority, we decided that this issue won't be fixed.