Copying and pasting in timeline makes things disappear
![Zantium](https://secure.gravatar.com/avatar/98230e6814a7e239e838768fd12858fb?&r=pg&s=100&d=https%3A%2F%2Fvanillicon.com%2F98230e6814a7e239e838768fd12858fb_100.png)
This is a very odd one! I have a couple of figues in DS v4.12 for which I've hand keyed animation for a few seconds. There are areas in the animation which I can repeat as a loop but if I copy that block of animation and paste it at the end of the animation, then parts or the whole of the figures just disappear or blink in and out of the animation - this also happens retrospectively, i.e. it affects the keyframes that I copied from earlier in the animation!
I've tried copying both figures together or frames from one at a time but the same issue persists. It's making it difficult to build an animation of any reasonable length if I can't take copy paste the loops.
Comments
Update: I've noticed that on the new keyframes themselves, all parts of the body are there. On in-between frames, parts of the body disappear.![surprise surprise](https://www.daz3d.com/forums/plugins/ckeditor/js/ckeditor/plugins/smiley/images/omg_smile.png)
It isn't keying the Visible property?
No, I've checked that as it was my first thought. There's no entry for that anywhere along those lines.
Other info;
Deleting the keys, removes the effect from the retrospective break of the source keys - but leaves the morph keys in (though I believe this has been identified as a bug an reported already).
It appears to be a timeline related issue, if I do the same copy paste in keyMate then it's not an issue, it works fine.
Since the original was a year ago, this may not be needed, but hopefully this could help others.
I had the same issue when working with poses in 4.16.0.3. When viewing the graph below the timeline with interpolations, they went way up and way down (seemingly to infinity). Selecting the keyframes and changing the interpolation set it back to normal in my scene. I was working with poses, rather than prebuilt animations, so your mileage may vary.
The last time I saw it, it happened when copying/pasting to multiple keyframes in the same timeline to keep the object in place (x,y,z translations). The interpolation graph looked like a giant sinewave over a few frames. Taking a wild guess about what's happening, is that it's trying to divide by a value change of zero somewhere when calculating the interpolation.