Preview of OctaneRender for Blender

[kavorka]

so excited for this release.
will greatly speed up my work and allow me to get better results.

[JimStar]

Region render!! It would solve a lot of time in my renders. Truly amazing.

You should understand, that the plugins can not implement the rendering features Octane engine does not have.
So I've implemented this feature in the plugin "in advance" - so far it uses the full rendered image taken from the engine, and shows the needed part.
I will improve it after this feature will be available in Octane.

[megacal]

re: JimStar's system specs...

Nothing very cool.
i7, One GTX-690 (2 cores dedicated for rendering), and a separate simple GPU for display... Engine team have done the great job increasing last versions speed...
And don't forget, that the video is highly compressed - so in real the quality is better than on the video, when something is moved in viewport...

Great!

One question about the render process...
With the Extended Plugin by yoyoz, Blender has to export a mesh for each frame which
takes some time before Octane renders it. Will Octane Render for Blender do the same? I.e. does it by-pass this step? If so, render times should be much faster (?)

We're ready to purchase anytime.

[JimStar]

One question about the render process...
With the Extended Plugin by yoyoz, Blender has to export a mesh for each frame which
takes some time before Octane renders it. Will Octane Render for Blender do the same? I.e. does it by-pass this step? If so, render times should be much faster (?)

The integrated plugin eliminates the .obj file write-read disk operations, the digital-to-text and text-to-digital translations when writing-reading this file, and some other things which slowdown the export-import process very much.
But. The acceleration structure-building process (voxelizing other words) which Octane engine needs - can not be eliminated by any plugin. This process is a much time-consuming among other before-the-render scene preparations things - as it runs on CPU before the scene can be started to be rendered on GPU.
So, the before-the-render-will-be-started time will be less in the Octane ingetration than in export-script, but you should understand that it can not be "null", as anyway, after every scene is translated and loaded to the engine, the plugin should wait before all the meshes will be voxelized by the engine.
As I already wrote - the engine team did a really great job optimising this process, so you can see in the standalone how fast the meshes are voxelized in last Octane versions when you load .obj mesh into standalone... The same voxelizing time will be needed by the plugin when it loads the meshes to the engine...

PS. Thanks very much to yoyoz for the great job which allows to Blender users work with Octane all this time. My wife has used his script too, and was happy with it.

[portdog77]

JS - "PS. Thanks very much to yoyoz for the great job which allows to Blender users work with Octane all this time. My wife has used his script too, and was happy with it."

And now she uses your plugin... How cool is that!

Now i'm wishing I was your wife... No, not really.

[daveyt]

Thanks for the update Jim!!

[megacal]

The integrated plugin eliminates the .obj file write-read disk operations, the digital-to-text and text-to-digital translations when writing-reading this file, and some other things which slowdown the export-import process very much.
But...

JimStar,
thanks for explaining the process. Even with the "But..." it sounds like OR4B
will be a huge improvement for workflow and cut render times.

[megacal]

Thanks very much to yoyoz for the great job which allows to Blender users work with Octane all this time. My wife has used his script too, and was happy with it.

-JimStar

Yes, I couldn't animate in Octane without it. Excellent plugin!

[AdamT]

Any Update? Thanks

[megacal]

Pretty soon....before Christmas, I think/hope.

"Wait for it, waiiit forrrrr it...."