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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment