Python SDK Examples for Cinema 4D 2025.0.0

Author: mxn-ferdinand

plugins/py-double_circle_r19/py-double_circle_r19.pyp

@@ -332,15 +332,15 @@ class DoubleCircleData(c4d.plugins.ObjectData, DoubleCircleHelper):
 
         # Defines the color of the handle according of the hovered state of the object.
         hoverColor = c4d.VIEWCOLOR_ACTIVEPOINT if hitId != 0 else c4d.VIEWCOLOR_SELECTION_PREVIEW
-        bd.SetPen(c4d.GetViewColor(hoverColor))
+        bd.SetPen(c4d.GetViewColor(hoverColor), 0)
 
         # Retrieves the information of the current handle.
         info = c4d.HandleInfo()
         self.GetHandle(op, 0, info)
 
         # Draw the handle to the correct position
         bd.DrawHandle(info.position, c4d.DRAWHANDLE_BIG, 0)
-        bd.SetPen(c4d.GetViewColor(c4d.VIEWCOLOR_ACTIVEPOINT))
+        bd.SetPen(c4d.GetViewColor(c4d.VIEWCOLOR_ACTIVEPOINT), 0)
         bd.DrawLine(info.position, c4d.Vector(0), 0)
 
         return c4d.DRAWRESULT_OK

plugins/py-noise_falloff_r14/py-noise_falloff_r14.pyp

