Maxon Developers Maxon Developers
    • Documentation
      • Cinema 4D Python API
      • Cinema 4D C++ API
      • Cineware 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

    Incorrect Evaluation

    SDK Help
    0
    2
    386
    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
      Helper
      last edited by

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

      On 22/12/2002 at 10:47, xxxxxxxx wrote:

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

      ---------
      I create a TP Velocity node and set the 'On' port to only evaluate the first frame. Subsequent frames still call my nodes for input ( of the speed and direction ports ) for evaluation, even though though Velocity node's 'On' port is set to false. Is there something in my nodes I am supposed to do to avoid being evaluated when the parent node is supposed to be in a non-evaluation state? ( if I disable the node the node does not evaluate of course ).
      darf

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

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

        On 30/12/2002 at 00:58, xxxxxxxx wrote:

        Without testing all possibilities I think this is how PVelocity is designed. It always evaluates its ports but just doesn't do anything with the particles if On is FALSE.
        So if the user wants to stop your node from evaluating he'll probably have to disable the whole PVelocity node or tell your node directly.

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