Best posts made by maxon

@trideshnik said in How to decompile cdl64 file?:

Hmm.. so..

Comrades, before getting the necessary information, I was told 100500+ times about copyright. Everyone saw fit to indicate this.

Dear, do you think that the person asking this question needs a triple copyright notice? If you do not want to answer or help, no one is forcing you, but making idiots out of people is bad form. I got a ton of off-topic information. reasoning, warnings. and only a fraction of the information I need. so nice.
but.
Thanks to those who indicated the direction in which to dig.

P.S. it seems to me that this is such a lifestyle. okay) khkhgxghzhuxvvldqkdfnhuv

This answer is considered irrespecutful and contradicts the collaboration spirit of the forum. User banned.

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

We are all very excited to announce that Ferdinand Hoppe ( @zipit ) has joined Maxon in our Team as SDK Specialist. Check out this post for more information.

The MAXON SDK Team

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

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.

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>

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