Cinema 4D R17 Drops C++ API Legacy Support



  • On 05/08/2015 at 07:38, xxxxxxxx wrote:

    User Information:
    Cinema 4D Version:    
    Platform:      
    Language(s) :

    ---------
    With Cinema 4D R17 the legacy support for the old pre-R15 C++ API will be dropped. The __LEGACY_API define will no longer be available. This means after two years of time for transition you will finally have to switch to the new API in order to compile plugins for R17. This step is not taken lightly, but was necessary to proceed with Cinema 4D's internal development. A guide how to transition your plugin can be found in the SDK documentation.
    Most of the needed changes can be done with simple search & replace operations. Only very few changes need your attention and manual adjustment of code.

    MAXON is aware, that this means additional work for external developers. We apologize for this.

    The Cinema 4D R17 C++ SDK will also require newer IDE versions:
    Windows: Visual Studio 2013
    Mac: Xcode 6 (any subversion will work, tested 6.0 to 6.4)

    If you need any assistance in handling the transition, please feel free to contact the SDK Support Team, either in Plugin Café forums or via e-mail (sdk_support@maxon.net).



  • On 05/08/2015 at 07:49, xxxxxxxx wrote:

    Hm, what i say...😠😢
    I need to fight with my laziness :clown:
    Thanks for info



  • On 15/08/2015 at 08:57, xxxxxxxx wrote:

    I tried compiling C4D plugins with the new VS2015 Community version and it seemed to work fine.
    Can we assume that R17++ will support the new VS2015 versions too?

    Also.
    Is it too late to ask Maxon to go back to the old way they had the API set up. Without putting everything in the "examples" folder?
    That was really annoying to me. And I think there were other people that also hated that.

    -ScottA



  • On 15/08/2015 at 09:11, xxxxxxxx wrote:

    That's the fate of the IDE users 
    But as far as I remember they already changed it in an R16 SP, or
    at least with R17.



  • On 15/08/2015 at 09:22, xxxxxxxx wrote:

    Originally posted by xxxxxxxx

    Is it too late to ask Maxon to go back to the old way they had the API set up. Without putting everything in the "examples" folder?
    That was really annoying to me. And I think there were other people that also hated that.

    I missed this and simply remove *..* in notepad, in sln file   < if not to examples dir
    Silly from my side, of course 🤢
    (firstly i did not understand why need examples)



  • On 16/08/2015 at 00:04, xxxxxxxx wrote:

    Originally posted by xxxxxxxx

    [...] Also.Is it too late to ask Maxon to go back to the old way they had the API set up. Without putting everything in the "examples" folder?That was really annoying to me. And I think there were other people that also hated that.-ScottA

    That was already changed with SP2 (six months ago).

    Best regards,

    Wilfried



  • On 16/08/2015 at 07:47, xxxxxxxx wrote:

    ^Thanks. That's good news.
    I still prefer to use R13. But I do also like to try out the new demos every year. And take a spin through the newest SDK stuff. And that "Examples" thing was a P.I.M.A.

    Is there any official word about VS2015 compatibility yet?
    I'm guessing that most people will probably be using the 2015 versions by the time R17 comes out.

    -ScottA



  • On 16/08/2015 at 08:07, xxxxxxxx wrote:

    Originally posted by xxxxxxxx

    I'm guessing that most people will probably be using the 2015 versions by the time R17 comes out.
    -ScottA

    Why are you thinking such?
    I met negative feedback about 2015. Mostly at ruMSDN and several russian coding forums.
    Yes, i saw requests at several communities and porting to this platform, for example adsk dev.network.
    But for example fabric team use from vs 2010 to 2013, i could only compile some c4d stuff with vs2010x64 and SpliceAPI v.1.14.2 a few months ago



  • On 16/08/2015 at 09:21, xxxxxxxx wrote:

    I'm just guessing based on previous experiences. And the number of posts on various sites where people are already asking for VS2015 support.

    When VS2013 was in final pre-release I couldn't build C4D plugins with it either. But as soon as the first RTM was released it worked fine for me.
    I've had no internet for a few months. So I've not tried the any of the 2015 pre-releases.
    But I just installed 2015 this week (It apparently went RTM a coupe of weeks ago) and it seems to work just fine.
    Based on the past couple of versions. VS seems to have a pattern of having many problems until the final version is released. And then it works pretty good.

    I have not used it that much yet. But so far it seems solid.

    -ScottA



  • On 16/08/2015 at 09:44, xxxxxxxx wrote:

    I will to test some new features of directx 12 / win10 for adsk stingray and i had chance compile a few, but it was flash view.
    Of course vs 2015 should be to support if possible



  • On 16/08/2015 at 09:49, xxxxxxxx wrote:

    Originally posted by xxxxxxxx

    ^Thanks. That's good news.I still prefer to use R13. But I do also like to try out the new demos every year. And take a spin through the newest SDK stuff. And that "Examples" thing was a P.I.M.A.Is there any official word about VS2015 compatibility yet?I'm guessing that most people will probably be using the 2015 versions by the time R17 comes out.-ScottA

    VS2015 isn't officially supported (for a good reason); you could use it and discover its bugs for yourself actually if you like though.

    We reported several (code generation) bugs already for the previews of VS 2015 that haven't been fixed for the RTM version and which will (most likely) need until SP1 of VS 2015 to be fixed.

    Therefore we'd advise developers to wait at least for SP1 of VS2015 before using it.

    Best regards,

    Wilfried



  • On 16/08/2015 at 10:11, xxxxxxxx wrote:

    Ok. Thanks Wilfried.

    -ScottA



  • On 27/08/2015 at 07:27, xxxxxxxx wrote:

    Will plugins compiled for R16 using the __LEGACY_API work on R17?
    What about R16 plugins compiled without __LEGACY_API?



  • On 04/09/2015 at 17:24, xxxxxxxx wrote:

    Howdy,

    Originally posted by xxxxxxxx

    ...The Cinema 4D R17 C++ SDK will also require newer IDE versions:
    Windows: Visual Studio 2013
    Mac: Xcode 6 (any subversion will work, tested 6.0 to 6.4)...

    Well, I installed Visual Studio Express 2013 and all my plugins compiled fine except my CD FBX Import/Export plugin. It is using the FBX SDK 2014.2.1 which doesn't have a library for VS 2013. It only has libraries up to VS 2012.

    So I changed the project's properties to compile using v110, and it compiled fine. Do you foresee any issues with that? The plugin loaded fine in R17 Demo and I was able to import a file using it with no crashing.

    I'm not really ready to upgrade the FBX SDK to 2015 because I'm still supporting earlier versions of Cinema 4D and FBX 2015 only supports clang on Mac OS. FBX 2014 supports both clang and gcc.

    Adios,
    Cactus Dan



  • On 05/09/2015 at 02:17, xxxxxxxx wrote:

    All my plugins are compiled with R14 or R15 and still work in R17. 😌



  • On 22/11/2015 at 07:04, xxxxxxxx wrote:

    Hi
    I got mac machine for testing(thanks to one girl coder).
    It has el Capitan and xcode 6.4. Compile sdkR17 samples normally and they run too.

    I read at apple dev.network that xcode 7.x supports 10.11. What do you think need to upgrade/update?

    (i tried to search about new xcode at this forum)



  • On 23/11/2015 at 06:31, xxxxxxxx wrote:

    Hi Ilya,

    we recommend to stick to the versions mentioned on our development blog.



  • On 23/11/2015 at 10:00, xxxxxxxx wrote:

    Thank you for reply


Log in to reply