Search Issue Tracker
By Design
Votes
0
Found in
2018.1.1f1
Issue ID
1051016
Regression
No
Values on a duplicated ScriptableObject aren't transferred from the previous one when they're added in a custom Inspector
Repro steps:
1. Open user attached project
2. Click on "New Scriptable Object Example" in the Project Window
3. Click "Add" a few times in the Inspector and assign any values
4. Duplicate "New Scriptable Object Example" by Ctrl+D (Command+D)
5. Observe the duplicated ScriptableObject in the Inspector
Expected: New ScriptableObject is created with values from the previous ScriptableObject
Actual: ScriptableObject is created with no values
Reproducible with: 2017.1.4p2, 2017.2.3p1, 2017.4.6f1, 2018.1.6f1, 2018.2.0b9, 2018.3.0a2
Notes:
- Reopening the project deletes all values previously added from all ScriptableObjects that were created through the Create Asset Menu
- If you add values on a duplicated ScriptableObject and duplicate the new one values are transferred correctly
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Multiple warnings are thrown when importing Terrain URP Demo Scene to the Project
- The Frame value field does not update when using the increment/decrement arrows in the Frame Debugger if the value has been manually inputted
- [Remote Config] PreparePayloadWithConfigType function is looking for camelCase property names, when the JSON objects are using PascalCase naming
- UI Builder Viewport's Tool Gizmo has deadzones
- SpriteShapes are rendered using multiple draw calls when the SRP Batcher determines their nodes are incompatible in a specific project
Add comment