Page 1 of 2

Having octane integrated in 3d applications.

Posted: Thu Apr 28, 2011 11:56 am
by MaTtY631990
Is it possible to have octane integrated within a 3d app. It would solve things like the render time for animations. No more exporting of the model and textures. Of course it will still do voxeling but animation render times would decrease significantly reduce to half the time it needs, since some scenes can take a couple of minutes for every frame.

thanks.

Re: Having octane integrated in 3d applications.

Posted: Thu Apr 28, 2011 1:19 pm
by Jaberwocky
MaTtY631990 wrote:Is it possible to have octane integrated within a 3d app. It would solve things like the render time for animations. No more exporting of the model and textures. Of course it will still do voxeling but animation render times would decrease significantly reduce to half the time it needs, since some scenes can take a couple of minutes for every frame.

thanks.
probably no need if Faces programming skills are used by Radiance in the future.

See the attached tech demo video from face.

See link http://www.vimeo.com/22785409

Re: Having octane integrated in 3d applications.

Posted: Thu Apr 28, 2011 1:56 pm
by matej
If you take face's approach, then the question becomes more like; Is it possible to have the 3D app integrated in Octane :D

But remember that that's just an experiment.

Re: Having octane integrated in 3d applications.

Posted: Thu Apr 28, 2011 2:34 pm
by MaTtY631990
probably no need if Faces programming skills are used by Radiance in the future.

See the attached tech demo video from face.
Thanks for info. Does this experiment take away the need to import model and textures every frame or can it render frame after frame.

Re: Having octane integrated in 3d applications.

Posted: Thu Apr 28, 2011 3:12 pm
by face
It can only send the camera data into Octane.
It should can change every value which is CPU based, like the UI start, refresh, reset camera, also changes of the mesh attributes like color, texture, whatever or changes in settings like samples, exposure, no of bounces.
Possible is also to read these values from Octane.

To integrate a renderer in a 3D-App is a lot more work.
You must program a version for every app, sometimes two version for 32/64bit.
If i only use the ones which are in the main plugin thread, then i come in the baddest configuration to this calculation:
9 Apps x 2 versions(32/64bit) = 18
18 x the latest 3 application versions = 54

Ok, thats a little bit unrealistic because not ever the api changes are so dramatically.
I think arround 25-30 is acceptable ;)

And at the end, when RS do it self, they must buy every App.
I think in the near future, it is unrealistic.

A possible solution is, to go the same way as vray gone.
They have an external renderer, which is updated, when the scene is changed.

face

Re: Having octane integrated in 3d applications.

Posted: Thu Apr 28, 2011 4:59 pm
by PeterCGS
Is it theoretically possible to send over the mesh information using RAM over to Octane just like you do with the camera? Right now alot of time when doing animations are spent on saving down the mesh to disk, load Octane, and then loading in the object from disk. Having Octane already opened, and accessing the the mesh from RAM would save a huge amount of time.

In my world you are already halfway there :) I hope that the experimental features in XSI done by Face, gets green light from Radiance and can be expanded to incorporate meshes and motion vectors *cough* *cough*

Re: Having octane integrated in 3d applications.

Posted: Thu Apr 28, 2011 7:51 pm
by Jaberwocky
PeterCGS wrote:Is it theoretically possible to send over the mesh information using RAM over to Octane just like you do with the camera? Right now alot of time when doing animations are spent on saving down the mesh to disk, load Octane, and then loading in the object from disk. Having Octane already opened, and accessing the the mesh from RAM would save a huge amount of time.

In my world you are already halfway there :) I hope that the experimental features in XSI done by Face, gets green light from Radiance and can be expanded to incorporate meshes and motion vectors *cough* *cough*

Yep +100

Re: Having octane integrated in 3d applications.

Posted: Thu Apr 28, 2011 8:25 pm
by abstrax
Hi all,

we are aware of the limitations of the current export workflow and unfortunately it's not possible to have a tighter integration of Octane into 3D apps at the moment, due to a lack of an API.

We have been thinking about this and we will definitely attack this problem as soon as possible. I can't say when, because we are currently focusing on other things. Our aim is to have the necessary capabilities available on the Octane side, if not with 1.0final then at least shortly after the 1.0final release with one of the point updates. And if programmers like Face then join the development of the integration into various 3D apps, it should not take too long until the first plugins will be available.

I know, this is all still quite a bit fuzzy and unspecific, but all I can say at this point in time.

Cheers,
Marcus

Re: Having octane integrated in 3d applications.

Posted: Fri Apr 29, 2011 1:22 am
by radiance
Hi all,

I can't say much about it yet, but we will be announcing some structural changes (hopefully) that I have been busy with the last months soon that will adress the tight 3d app integration requests.

Radiance

Re: Having octane integrated in 3d applications.

Posted: Fri Apr 29, 2011 5:33 am
by PeterCGS
Great news indeed! I totally disregard that "hopefully" remark hahaha...