About the devkit examples
The devkit examples can change between releases. This includes their node IDs. Node IDs are used to uniquely identify nodes and plug-ins. If you will be using examples in production, or basing your own plug-ins on the example plug-ins, please obtain a unique node ID from https://mayaid.autodesk.io.
C++, C#, and Python example plug-ins are packaged with the devkit, as well as example standalone applications in C++ and Python.
The example plug-ins extend Maya by adding functionality, such as nodes and commands, to it. Standalone applications use the Maya API but run outside of Maya.
| Type of Example | Location on Windows | Location on macOS and Linux |
|---|---|---|
| C++ plug-ins | devkit\devkitBase\plug-ins\ |
devkit/devkitBase/plug-ins |
| Python API 1.0 plug-ins | devkit\devkitBase\plug-ins\python\api1 |
devkit/devkitBase/plug-ins/python/api1 |
| Python API 2.0 plug-ins | devkit\devkitBase\plug-ins\python\api2 |
devkit/devkitBase/plug-ins/python/api2 |
| C# plug-ins | devkit\devkitBase\dotnet |
not available |
| Standalone C++ applications | devkit\devkitBase\applications |
devkit/devkitBase/applications |
| Standalone Python applications | devkit\devkitBase\applications\python |
devkit/devkitBase/applications/python |
Some examples require third-party libraries to compile or run. Most notably, any plug-in example that begins with abc cannot be built without additional libraries not included with Maya. Do not attempt to build these examples.
Example Naming Conventions
Examples are built into plug-ins that create specific items. An example's suffix indicates the item its plug-in creates.
| Suffix | Element created |
|---|---|
| Cmd | command |
| Tool | interactive tool |
| Node | dependency node |
| Translator | file translator |
| Shader | shading node |
| Manip | manipulator |
| Field | dynamic field |
| Emitter | dynamic emitters |
| Spring | dynamic spring |
| Shape | shape |