as noted, we have had lots of issues with this, but if we strip an offending scene down to just an animated null/root, the unwanted behaviour ceases
this makes it VERY difficult to send a low complexity scene to support for repro having already lost PLENTY of production time to this bug, we can't justify MORE time spent trying to create a repro scene at our expense a _____ From: [email protected] [mailto:[email protected]] On Behalf Of Steven Caron Sent: 05 February 2013 05:41 To: [email protected] Subject: Re: Fcurve editor crashing soft fyi, i animate regularly, have arnold loaded, and haven't experienced this. it must be very specific data set that causes it On Mon, Feb 4, 2013 at 9:35 PM, Enrique Caballero <[email protected]> wrote: This is great to know. I am now disconnecting Arnold from our Animation WG. I had it in there due to Laziness On Mon, Feb 4, 2013 at 11:53 PM, Stefano Jannuzzo <[email protected]> wrote: In SItoA, most of the ipr events are managed through the dirty list. Since it's not perfect, we manage some through the OnValueChange event. Can you guys test after disabling the event in the plugin manager? On Mon, Feb 4, 2013 at 4:24 PM, Kamen Lilov <[email protected]> wrote: On 2/2/2013 2:26 AM, Stefan Kubicek wrote: Just wildly guessing here but since renderers need to update e.g. the Render Region when values are changed in the scene, which sometimes fails when the built-in mechanisms are used, I suspect both Vray and Arnold are making heavy use of some custom OnValueChanged events. Maybe this could cause problems when used excessively and/or or with deep hierarchies? Can't speak for Arnold, but yes, VRay does rely heavily on OnValueChanged. Hope this helps the dev folks at Autodesk _____ No virus found in this message. Checked by AVG - www.avg.com Version: 2012.0.2238 / Virus Database: 2639/5582 - Release Date: 02/04/13
