OTOY Forums

Hi,

I was going through the slides of the OTOY GTC 2017 presentation and the feature list for 3.07 looks really impressive.
https://www.slideshare.net/OTOYInc1/the ... 7-76278133

I was wondering what would be the rough release date for 3.07

regards
Rohan
http://www.rohandalvi.net

Everything in 3.x that got a screenshot in the slides is working nicely in an internal build. Testing stability this week and next, then we can share a more precise ETA.

Hi,

Thank you for the quick reply. Looking forward to the new release. As I said the feature set look really good. Also I saw the new AI based denoiser on Facebook, that look really cool too.

Regards
Rohan.

Hi,

Sorry to bother you but one more question. In the features of 3.07 there's a mention of C API. What exactly does that mean. I'm not a programmer but what will the C API allow developers or users with programming knowledge to do? A simple example would be great.

Regards
Rohan

Just adding to the previous question. The octane modules shown in the slides, are those examples of the kind of stuff that can be made using the C/C++ API.

So if I understand it correctly, the API will allow any programmer to code a custom module/node for octane, would that be correct?

Also will this be available for just standalone or for the plugins as well?

Regards
Rohan.

With 3.07, you will have greater access to the internals of Octane even from the lua API. We have added a native C API in 3.07 (still in testing) on top of this, which will allow white listed script nodes to include C as well as lua code, which open the door to just about anything. For user stafety on LiveDB, we will sanbdbox module access, and only allow whitelisted modules to be published as LiveDB entries. This will work across plug-ins, the same way script nodes already do now.

For modules that can edit, send or generate data in the node system from another process (like Phantom Scatter), there will be an IPC interface and API just for this purpose, and we will whitelist modules for this use case as well.

For sideloading 'untrusted' C modules w/ 3.07+ locally, you will have to enable a flag (same as we do now for script nodes). We are looking into ways of sandboxing untrusted C code cleanly so even that could run on ORC or be published into LiveDB down the line.