Maxon Developers Maxon Developers
    • Documentation
      • Cinema 4D Python API
      • Cinema 4D C++ API
      • Cineware API
      • ZBrush Python API
      • ZBrush GoZ API
      • Code Examples on Github
    • Forum
    • Downloads
    • Support
      • Support Procedures
      • Registered Developer Program
      • Plugin IDs
      • Contact Us
    • Categories
      • Overview
      • News & Information
      • Cinema 4D SDK Support
      • Cineware SDK Support
      • ZBrush 4D SDK Support
      • Bugs
      • General Talk
    • Recent
    • Tags
    • Users
    • Login
    The Maxon SDK Team is currently short staffed due to the winter holidays. No forum support is being provided between 15/12/2025 and 5/1/2026. For details see Maxon SDK 2025 Winter Holidays.

    ModifyObject() and quick attribute changes

    Scheduled Pinned Locked Moved SDK Help
    3 Posts 0 Posters 290 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • H Offline
      Helper
      last edited by

      On 14/03/2013 at 18:42, xxxxxxxx wrote:

      User Information:
      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?

      1 Reply Last reply Reply Quote 0
      • H Offline
        Helper
        last edited by

        On 15/03/2013 at 08:11, xxxxxxxx wrote:

        Hi Robert,

        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.

        1 Reply Last reply Reply Quote 0
        • H Offline
          Helper
          last edited by

          On 18/03/2013 at 09:51, xxxxxxxx wrote:

          Hi Robert,

          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]

          1 Reply Last reply Reply Quote 0
          • First post
            Last post