Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2020.1.X
Votes
1
Found in
2020.1.0a7
2020.1.0b8
2020.2
Issue ID
1247409
Regression
Yes
[Scripting] NamespaceParser fails when ScriptableObject class is inside a custom namespace
How to reproduce:
1. Open user's attached project
2. Select the "Test" ScriptableObject in the Project window (Assets folder)
3. Observe the Inspector
4. Create a new ScriptableObject (Create -> Baz)
5. Select the new ScriptableObject and observe the Inspector
Expected result: Test.cs script is assigned in the Script property
Actual result: Test.cs script is not assigned in the Script property
Reproducible with: 2020.1.0a7 2020.1.0b9, 2020.2.0a11
Not reproducible with: 2017.4.40f1, 2018.4.23f1, 2019.3.14f1, 2020.1.0a6
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
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.0a13
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.0b11