Fcurve editor extremely slow to update simple operations
I recall a thread some years ago of which I myself was part discussing why the fcurve editor in some cases got extremely slow at updating simple operations such as changing frame for selected keys on several curves at once, or for instance cycling several curves at once. I have forgotten what the solution was and can't seem to find that thread again - can someone perhaps jog my memory on this one? Cheers Morten
Re: Fcurve editor extremely slow to update simple operations
Hi, I know this sounds daft but I sort of remember it being to do with having a third party renderer installed! Cheers Lawrence > On 10 May 2015, at 11:07, Morten Bartholdy wrote: > > I recall a thread some years ago of which I myself was part discussing why > the fcurve editor in some cases got extremely slow at updating simple > operations such as changing frame for selected keys on several curves at > once, or for instance cycling several curves at once. I have forgotten what > the solution was and can't seem to find that thread again - can someone > perhaps jog my memory on this one? > > > Cheers > Morten >
Re: Fcurve editor extremely slow to update simple operations
That (the bug in Softimage related to third-party renderers) was a crash, not a slowdown: SOFT-8283 Softimage crashes when using the animation editor and 3rd party renderer SOFT-8283 was fixed in 2014 SP1 Then there was the extreme slowdown, fixed in 2014 SP2 SOFT-9089 Very slow access to the ICE attribute arrays On Sun, May 10, 2015 at 7:06 AM, Softimage wrote: > Hi, > I know this sounds daft but I sort of remember it being to do with having > a third party renderer installed! > > Cheers > Lawrence > > > > > On 10 May 2015, at 11:07, Morten Bartholdy wrote: > > > > I recall a thread some years ago of which I myself was part discussing > why the fcurve editor in some cases got extremely slow at updating simple > operations such as changing frame for selected keys on several curves at > once, or for instance cycling several curves at once. I have forgotten what > the solution was and can't seem to find that thread again - can someone > perhaps jog my memory on this one? > > > > > > Cheers > > Morten > > > >
RE: Fcurve editor extremely slow to update simple operations
IIRC the third party renderer problem was causing softimage to crash when using the animation editor. It was fixed in one of the SPs in version 2014. sven -Original Message- From: softimage-boun...@listproc.autodesk.com [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Softimage Sent: Sunday, May 10, 2015 1:07 PM To: Morten Bartholdy; softimage@listproc.autodesk.com Subject: Re: Fcurve editor extremely slow to update simple operations Hi, I know this sounds daft but I sort of remember it being to do with having a third party renderer installed! Cheers Lawrence > On 10 May 2015, at 11:07, Morten Bartholdy wrote: > > I recall a thread some years ago of which I myself was part discussing why the fcurve editor in some cases got extremely slow at updating simple operations such as changing frame for selected keys on several curves at once, or for instance cycling several curves at once. I have forgotten what the solution was and can't seem to find that thread again - can someone perhaps jog my memory on this one? > > > Cheers > Morten >
Re: Friday Flashback #223
I started in beta of Sumatra and Twister... its been one hell of a ride :) I am still using every day, even this fine Mother's Day Weekend. On Sat, May 9, 2015 at 6:48 PM, David Saber wrote: > I also started with 1.0 which was not production ready, too crashy. But > since 1.5 it was OK I.M.O. >
Re: Friday Flashback #223
Yeah, my first XSI, 4.2, great start, amazing software. 2015-05-10 14:46 GMT-03:00 Greg Punchatz : > I started in beta of Sumatra and Twister... its been one hell of a ride :) > I am still using every day, even this fine Mother's Day Weekend. > > On Sat, May 9, 2015 at 6:48 PM, David Saber wrote: > >> I also started with 1.0 which was not production ready, too crashy. But >> since 1.5 it was OK I.M.O. >> > > -- paulo-duarte.com
RE: Fcurve editor extremely slow to update simple operations
Try muting any "OnValueChanged" events in the Plug-in Manager's "Events" tab. Am 10.05.2015 13:49 schrieb "Sven Constable" : > IIRC the third party renderer problem was causing softimage to crash when > using the animation editor. It was fixed in one of the SPs in version 2014. > > sven > > -Original Message- > From: softimage-boun...@listproc.autodesk.com > [mailto:softimage-boun...@listproc.autodesk.com] On Behalf Of Softimage > Sent: Sunday, May 10, 2015 1:07 PM > To: Morten Bartholdy; softimage@listproc.autodesk.com > Subject: Re: Fcurve editor extremely slow to update simple operations > > Hi, > I know this sounds daft but I sort of remember it being to do with having a > third party renderer installed! > > Cheers > Lawrence > > > > > On 10 May 2015, at 11:07, Morten Bartholdy wrote: > > > > I recall a thread some years ago of which I myself was part discussing > why > the fcurve editor in some cases got extremely slow at updating simple > operations such as changing frame for selected keys on several curves at > once, or for instance cycling several curves at once. I have forgotten what > the solution was and can't seem to find that thread again - can someone > perhaps jog my memory on this one? > > > > > > Cheers > > Morten > > > >
