For Softimage 2013, the issue is with anything that calls FCurve.SetKeys() in the SDK resulting in extreme (cumulative) slowdowns. This was fixed for 2014, but the bug shifted to a different part of the SDK causing the extreme slowdown when using 3rd party renderers such as Arnold. 2014 SP2 was released to fix that problem.
The most stable version of Softimage available right now is likely 2014 SP2. Matt From: [email protected] [mailto:[email protected]] On Behalf Of Jason S Sent: Tuesday, April 29, 2014 5:50 PM To: Morten Bartholdy; [email protected] Subject: Re: BUMP: fcurve editing extreme lag You can search this list, I can recall a whole discussion on the issue (2013), and I think there was either a workaround or a fix ( apart from uninstalling Arnold :) ) On 04/29/14 6:29, Morten Bartholdy wrote: I am going to bump this one - I am now experiencing serious lag when doing numerical editing of fcurves as well as most tool functions. No problem when editing manually, ie. moving multiple keys by hand. If memory serves me right, this is fairly new behavior, so I am suspecting some stupid win update has thrown me a curveball. I am guessing graphics problem either by driver version or aero settings, but have yet to get it sorted after various attempts. Does someone here know this problem and the specific fix? Win7 Geforce gtx 570 and driver version 320.18 Thanks Morten