@@ -70,7 +70,7 @@ class NoiseFalloffHelper(object):
         """
 
         # Defines the Draw Color
-        bd.SetPen(c4d.GetViewColor(c4d.VIEWCOLOR_ACTIVEPOINT))
+        bd.SetPen(c4d.GetViewColor(c4d.VIEWCOLOR_ACTIVEPOINT), 0)
 
         # According the handle id, defines start/end of the line handle
         p1, p2, p3, p4 = c4d.Vector(), c4d.Vector(), c4d.Vector(), c4d.Vector()

plugins/py-ocio_node_2025/py-ocio_node_2025.pyp

@@ -0,0 +1,16 @@
+#ifndef C4D_SYMBOLS_H__
+#define C4D_SYMBOLS_H__
+
+enum
+{
+	// Plugin IDs
+	PID_OCIO_NODE_2025 = 1064267,
+
+	// String IDs
+	IDS_NME_OCIO_NODE_2025  = 10000,
+
+	// End of symbol definition
+	_DUMMY_ELEMENT_
+};
+
+#endif //C4D_SYMBOLS_H__

plugins/py-ocio_node_2025/res/c4d_symbols.h

@@ -0,0 +1,9 @@
+#ifndef OOCIONODE2025_H__
+#define OOCIONODE2025_H__
+
+enum
+{
+  OCIO_NODE_2025_COLOR = 1000,
+};
+
+#endif // OOCIONODE2025_H__

plugins/py-ocio_node_2025/res/description/oocionode2025.h

@@ -0,0 +1,10 @@
+CONTAINER Oocionode2025
+{
+  NAME Oocionode2025;
+  INCLUDE Obase;
+
+  GROUP ID_OBJECTPROPERTIES
+  {
+    COLOR OCIO_NODE_2025_COLOR {}
+  }
+}

plugins/py-ocio_node_2025/res/description/oocionode2025.res

@@ -0,0 +1,4 @@
+STRINGTABLE
+{
+    IDS_NME_OCIO_NODE_2025              "Python SDK: Ocio Node 2025";
+}

plugins/py-ocio_node_2025/res/strings_en-US/c4d_strings.str

@@ -0,0 +1,5 @@
+STRINGTABLE Oocionode2025
+{
+  Oocionode2025              "Ocio Node 2025";
+  OCIO_NODE_2025_COLOR       "Color";
+}

plugins/py-ocio_node_2025/res/strings_en-US/description/oocionode2025.str

@@ -388,7 +388,7 @@ class RoundedTube(c4d.plugins.ObjectData, RoundedTubeHelper):
             # Defines the color of the handle according of the hovered state of the object.
             handleColorFlag = c4d.VIEWCOLOR_HANDLES if c4d.GetC4DVersion() >= 21000 else c4d.VIEWCOLOR_ACTIVEPOINT
             hoverColor = c4d.VIEWCOLOR_SELECTION_PREVIEW if hitId == i else handleColorFlag
-            bd.SetPen(c4d.GetViewColor(hoverColor))
+            bd.SetPen(c4d.GetViewColor(hoverColor), 0)
 
             # Retrieves the information of the current handle.
             info = c4d.HandleInfo()
@@ -398,7 +398,7 @@ class RoundedTube(c4d.plugins.ObjectData, RoundedTubeHelper):
             bd.DrawHandle(info.position, c4d.DRAWHANDLE_BIG, 0)
 
             # Sets the color back to normal before drawing lines
-            bd.SetPen(c4d.GetViewColor(handleColorFlag))
+            bd.SetPen(c4d.GetViewColor(handleColorFlag), 0)
 
             # Draws the lines 0, 1, 2 are draw in the same drawcall
             if i == 0:

plugins/py-rounded_tube_r13/py-rounded_tube_r13.pyp

@@ -346,7 +346,7 @@ class SpherifyModifier(c4d.plugins.ObjectData):
                     return c4d.DRAWRESULT_FAILURE
 
             # Retrieves the object color
-            bd.SetPen(bd.GetObjectColor(bh, op))
+            bd.SetPen(bd.GetObjectColor(bh, op), c4d.SET_PEN_USE_PROFILE_COLOR)
             bd.SetMatrix_Matrix(None, c4d.Matrix())
 
             # Defines the scale/rotation where drawing will operate by the radius of the generator
@@ -389,7 +389,7 @@ class SpherifyModifier(c4d.plugins.ObjectData):
             for i in range(SpherifyModifier.HANDLECOUNT):
                 # Defines the color of the handle according of the hovered state of the object.
                 hoverColor = c4d.VIEWCOLOR_ACTIVEPOINT if hitId != i else c4d.VIEWCOLOR_SELECTION_PREVIEW
-                bd.SetPen(c4d.GetViewColor(hoverColor))
+                bd.SetPen(c4d.GetViewColor(hoverColor), 0)
 
                 # Retrieves the information of the current handle.
                 info = c4d.HandleInfo()
@@ -399,7 +399,7 @@ class SpherifyModifier(c4d.plugins.ObjectData):
                 bd.DrawHandle(info.position, c4d.DRAWHANDLE_BIG, 0)
 
             # Draw the line to the second Handle
-            bd.SetPen(c4d.GetViewColor(c4d.VIEWCOLOR_ACTIVEPOINT))
+            bd.SetPen(c4d.GetViewColor(c4d.VIEWCOLOR_ACTIVEPOINT), 0)
             bd.DrawLine(info.position, c4d.Vector(0), 0)
 
         # If the current draw pass is not the object or handle, skip this Draw Call.

plugins/py-spherify_modifier_r13/py-spherify_modifier_r13.pyp

@@ -1,11 +1,11 @@
 # Foundations
 
-The classic API and MAXON API provides various fundamental concepts and classes.
+The Cinema API and MAXON API provides various fundamental concepts and classes.
 
 Classic API:
-- **c4d.C4DAtom**: *Base class for many entities in the classic Cinema 4D API.*
+- **c4d.C4DAtom**: *Base class for many entities in the Cinema API.*
 - **c4d.GeListNode**: *Based on C4DAtom, provides the functionality to organize elements in linked lists and trees.*
-- **c4d.BaseList2D**: *Based on C4DAtom and GeListNode. It is a base class for many entities of the classic Cinema 4D API.*
+- **c4d.BaseList2D**: *Based on C4DAtom and GeListNode. It is a base class for many entities of the Cinema API.*
 - **c4d.GeListHead**: *A GeListHead object is the root of a list or tree of GeListNode elements.*
 - **c4d.DescID**: *Parameters of C4DAtom based elements are identified using a DescID object.*
 

scenes/py_generator_binary_kite_2025.c4d

@@ -28,7 +28,7 @@ def main():
         dataDict[key] = value
 
     # However, only the most atomic Python types as string, int, float, and bool are being
-    # automatically converted to their maxon API equivalent. For storing a list of integer values 
+    # automatically converted to their Maxon API equivalent. For storing a list of integer values 
     # under a key for example, one must convert that list explicitly to a BaseArray.
     dataDict["prime_numbers"] = maxon.BaseArray(maxon.Int32, [2, 3, 5, 7, 11, 13])
 

scripts/01_foundations/readme.md

@@ -1,6 +1,6 @@
 # Data & Algorithms
 
-Both the classic API and the MAXON API provide simple and complex data types, data structures and basic algorithms.
+Both the Cinema API and the MAXON API provide simple and complex data types, data structures and basic algorithms.
 
 It is advised to always use these data types instead of basic data types or standard library structures. Using the provided data types ensures compatibility with all supported platforms.
 

scripts/02_data_algorithms/maxon_datadictionary_2023_1.py

@@ -1,6 +1,6 @@
 # Files Medias
 
-The classic API and MAXON API provide tools and classes to handle file and media data. If possible, the classes of the MAXON API should be preferred.
+The Cinema API and MAXON API provide tools and classes to handle file and media data. If possible, the classes of the MAXON API should be preferred.
 
 Classic API:
 - **c4d.bitmaps.BaseBitmap**: *The bitmap class can be used to load, read, draw and save bitmap pictures of various formats.*

scripts/02_data_algorithms/readme.md

@@ -6,7 +6,7 @@ The Cinema 4D GUI is based on "dialog" windows based on the GeDialog class. A pl
 
 ## Content
 
-The classic API as well as the MAXON API provide generic application development components to handle threads, files, GUI elements etc.
+The Cinema API as well as the MAXON API provide generic application development components to handle threads, files, GUI elements etc.
 
 * **description**: *Stores information on how parameters are to be displayed in the GUI (Attribute Manager).*
 

scripts/03_application_development/files_media/readme.md

@@ -2,11 +2,11 @@
 
 ## Introduction
 
-The classic API as well as the MAXON API provide generic application development components to handle threads, files, GUI elements etc.
+The Cinema API as well as the MAXON API provide generic application development components to handle threads, files, GUI elements etc.
 
 ## Content
 
-* **files_media**: *The classic API and MAXON API provide tools and classes to handle file and media data. If possible, the classes of the MAXON API should be preferred.*
+* **files_media**: *The Cinema API and MAXON API provide tools and classes to handle file and media data. If possible, the classes of the MAXON API should be preferred.*
 
 * **gui**: *The Cinema 4D GUI is based on "dialog" windows based on the GeDialog class. A plugin can create custom dialog windows for user interaction or creates new managers.*
 

scripts/03_application_development/gui/readme.md

@@ -3,10 +3,10 @@
 Cinema 4D is a multi-threaded application that handles different tasks in different threads. Certain operations can only be performed from within the main thread.
 So a plugin must know its current thread context.
 
-Both the classic API and the MAXON API provide tools to handle threads, create custom threads to perform multi-threaded operations.
+Both the Cinema API and the MAXON API provide tools to handle threads, create custom threads to perform multi-threaded operations.
 
 Classic API:
-- **c4d.threading.C4DThread**: *The base class for custom classic threads in Cinema 4D. Operations can be done on multiple cores or in the background.*
+- **c4d.threading.C4DThread**: *The base class for custom Cinema API threads. Operations can be done on multiple cores or in the background.*
 
 ## Examples
 

scripts/03_application_development/readme.md

@@ -1,5 +1,5 @@
 #coding: utf-8
-"""Explains the geometry model of the classic API in Cinema 4D.
+"""Explains the geometry model of the Cinema API in Cinema 4D.
 
 The script either evaluates the caches of the currently selected object or when there is no
 object selection, or inserts the following object hierarchy into the active document and evaluates 
@@ -10,7 +10,7 @@
         +- Bend Object
 
 Topics:
-    * The geometry model of the classic API
+    * The geometry model of the Cinema API
     * The purpose and structure of generator and deform caches
     * c4d.BaseObject
     * c4d.PointObject
@@ -23,10 +23,10 @@
     * PrintCacheTree(): Prints out the cache-tree of the passed object.
 
 Overview:
-    All geometry in the Cinema 4D classic API is represented as `BaseObject` instances. `BaseObject` 
+    All geometry in the Cinema 4D Cinema API is represented as `BaseObject` instances. `BaseObject` 
     instances can also express non-geometry entities as light objects or cameras, but they are being 
     ignored in this context. There are two fundamental types of geometry representations in the 
-    classic API:
+    Cinema API:
 
         * Generator objects
         * Non-generator objects
@@ -39,7 +39,7 @@
     objects do not allow users to modify their underlying cache manually which also applies to 
     programmatic access.
 
-    There are two types of geometry caches in the classic API. Caches for internal representations 
+    There are two types of geometry caches in the Cinema API. Caches for internal representations 
     of generator objects, they are plainly referred to as *caches*, and *deform caches*; which can
     only be found on non-generator objects. The latter represents the state of a generator, as 
     expressed by its parameters, as a (more) discrete form. In most simple cases this means

scripts/03_application_development/threading/readme.md

@@ -1,5 +1,5 @@
 #coding: utf-8
-"""Explains the user-editable polygon object model of the classic API.
+"""Explains the user-editable polygon object model of the Cinema API.
 
 The example constructs a simple polygonal cube object.
 

scripts/04_3d_concepts/modeling/geometry/geometry_caches_s26.py

@@ -1,5 +1,5 @@
 #coding: utf-8
-"""Explains the user-editable spline object model of the classic API.
+"""Explains the user-editable spline object model of the Cinema API.
 
 The example constructs two spline objects, one without tangents and one with tangents.
 

scripts/04_3d_concepts/modeling/geometry/geometry_polygonobject_s26.py

@@ -1,12 +1,12 @@
 # Geometry
-Provides examples for geometry types in the classic API.
+Provides examples for geometry types in the Cinema API.
 
-All geometry in the Cinema 4D classic API is represented as `BaseObject` instances. `BaseObject` instances can also express non-geometry entities as light objects or cameras, but they are being ignored in this context. There are two fundamental types of geometry representations in the classic API:
+All geometry in the Cinema 4D Cinema API is represented as `BaseObject` instances. `BaseObject` instances can also express non-geometry entities as light objects or cameras, but they are being ignored in this context. There are two fundamental types of geometry representations in the Cinema API:
 
 * Generator objects
 * Non-generator objects
 
-Realized are most forms of classic API geometry by the following type hierarchy (there are some outliers as for example VolumeObject which have their own type, but these are still all `BaseObject` instances):
+Realized are most forms of Cinema API geometry by the following type hierarchy (there are some outliers as for example VolumeObject which have their own type, but these are still all `BaseObject` instances):
 
     c4d.BaseObject
     +- c4d.PointObject
@@ -18,17 +18,17 @@ Generator objects are objects which generate some form of geometry over their pa
 
 Non-generator objects on the other hand do not have any parameters which are exposed in the Attribute Manager which would influence their geometry. The two types which follow this model are `LineObject` and `PolygonObject`, both derived from `PointObject` . `PolygonObject` represents discrete polygonal data over vertices and polygons, and `LineObject` represents discrete curve data over points and segments. The outlier from this model is the type `SplineObject` which is representing splines. It is both a `PointObject` and a generator object. Spline generator objects in the sense of parametric objects, as for example the Circle Spline object, return directly spline caches in the form of `LineObject`. But user-editable splines, `SplineObject` instances, also have a `LineObject` cache for their current interpolation settings. 
 
-There are two types of geometry caches in the classic API. Caches for internal representations of generator objects, they are plainly referred to as *caches*, and *deform caches*; which can only be found on non-generator objects. The cache of a generator object represents the set of parameters the generator object had when the cache was built. In the case of simple generators, as for example the Cube generator object, the cache is a `PolygonObject`, representing the polygons of that generator. But generator object caches can be much more complex, where the cache of the generator is a hierarchy of objects, including other generator objects with their own caches. 
+There are two types of geometry caches in the Cinema API. Caches for internal representations of generator objects, they are plainly referred to as *caches*, and *deform caches*; which can only be found on non-generator objects. The cache of a generator object represents the set of parameters the generator object had when the cache was built. In the case of simple generators, as for example the Cube generator object, the cache is a `PolygonObject`, representing the polygons of that generator. But generator object caches can be much more complex, where the cache of the generator is a hierarchy of objects, including other generator objects with their own caches. 
 
 Deform caches can only be found on non-generator `PointObject` objects and they are generated when a deformer, e.g., the Bend object, is applied to them. These caches then represent the deformed state of the `PolygonObject` or `LineObject` and realize the non-destructive nature of deformers in Cinema 4D. Since many objects in a scene can be generator objects, deform caches are often buried deep within the cache of a generator object.
 
 ## Examples
 
 | File | Description |
 | :-   | :-          |
-| geometry_caches_xxx.py | Explains the geometry model of the classic API in Cinema 4D. |
-| geometry_polygonobject_xxx.py | Explains the user-editable polygon object model of the classic API. |
-| geometry_splineobject_xxx.py | Explains the user-editable spline object model of the classic API. |
+| geometry_caches_xxx.py | Explains the geometry model of the Cinema API in Cinema 4D. |
+| geometry_polygonobject_xxx.py | Explains the user-editable polygon object model of the Cinema API. |
+| geometry_splineobject_xxx.py | Explains the user-editable spline object model of the Cinema API. |
 | operation_extrude_polygons_xxx.py | Demonstrates how to extend polygonal geometry at the example of extruding polygons. |
 | operation_flatten_polygons_xxx.py | Demonstrates how to deform points of a point object at the example of 'flattening' the selected polygons in a polygon object. |
 | operation_transfer_axis_xxx.py | Demonstrates how to 'transfer' the axis of a point object to another object while keeping its vertices in place. |

scripts/04_3d_concepts/modeling/geometry/geometry_splineobject_s26.py

@@ -1,5 +1,5 @@
 # Modelling
-Both the classic API and the maxon API provide types of geometry representations and modelling tools for them. The maxon API represents geometry with Scene Nodes, which are currently not yet documented in Python. Documented are here the classic API geometry representations and the modelling tools which exist for them, both in the classic and maxon API.
+Both the Cinema API and the Maxon API provide types of geometry representations and modelling tools for them. The Maxon API represents geometry with Scene Nodes, which are currently not yet documented in Python. Documented are here the Cinema API geometry representations and the modelling tools which exist for them, both in the Cinema and Maxon API.
 
 ## geometry
 Provides examples for the fundamental geometry types `PointObject`, `SplineObject`, `PolygonObject`, `LineObject`, and `Cpolygon`, how to construct and manipulate them, as well as for the concept of caches used by them. The manipulation and construction examples provided here are of more fundamental nature. For using existing modelling tools, see the section *modelling_commands*.

scripts/04_3d_concepts/modeling/geometry/readme.md

@@ -6,9 +6,9 @@ The Cinema 4D API provides classes to describe complex 3D scenes and tools to ed
 
 ## Content
 
-* **modeling**: *The classic API provides the base classes for modeling in Cinema 4D. The MAXON API provides further, advanced modeling tools.*
+* **modeling**: *The Cinema API provides the base classes for modeling in Cinema 4D. The MAXON API provides further, advanced modeling tools.*
 
-* **rendering**: *The classic API provides tools to render a given BaseDocument*
+* **rendering**: *The Cinema API provides tools to render a given BaseDocument*
 
 * **scene_elements**: *Information about scene settings, take system, objects, tags, materials, shaders and animation.*
 

scripts/04_3d_concepts/modeling/readme.md

@@ -1,6 +1,6 @@
 # Rendering
 
-The classic API provides tools to render a given BaseDocument.
+The Cinema API provides tools to render a given BaseDocument.
 
 Classic API:
 - **c4d.documents.RenderData**: *Represents a set of render settings of a BaseDocument.*