Search Issue Tracker
Won't Fix
Votes
2
Found in
5.1.2f1
Issue ID
714362
Regression
No
Copying a layer from script throws pointer errors and deletes transitions
How to reproduce:
1. Open attached project
2. Open the New Animator Controller in the assets folder
3. Create a new layer in it
4. Add some states and transitions between states
5. Select Assets/Copy animator layer (or press Alt + T)
6. Select the New Animator Controller
7. Give the new layer any name
8. Press OK
- Note that the layers appear to be duplicated properly, however a few errors are thrown:
(metaFlags & kStrongPPtrMask) == 0
UnityEngine.Object:Instantiate(AnimatorStateMachine)
!(transfer.IsRemapPPtrTransfer() && SerializeTraits<FirstClass>::MightContainPPtr() && transfer.IsReadingPPtr())
UnityEngine.Object:Instantiate(AnimatorStateMachine)
9. Delete the newly created layer copy
- Note that the transitions in the original layer are gone as well
Comments (3)
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
- AI Assistant upgrade banner's `Open package Manager` link doesn't work
- 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
Malbers
Apr 26, 2017 17:06
Same Error in 5.6.0f3
Malbers
Apr 26, 2017 17:00
Error here for me too
Still giving :
!(transfer.IsRemapPPtrTransfer() && SerializeTraits<FirstClass>::MightContainPPtr() && transfer.IsReadingPPtr())
and:
(metaFlags & kStrongPPtrMask) == 0
UnityEngine.Object:Instantiate(AnimatorStateMachine)
ZeroSumGames
Aug 16, 2016 16:44
This issue can also sometimes prevent a proper instantiation of an animation controller from the Resources folder