Search Issue Tracker
Fixed in 2022.1.X
Votes
3
Found in
2019.4
2020.1.0f1
2020.2
Issue ID
1265844
Regression
No
EditorUtility.CopySerialized fails when objects assigned to SerializeReference fields have different types
Reproduction steps:
1. Open attached project "CopySerialized.zip" and scene "SampleScene"
2. In Editor menu, click Bug -> Try CopySerialized
3. Observe Console window
Expected result: No error
Actual result: "Source and Destination Types do not match" error
Reproducible with: 2019.4.6f1, 2020.1.0f1, 2020.2.0a19
Could not test with: 2018.4.26f1 (console errors break project)
Comments (1)
-
Elfstone
Jul 28, 2020 12:25
Well, this really sucks. I've been trying out this new SerializeReference feature for some days (I didn't when it was still in Experimental), and have run into tons of problems. But this really is not acceptable.
How is this not still in .Experimental when simple CopySerialized won't work!? How could you release it?
If only I had known what to expect from Unity. I should've. I shouldn't even have started.
I am new in this, but look at what I've tried and suffered, not just Shader Graph, SerializeReference.
Asset Store offered solutions a hundred times better than Unity could. Is this your strategy now and ever?
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
- Sub-asset UI does not refresh when undoing Renderer Feature add or remove actions in a URP Renderer asset
- Scene flickers with a green tint when using Screen Space Ambient Occlusion and Contact Shadows with raytracing
- Scripts with null Components on GameObjects are not removed when calling GameObjectUtility.RemoveMonoBehavioursWithMissingScript
- Color Curve Key values remain visible after changing Curve type
- Selection highlight is drawn in an Animation Window when clicking in another Animation Window after highlighting items in the first one
Resolution Note (fix version 2022.1):
Fixed in 2022.2.0a3