Dear Development Community,

due to some recent "module ID" conflicts we've seen reported in the last months, we remind you that the module ID used in the projectdefinition.txt MUST be unique to the dynamic library.
The module ID is used by Cinema 4D to distinguish modules and, "similarly" to plugin ID, it's supposed to be unique.
The practice of using any of the projects shipped with the sdk.zip as a template is fine as long as you keep attention on changing the module ID provided by default.
Finally it's worthy reminding that the module ID should follow a reverse domain notation order as suggested from the value available here where based on your username and, eventually, the website used in your profile, we suggest a potential root representation.

The SDK Team

Dear Community,

with the incoming Winter Holiday season, being most of the Team in vacation from December 23rd to January the 2nd, you might experience slowdowns in the usual support workflow. Please be patient until the full team is back in January 2020.

Best wishes,
The Maxon SDK Team

Dear PluginCafé user,

on Monday, November the 25th, from 07:00 to 08:00 UTC, due to planned maintenance activity, the services will be down and unreachable during this period.
Please be sure to quit from this server duly.

Apologizing for any inconvenience this might cause, give best.

Maxon SDK Team

Hi rui_mac, thanks for reaching out us.

With regard to the issue reported, I'm a bit surprised to see c4d.documents.KillDocument() executed considering the way garbage collection is handled in Python (i.e. you don't have to take care of freeing memory - if not on very explicit cases - since Python does it automatically)

Nevertheless, if you could provide us with a simple code to reproduce the issue we could get a better understanding of the cause.

Riccardo

Hi final3d, thanks for writing us.

Please file your suggestions and recommendations on Maxon Support page paying attention to select "Suggestions and Ideas for Maxon".

This forum is only aimed to discuss development-related topics.

Best, Riccardo

Being the SDK formerly known as Melange renamed in Cineware SDK, the category hosting the related discussion has been renamed accordingly.

Cheers,
MAXON's SDK Team

Hello,

by default, the MSVC build settings of the Cinema 4D R21 SDK activate Advanced Vector Extensions. This can cause issues on client systems that do not support AVX (the plugin will not show up for them).

The AVX settings are defined in the frameworks\settings\Base.props file.

To disable AVX support, simply remove the line

<EnableEnhancedInstructionSet>AdvancedVectorExtensions</EnableEnhancedInstructionSet>

The new major version R21 of Cinema 4D has been officially released and is now available for download. Everyone can now create accounts on the new MyMaxon portal (my.MAXON.net) and download the latest version of Cinema 4D.

An overview of all new development resources can be found on developers.maxon.net.

Cinema 4D Release 21 has been announced. The new release introduces several relevant changes for plugin developers.

• Existing C++ plugins must be adapted and re-compiled for R21.
• Building C++ plugins will require Visual Studio 2017 or Xcode 10.
• Only one version of Cinema 4D will exist in the future.
• A new licensing system replaces the old, serial number based system. Plugins, that base their licensing scheme on that serial number, must adapt.
• Also, the SNHookClass plugin type has been removed.

More information on Cinema 4D R21 is found here:

• Cinema 4D R21 Overview
• Complete Feature List
• Cinema 4D R21 FAQ

The adapted C++ and Python SDKs will be published with the release of Cinema 4D R21 in September.

Dear Community,

we will need to leave you alone for a few days during which you'll experiment limited support bandwidth since the MAXON's SDK Team will be traveling to Frankfurt am Main to attend a yearly-recurring company meeting.

See you next week again,
Riccardo in the name of the entire team