R17 sdk [closed]

Helper

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.

Helper

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.

Helper

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

Helper

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?!

Helper

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.

Helper

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

Helper

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

Helper

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

Helper

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

Helper

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

argh sorry, my fault

maybe under - More C++ API Coverage

Helper

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

No problem

Helper

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

--- 02:54: SideFx shows PyObjectScript and HE 2.0
interesting thing

Helper

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

Helper

On 10/08/2015 at 03:59, xxxxxxxx wrote:

Hi Ilya,

sad to hear that. I hope, one day you'll return to C4D development.

Helper

On 10/08/2015 at 04:48, xxxxxxxx wrote:

Any comments on Tokens support in Python?

-b

Helper

On 10/08/2015 at 04:57, xxxxxxxx wrote:

Originally posted by xxxxxxxx

Hi Ilya,

sad to hear that. I hope, one day you'll return to C4D development.

Sure, i will test demo and will check out sdk changes - i'm not only lazy and be curious

Helper

On 24/08/2015 at 07:32, xxxxxxxx wrote:

Hello
I download demo.
testing examples of sdk ... docs?

does updated to ogl 3.2 context for handles and etc.?

http://oi57.tinypic.com/2e3c2l1.jpg

Helper

On 25/08/2015 at 01:25, xxxxxxxx wrote:

Hello,

what exactly is your question please?

Best wishes,
Sebastian

Helper

On 25/08/2015 at 01:56, xxxxxxxx wrote:

Hello Sebastian
Argh, sorry

I ask about release of sdk manuals for r17.

I test my several plug-ins, slightly. Something were change.

Helper

On 26/08/2015 at 01:37, xxxxxxxx wrote:

Hello,

the R17 C++ and Python documentation will be released next week.

Best wishes,
Sebastian