![]() I would draw my next Bline, set the width points to the Bline extremities, go into animation mode, move the time position several frames ahead, add a new keyframe, set the width point end points to “flat stop”, go back to the previous keyframe and position the ending “width point” position to zero. Let us say that I had drawn 2 or so Blines and I was on the 3rd keyframe. Your analysis is starting to ring some bells. I’ll try to fix that bug in the upcoming release (october probably). When I re-did the animation I just used the lock keyframe past only and I were careful to not produce any unneeded waypoint. In your case, to avoid that bug just use Linear interpolation (ToolBox->Default Interpolation widget->Linear) by default and those negative values won’t appear. Looks like those negtive values are not properly handled by the render routine and hangs Synfig Studio. So, for example, inner legs layer widhtpoint position, starts to move form ‘com Outline’ to ‘comp inner legs’ but there is a extra waypoint at ‘com Outline’ where the widthpoint’s position is zero too.ĭue to the nature of the TCB interpolation, the interpolation for a 0 -> 0 -> 1 values produce negative values between the travel from 0 to 0 (yes I know it is not what user expects see: viewtopic.php?f=14&t=1603) In particular there are 4 keyframes in your file: ![]() While you animated the second widthpoint position looks like you added some extra waypoints at the previous keyframes where the interpolation is being done. In your advanced outlines there are two widthpoints: one at start (stationery) and one that travels from the start to the end of the bline. I’m sorry for the inconveniences that this is producing. Try to handle it with a debugger to know who is causing the bad alloc.First, produce the same exception in one similar machine.It has to be related with the standard libraries. Obviously I need to catch the std exception and handle it properly.īad_alloc means that it has tried to setup a portion of memory and it couldn’t do it. Unhandled exception (type std:exception) in signal handler: The sync() procedure is under a try…catch handler so this is why the exception is thrown. Synfig error: Advanced Outline:: sync: Exception thrown Those messages are normal, they will appear every time an Advanced Outline is created. Synfig warning: Advanced Outline: WPList doesn’t accept new bline The sample file crashed here on this Windows Vista computer.ĭid it crash on Ubuntu 11.04? or did it work fine? I guess it crashed too.
0 Comments
Leave a Reply. |