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
    • Unread
    • Recent
    • Tags
    • Users
    • Login

    Plugin deformers & Point Editing Crashes

    Scheduled Pinned Locked Moved SDK Help
    4 Posts 0 Posters 334 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

      THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

      On 28/09/2006 at 02:59, xxxxxxxx wrote:

      User Information:
      Cinema 4D Version:   9.102 
      Platform:   Windows  ;   Mac OSX  ; 
      Language(s) :     C++  ;

      ---------
      My plugin suite uses a plugin hierarchy deformer to deform the root polygon mesh. It seems that when editing the mesh points/edges/polygons, there is a chance of crashing C4D. The crash occurs in ModifyObject(). I've checked (and rechecked, twice) and there is not one memory pointer that isn't accounted for, even the arguments are checked. There are only three methods called during the process (when editing) : Draw(), CheckDirty(), and ModifyObject().

      When and how it occurs is not reproducable so far. Sometimes it's just moving the points, sometimes it's the undo after moving them, sometimes it's the moving after undoing a move. Sometimes it happens right away, sometimes it doesn't happen at all.

      Any ideas, suggestions, caveats?

      Thanks,

      Robert

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

        THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

        On 28/09/2006 at 07:02, xxxxxxxx wrote:

        Howdy,

        Well, I don't know if this applies, but is the polygon mesh also in a HyperNURBS?

        I had some trouble with getting proper point count when the object was in a HyperNURBS, it was unpredictable because sometimes the point count of the HyperNURBS object would be returned. So, then as I looped through the points array's indeces it would get to the end of the points array, but still try to keep going, and you know for sure it would crash then.

        It has something to do with the timing of when GetPointCount() is called. Or, something like that. Here's the thread I posted:
        http://www.plugincafe.com/forum/display_topic_threads.asp?ForumID=4&TopicID;=2259&SearchPagePosition;=1&search;=GetPointCount&searchMode;=allwords&searchIn;=Thread&forum;=4&searchSort;=dateDESC&ReturnPage;=Search

        Adios,
        Cactus Dan

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

          THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

          On 28/09/2006 at 19:59, xxxxxxxx wrote:

          Hey Dan,

          Definitely not related to HN. It happens with just the base Polygon object - as long as my hierarchy modifier bones are underneath. Still cannot reproduce a single instance - it just occurs at random some time, some place during editing or undoing. If the hierarchy is moved out from underneath the Polygon object, it never crashes.

          Thanks,

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

            THE POST BELOW IS MORE THAN 5 YEARS OLD. RELATED SUPPORT INFORMATION MIGHT BE OUTDATED OR DEPRECATED

            On 29/09/2006 at 15:10, xxxxxxxx wrote:

            :Bump: this one too.

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