Jump to content

dast

Registered Member
  • Posts

    1,276
  • Joined

  • Last visited

  • Days Won

    65

Video Comments posted by dast

  1. One minor thing to mention is that R20 also uses the project tool, so the explanation provided by Kent in part 1 does also apply for that version.

    For those wondering, R19 and earlier versions don't use the project tool, but require a complete different setup. Something which is quite a laborious thing to do ... and this for every plugin.

    However, I can understand that to some it might seem as quite an effort to get the environment downloaded, installed, and set up ... only to write a plugin.

     

    One tip for the brave ones wanting to develop for multiple versions of Cinema4D: create a folder for each version, named accordingly, and put the SDK, projecttool, and bat-file(s) into that folder. (example D:\dev\SDK_R20, D:\dev\SDK_R21 and D:\dev\SDK_R23). Obviously, the paths in the bat files will need to point to the appropriate locations.

    Also, rename the created plugins.sln to include the version number (example: R20_plugins.sln). That way, if you have 3 Visual Studio's open (for R20, R21 and R23) you at least know which version is which. Been there, done that.

     

    I only watched part 1, so maybe Kent goes over this in a next video.

     

    @kbar Good luck with the development series!

×
×
  • Create New...

Copyright Core 4D © 2023 Powered by Invision Community