R17 sdk [closed]



  • On 30/07/2015 at 05:51, xxxxxxxx wrote:

    Hello
    There are speculations about upcoming r17 at several forums.
    We know about python sdk.
    What about CAPI?



  • On 31/07/2015 at 02:22, xxxxxxxx wrote:

    Hi Ilya,

    which speculations are you talking about?
    We announced a change of the Python integration from 2.6.4 to 2.7.9 ahead of time, as it may have impact on existing plugins.
    Everything else will be made public as soon as R17 is officially announced. But you can rest assured, R17 will again have a C++ API  😉



  • On 31/07/2015 at 04:24, xxxxxxxx wrote:

    Originally posted by xxxxxxxx

    Hi Ilya,

    which speculations are you talking about?
    We announced a change of the Python integration from 2.6.4 to 2.7.9 ahead of time, as it may have impact on existing plugins.
    Everything else will be made public as soon as R17 is officially announced. But you can rest assured, R17 will again have a C++ API  😉

    Argh, sorry, i mean discussions at cgtalk and c4dcafe, mostly non sdk related.

    What i mean under sdk, previous versions: maxon rename classes and etc. strange decorations - will be such with new?
    From my side, i know several developers which moved from c4d, needs to support several versions of c4d and code is differ. So they gave up.
    LEGACY stuff are still supported?

    Upd.
    What will be with resEdit tool? any info to support r17



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

    I see something new

    > Python
    >   BrushDabData
    >   SculptBrushParams
    >   SculptObject
    > C++
    >   lib_sculptbrush.h
    >   SculptMouseData
    >   Spline Brush SDK Example
    >   Other Additions
    >   lib_sculpt.h
    >



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

    Andreas or Jean-François
    Will sdk info presented after demo/retail in September?



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

    Hi Ilya,

    actually you made us aware of a really important point. As R17 is the first major release for the new SDK Support Team, we were currently working on the processes. And such announcements ahead of a release are new to MAXON as well.
    So, thanks, for reminding us!
    Regarding the __LEGACY_API define, this will be gone with R17. I have just posted an announcement.

    Regarding news in the R17 SDK, here are a the most important points:

    Python
    - Take System Support
    - More C++ API Coverage
    - Sculpting Additions
    - Fixes

    C++
    - Take System Support
    - Token System Support
    - UTF-32 Unicode Strings
    - Removed Legacy Defines
    - SculptBrush MouseData
    - Sculpting Additions
    - SplineHelp Enhancements
    - Spline Functions
    - Spline Brush SDK Example
    - CKey Autotangent Support
    - New Color Chooser Support
    - Hover menu
    - New Motion Blur API

    I hope, this answers at least a few of your questions.
    For more you will have to wait for the actual release.



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

    Thanks for info 👍



  • On 05/08/2015 at 12:31, xxxxxxxx wrote:

    also need to recompile and refactory non-legacy code according new sdk?

    Motion blur api ? https://www.sidefx.com/index.php?option=com_forum&Itemid=172&page=viewtopic&t=41064

    ------------------------
    Also someone, write about new sdk at cgsociety, i can not - lost account, Leigh or Bjorn(Srek) banned me permanently.

    I think it will be my last version of c4d, which will support(i have small collection of plug-ins). Thanks to sdk team. Keep great work.



  • On 06/08/2015 at 01:55, xxxxxxxx wrote:

    Hi Ilya,

    sorry, to hear you got banned from cgsociety. I checked with Björn (srek), neither he nor MAXON had anything to do with this.
    For the new features of the API, like Motion Blur, you will have to wait for the release and final documentation.

    also need to recompile and refactory non-legacy code according new sdk?

    In general plugins compiled for R16 will work in R17. So if you don't need features from R17, you can still compile against R16 (or even prior versions).
    There will be minor changes in R17 SDK, that need changes in your code to compile. We are still working on the documentation, but are planning to provide guides as soon as possible.



  • On 06/08/2015 at 02:06, xxxxxxxx wrote:

    In general plugins compiled for R16 will work in R17

    Great, hopes-hopes. Thanks. I simply maintain several in-house plug-ins, i still have c4d users.
    ----------
    Srek simply request to ban me to Leigh or Keenly(they are admins), she or he do it.
    I was rude and harsh about silence from maxon hq stuff and etc.
    Anyway i switch to AutoDesk discussion groups and social network in companies. And will forget cgs



  • On 06/08/2015 at 12:20, xxxxxxxx wrote:

    Hi again
    I'm looking of profile of maxon company in linkden. I see sculpt developer move from maxon. Sculpt lib will have end of life?!



  • On 07/08/2015 at 04:01, xxxxxxxx wrote:

    Hi Ilya,
    of course, MAXON cannot lose feature development capabilities and will replace people leaving. We already have a suitable replacement for sculpting.



  • On 07/08/2015 at 04:09, xxxxxxxx wrote:

    Hello
    Sure thing. I was afraid after reading of Paul Everett suggestion about dropping of development for unused projects



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

    Hi
    I hope Token support is included in Python even though it's not listed?
    And will there be a Python API for the Houdini Engine? To load and query assets or get houdini version/path etc?

    -b



  • On 07/08/2015 at 06:24, xxxxxxxx wrote:

    Originally posted by xxxxxxxx

    Hi
    I hope Token support is included in Python even though it's not listed?

    -b

    up to several post

    Regarding news in the R17 SDK, here are a the most important points:

    Python
    - Take System Support



  • On 07/08/2015 at 06:26, xxxxxxxx wrote:

    Takes and Tokens are not the same thing. Both are listed under C++. Only takes is listed under Python.
    I'm worried because we need this to resolve C4D paths in Deadline.

    -b



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

    argh sorry, my fault

    maybe under - More C++ API Coverage



  • On 07/08/2015 at 06:29, xxxxxxxx wrote:

    No problem :)



  • On 07/08/2015 at 09:50, xxxxxxxx wrote:

    Originally posted by xxxxxxxx

    And will there be a Python API for the Houdini Engine? To load and query assets or get houdini version/path etc?

    Such?
    for current beta(1) - > id of prefshoudini = 1032269

    import c4d  
    from c4d import documents, plugins  
      
    def prefs(id) :  
      return plugins.FindPlugin(id, c4d.PLUGINTYPE_PREFS)  
        
    def main() :  
      c4d.PrefsLib_OpenDialog(1032269)  
      print prefs(1032269)[c4d.PREFS_HOUDINI_ENGINE_VERSION]  
      print prefs(1032269)[c4d.PREFS_HOUDINI_ENGINE_INSTALLATION_PATH]  
      
    if __name__=='__main__':  
      main()
    

    Another things are through ctypes + several modules, according sdk - http://www.sidefx.com/docs/hengine1.9 + hdk , even enviro vars like HAPI

    + at video https://vimeo.com/135607909 --- 02:54: SideFx shows PyObjectScript and HE 2.0
    interesting thing



  • On 09/08/2015 at 08:48, xxxxxxxx wrote:

    Yeah, today, after discussions with my employer, they decided will not upgrade to r17. They found replacement of mograph and something in c4d, in own in-house tools.

    Good bye c4d, sdk team. Thanks for all

    Andreas, you can to delete or close or anything else  with topic


Log in to reply