Search Issue Tracker
Won't Fix
Votes
4
Found in
5.5.0f3
Issue ID
873892
Regression
No
OnSceneGUI is not called in the Custom Editor class
Reproduction steps:
1. Open the attached project "SceneGUI.zip";
2. Open the Scene.unity;
3. Observe results in console;
4. Try to Disable/Enable the SceneGUITest object;
Expected results: The OnSceneGUI class will be called even with Custom Editor.
Actual results: The class is not called, only OnEnable/OnDisable classes are working.
Reproduced on: 5.3.6p6, 5.4.1f1. 5.5.0f3, 5.6.0b5, 2018.3.0a6.
-
huulong
Jul 28, 2021 19:01
If you have this issue, and noticed that loading default Layout or closing all inspectors and reopening one fixes the issue (like MARTINLB), please check the new issue which is more likely to get fixed (I provided more details and a sample of corrupted layout): https://issuetracker.unity3d.com/issues/onscenegui-is-not-being-called-when-using-a-certain-layout
-
martinlb
Jun 29, 2018 18:56
In my case this issue was solved by closing the additional inspector tab I had open. Everything started working again as soon as there was only a single inspector tab open.
-
martinlb
Jun 29, 2018 07:42
Still happening in 2018.1.3f1 on some computers.. even though they are running the same project..
-
matrem
Oct 09, 2017 11:21
I don't know if this is the same problem, but OnSceneGUI() seems not to be called when the edited object is disabled.
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
- Profiler - Taking you to the wrong section when using 'show'
- Draw Renderers custom pass doesn't work with SSGI
- WebCamTexture does not set the requested resolution when used in WebGL
- Editor default Stylesheet/Matching Selector buttons in Debugger don't do anything
- Graphics.DrawMeshNow stops rendering Render Texture after a few frames when viewed in the Player
Resolution Note:
We really appreciate your contribution to the Unity product. Thank you for reporting this issue. We take every case submitted to us seriously by investigating the impact on you, our customer, as well as the impact it may have on the engineering and experience of our product.
This particular case has been investigated thoroughly and we have decided, in the interests of protecting the stability and features of Unity for users that rely upon the affected versions, to not address this issue.