Search Issue Tracker
Fixed in 2018.2.X
Won't Fix in 2018.1.X
Votes
0
Found in
2017.1.0b6
2017.3.0b11
Issue ID
973553
Regression
Yes
Inspector Debug mode allows ScriptableObject script to be changed to an incompatible script and stops drawing Inspector content
How to reproduce:
1. Open Unity
2. Load tester-submitted project
3. Create a new 'Scriptable Object Script' using context menu
4. Set inspector to 'Debug' mode
5. Change Scriptable Object Script (Switch between 'RegularScript.cs' and 'ScriptableObject.cs' until issue occurs. Usually takes about 1-2 attempts)
Expected result: Inspector shows error message prompting the user to specify a valid ScriptableObject derived script.
Actual result: Inspector stops rendering content for the selected project item.
Notes:
- May be triggered when either assigning and unassigning RegularScript.
Reproducible with - 2017.1.2p4, 2017.2.1f1, 2017.3.0f1, 2018.1.0a7
Not reproducible with - 5.6.4p4
Verified: 2018.2.0a4
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Add comment