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

    Python Effector: Full Control falloff issue

    Scheduled Pinned Locked Moved PYTHON Development
    3 Posts 0 Posters 236 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 12/09/2012 at 23:15, xxxxxxxx wrote:

      I've been fiddling with the Python Effector for a while, but I couldn't figure out this problem.
      If the Python Effector is set to Full Control , things work as intended when I start working. But when I go to the Falloff Tab and set the Falloff Shape to anything besides Infinite , things go wrong.
      Whatever I do, the falloff's center is always locked on the Cloner/Fracture/Matrix object's center.
      If I try using Source as its falloff shape, The falloff center point seems to move opposite the Effector's center instead of following the Source Link.
      Was something left out when the code for the Python Effector's falloffs was made? Do I have to code my own "Falloff Tab" just to get something that works?
      The falloff behavior in Parameter Mode is fine, but anything I code in is ignored unless it's a built-in element in the Parameter Tab, so I can't brute-force it that way.
      Tried this on R13 and on R14_Demo, same behavior on both.

      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 21/09/2012 at 13:01, xxxxxxxx wrote:

        did you try it with xpresso as an effector?
        try this 🙂 i'm pretty sure (like 99%) it will work
        just use the xpresso python node and xpresso falloff node...if u got the code i may see the problem

        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/2012 at 15:08, xxxxxxxx wrote:

          My goal is to use the Python Effector on its own, no jerry-rigging. COFFEE works fine, so it's the one I'd use instead of relying on XPresso to double the workload.
          The Python Effector Object itself is broken, even if you don't edit any of the code inside. Just add one into your scene right from the MoGraph menu, and set the mode to Full Control. Any Falloff Shape besides Infinite exhibits the same behavior.
          At the very least I'd want to override the default Effector Falloff function, but I don't know if it's even allowed to access it. I can't find anything inside the Python Documentation.

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