Thanks for looking into it, guys. Zapping the preffs was the first thing I tried, but good call tough Matt. I don't now what could be up with the scene, it was created with a fresh scene and only a null. Odd thing is, you can be working in a scene--simple or complex--everything will be going well, and boom, this kicks in and it is borked forever more. :-/
-=T=- On Sat, Sep 22, 2012 at 3:48 AM, Toonafish <[email protected]> wrote: > yep, there's definitely something fishy with this scene. > > > I can't reproduce the first problem of the key on frame 34 not responding > untill frame 35. > But when I try moving the null, it jumps back to the keyframed position > every time. Even when I create a new Null in the same scene, create some > keys, and set the curve to stepped, the same thing happens. > > Doing the same in a new scene works just fine. > > I don't have time to look into it much further today, just wanted to let > you know. > > - Ronald > > > On 9/22/2012 2:05 AM, Eric Turman wrote: > > In 2013 our animators are having a lot of strange issues For example, does > anyone else get this strange behavior? > you can download the file by clicking on the link: > > http://client.elementxcreative.com/public/tech/animate__keyframe-problem-between-frame_34-and_35.zip- > Size: 0.10 MB > > > - The FCurve editor was not messed with (keys were not moved in the > FCurve editor and the FCurve editor was set to auto snap to frames) > - We set a Key at 34, but you will notice that it will not update > until frame 35 where there are no keyframes > - any keys set after loading this file will be messed up > - even if you start a new scene after setting a few keyframes this bug > will kick in. > - only restarting Softimage will make setting keys work again > - Worse yet, if you move the null more than once. it will pop back to > the previous position. > > > The scene contains one null and the default camera--can't get much simpler > than that. I have completely disconnected from our workgroups and deleted > my user prefs and this still occurs. > Is anyone else having animation issues with 2013. > > > > -- > > > > > -=T=- > > > > -- -=T=-
