Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2019.3.0a3
2019.3.0a12
Issue ID
1176833
Regression
Yes
EditorGUIUtility.GetBuiltinSkin() does not display the EditorSkin of the same type, that is currently used by the Editor
How to reproduce:
1. Open user-submitted project (BuiltinInspectorSkinError)
2. In the Hierarchy window select the 'SelectThis' GameObject
3. See the windows that pop up in the Scene View
Expected result: all 3 windows are displayed correctly
Actual result: one of the 3 windows does not display an EditorSkin
Reproducible with: 2019.3.0a3, 2019.3.0a12
Not reproducible with: 2017.4.31f1, 2018.4.7f1, 2019.1.14f1, 2019.2.1f1, 2019.3.0a2
Notes:
The EditorSkin that will not work correctly depends on the current Editor Theme:
- If Personal is used, EditorSkin.Inspector will be displayed incorrectly
- If Professional is used, EditorSkin.Scene will be displayed incorrectly
- If switching from one to another, both will be displayed incorrectly until the Editor is restarted
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Add comment