Quote: "Hi nex, if I understood your question correctly my answer would be the same - (recap)
what stops the animation data from being moved to the clone is that the optional parameter in his code was set to "1" (shared animation data)
now once the primary object is deleted then when the object that depended on it tries to access the animation data it simply no longer exists, but the pointer to it does and the result is that it gives you a little bit more grinding before it notifies you that its crashed.
so this is not really a bug, it works exactly the way it was supposed to from what I can see :"
I don't think you actually bothered to read my post at all. Why not just make one of the instances the new "master" when the master is deleted? No copying would be required beyond pointers to the animation data and a quick shuffle of the lists.
No crash, no overhead, just WORKING.
Athlon64 2.7gHz->OC 3.9gHz, 31C, MSi 9500GT->OC 1gHz core/2gHz memory, 48C, 4Gb DDR2 667, 500Gb Seagate + 80Gb Maxtor + 40Gb Maxtor = 620Gb, XP Home
Air cooled, total cost £160