On 14/03/2013 at 18:42, xxxxxxxx wrote:
Cinema 4D Version: R12
Platform: Windows ; Mac OSX ;
Language(s) : C++ ;
My deformer object plugin does quite a bit of work every time that ModifyObject() is called. I've cached information that hasn't changed between invocations. Still, if the user (in this case, me testing) changes several attributes of the deformer, deformed, or object being used to deform quickly enough, my plugin typically crashes. Too me, this appears as if the ModifyObject() process is being aborted too soon if the user moves quickly - but I am uncertain as to the reasons.
For instance, if I have a cube object and change the Segments X/Y/Z fast enough, I imagine that either ModifyObject() is being called again while still processing or it aborts and gets called again with corrupted (incomplete) data. Then Cinema 4D is crashed.
How do I avoid this?
On 15/03/2013 at 08:11, xxxxxxxx wrote:
Are you experiencing these crashes under R12 only?
Have you tested this on latest versions R13 and R14?
The behavior you describe looks really strange, I'll contact the developers.
On 18/03/2013 at 09:51, xxxxxxxx wrote:
It sounds like you're storing/caching some direct pointer to scene data internally.
Like your other problem with deformer and rotation, you can send us your code to [email protected]