Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2020.2.0a4
Issue ID
1228030
Regression
No
References to ScriptableObject are lost when ScriptableObject is duplicated
Steps:
1. Open attached project
2. Select "Scriptable" ScriptableObject asset
==> It has two references to other ScriptableObject (Ref1 and Ref2)
3. Duplicate the Scriptable asset (Ctrl+D)
==> "Scriptable 1" asset is created and it also has references to Ref1 and Ref2
4. Double-click on Scriptable script and comment out both public references
==> References disappear from inspector
5. Take a look into files on disk
==> Both "Scriptable" and "Scriptable 1" has links to scriptable objects
6. Right-click in Project Browser and select "ReimportAll"
==>
"Scriptable 1" lost its links to scriptable objects (Ref1 and Ref2)
"Scriptable" still has those links in the file
Take a look into attached movie for details
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Initialization Mode" and "Update Mode" drop-downs are not localized in the Custom Render Texture asset
- Switching Graphics Default or DevLook Profile to “NightSkyRenderingSettings Profile” throws “KeyNotFoundException” error in the Console window
- Section separator renders in the wrong place in Search Journaling and Archetypes windows
- [D3D12][UWP] Additional persistent shadows are drawn in UWP builds when using D3D12
- Search Journaling window link to Journal Manager documentation isn’t working
Add comment