Search Issue Tracker
By Design
Votes
0
Found in
2017.4.1f1
2018.3.0a1
2019.1.0a1
2019.2.0a1
2019.2.0b2
2019.3.0a1
Issue ID
1156495
Regression
Yes
ScriptedImporter Imported Assets cannot be edited in the Inspector when they have a CustomEditor
How to reproduce:
1. Open the attached "ScriptedImporterAssetsUneditable.zip"
2. Click on "asset.text"
3. Observe the Inspector
Expected Behaviour: The Inspector under "asset" imported Object are editable and not grayed out
Actual Behaviour: The Inspector under "asset" imported Object is grayer out and unresponsive
Reproducible with: 2017.4.1f1, 2017.4.27f1, 2018.4.1f1, 2019.1.4f1, 2019.2.0b4, 2019.3.0a4
Not reproducible with: 2017.4.0f1
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
Imported assets are immutable by definition. That they were editable prior to 2018.4 was a bug. See workaround below if it's a blocker for customers.