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
    • Register
    • Login

    GetDirty in a generator hierarchy

    Scheduled Pinned Locked Moved SDK Help
    2 Posts 0 Posters 225 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 10/09/2005 at 06:19, xxxxxxxx wrote:

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

      ---------
      Hi,

      I have a generator hierarchy. Each generator level has 3 children, the first two are splines, and the third is the next generator level.

      Now I would like to check if there were changes made to the splines. For this I am using GetDirty(). But I also need the generator to update at each frame, so I have a tag that sets it dirty on each frame. This however also seems to affect the dirty state of the children and therefore GetDirty on the splines always returns TRUE.

      Is there a way to prevent this, still have my generator update and keep track of changes made to the splines?

      Thanks
      Katachi

      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 10/09/2005 at 09:34, xxxxxxxx wrote:

        ah forget about it. it was my fault. The problem lies somewhere else.

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