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

    Bug in Py-RoundedTube Example

    Bugs
    0
    2
    871
    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

      On 10/11/2017 at 02:46, xxxxxxxx wrote:

      User Information:
      Cinema 4D Version:   n/a 
      Platform:   Windows  ;  Mac  ;  Mac OSX  ; 
      Language(s) :       PYTHON  ;

      ---------
      Hi,

      the "Py-RoundedTube" example has a bug in its static SetAxis method. It references a non existing variable 'i':

      Traceback (most recent call last) :
        File "'Py-RoundedTube.pyp'", line 310, in GetVirtualObjects
        File "'Py-RoundedTube.pyp'", line 40, in SetAxis
      NameError: global name 'i' is not defined

      It is easy to test by switching the axis orientation with the "Orientation" option in the attributes of a "Py-RoundedTube" object. It only works for "Y+". For all other variants the object simply disappears from the viewport.

      Noticed with the R16 SDK version, but the issues still seems to be present in the current version of the plugin on GitHub.

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

        On 13/11/2017 at 03:13, xxxxxxxx wrote:

        Hi,

        Thanks for reporting this important issue in Py-RoundedTube example.
        It will be fixed and the file on GitHub will be updated.

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