OTOY Forums

OctaneRender™ for Blender plugin. Windows x64 version.


The bundle consists from two parts:
1. OctaneRender™ Server
2. Blender - OctaneRender™ edition.

The first part (server) should be run on the same computer as the second one. To stop the server - just right-click its icon in the tray.
After the server is run - you can start rendering (or open a rendered view) from inside Blender. Before the very first rendering you should fill in the server address (only 127.0.0.1 at the time), login and password (your license key info) to activate the server. After the first rendering the server will remember this activation info, and you will not need to enter it again.

You should use only OctaneRender materials inside Blender scenes - the plugin knows nothing about Blender specific materials and textures (about any Blender nodes, generally speaking).


FIXES AND NEW FEATURES SINCE LAST RELEASE

• Added new feature: export of animation into OctaneRender Alembic file. The feature is implemented in the first draft, so you can test it...
  Only geometry and camera export is supported so far. Materials, imager, environment etc are not supported at this time, but you can tune them in standalone after export.
• New 1.33 engine.
• Fixed alpha-channel bug in rendered images.
• Minor bug fixes...

To export Alembic file instead of animation rendering - just set the "Export alembic" checkbox before starting animation rendering. After starting OctaneServer it will take some time before the LiveDB tree and LiveDB material previews will be available from Blender - as OctaneServer caches the LiveDB data from remote server right after starting. But only the materials groups tree will be re-cached every time after server start, LiveDB material preview images will be cached only once - so only the very first OctaneServer start will need some more time before LiveDB tree will be available in Blender.


DOWNLOAD (both distributives must be reinstalled, they depend on each other)

Blender Octane Edition - 1.33 - 3.3 beta (2.69) (53.4MB autoinstaller file)
Octane Server - 1.33 - 3.3 beta (7.8MB autoinstaller file)

JimStar wrote:To export Alembic file instead of animation rendering - just set the "Export alembic" checkbox before starting animation rendering.

wow, impressive

I need to test this.
So, I can export my scene and camera animation (for a flythrough of a building) and then set it up in Octane standalone and render?

I was just trying to figure out how to do this the other day.

kavorka wrote:So, I can export my scene and camera animation (for a flythrough of a building) and then set it up in Octane standalone and render?

Yep.

Added new feature: export of animation into OctaneRender Alembic file.

Woaw ... JIM !
That's a pretty f****** good update !

THANKS !!!!

Edit: This is working perfectly here ! Amaizing no more need to deal with exporter animate issues

Wow..good!

Thanks Mr. J

Regards

Hi, I have many scenes and complex models for which I have created all the materials in Octane standalone.

Do you think that there would be a possibility for the plugin to convert the materials contained in ocs, or ocm or orbx files into a node setup inside blender, to allow the direct use of already made objects or scenes inside blender without the need of re-creating all materials ?

ROUBAL wrote:Hi, I have many scenes and complex models for which I have created all the materials in Octane standalone.

Do you think that there would be a possibility for the plugin to convert the materials contained in ocs, or ocm or orbx files into a node setup inside blender, to allow the direct use of already made objects or scenes inside blender without the need of re-creating all materials ?

I was thinking the same thing and have found a work-around that seems to work well.

The big picture is to use your current octane standalone scene with materials and use a blender alembic file for just the camera and motion.

the details:
- go into the same blender file that has the mesh for your standalone scene
- animate a camera, hide the larger mesh items but leave a mesh cube so it has some geom
- check the export only shown items and check alembic, export the animation to alembic (should be a very small file)
- now in the standalone scene, add a group node connect both scene mesh and alembic mesh
- connect the alembic camera and that group node to the render target.

what you should be left with is a scene that uses the camera from the alembic file and your current standalone scene with all your materials intact.

-----------------
Wait a second
-----------------
I'm having a hard time getting this to work after I restarted my computer.