Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
0
Found in
2018.4
2020.1.4f1
2020.2
Issue ID
1276574
Regression
No
Ctrl + Drag or Option + Drag on an asset with unsaved changes will copy an asset without the unsaved changes
How to reproduce:
1. Open user-submitted project (CopyAssetBug.zip)
2. Select BugMaterial.mat
3. Change something in the Inspector window(e.g. Metallic value)
4. CTRL + Drag(Windows) or Option + Drag(macOS) the Material to create a copy
5. Inspect the copy of the Material
Expected result: the Material copy is identical to the original
Actual result: the Material copy does not contain unsaved changes
Reproducible with: 2018.4.27f1, 2019.4.10f1, 2020.1.6f1, 2020.2.0a20
Not reproducible with: 2020.2.0a21, 2020.2.0b3
Notes:
Duplicating an asset via CTRL + D/CMD + D duplicates the material along with the unsaved changes
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
- [macOS] There is no way to tell if you are running under Rosetta
- [AssetImport] Changing Graphics APIs in Android platform reimports most of the assets (textures, fonts, ...)
- Stack frames are missing from Console window when in Full Stack trace mode
- An error is returned and no package is listed if an invalid package is hosted on a scoped registry
- Crash with ComputeTileMeshJob when generating Navmesh
Resolution Note (fix version 2020.1):
Fixed in 2020.1.11f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.14f1