Search Issue Tracker
By Design
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2018.3.12f1
2019.1.0a1
2019.2.0a1
Issue ID
1146412
Regression
No
ScriptableObject instance Script field is 'None'when created out of ScriptableObject that isn't defined in file of the same name
How to reproduce:
1. Open the attached 'ScriptableObjectCreation.zip' project
2. Right-click in the project tab -> "Create" -> "Create TestData"
3. Select the new asset and observe the script's field
Expected result: "Script" field has attached file
Actual result: "Script" field shows as None (Mono Script)
Reproducible: 2017.4.26f1, 2018.3.13f1, 2019.1.0f2, 2019.2.0a12
Workaround: create C# script called "TestData" and then create "TestData" asset
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note:
This is by design. ScriptableObjects and MonoBehaviour have to be declared in a .cs file with the same filename as the class name.