render3d

  • Increase font size
  • Default font size
  • Decrease font size

OCTANE (GPU)

E-mail Print PDF

Data

Type

  • Standalone renderer with exporters for a lot of 3d applications
  • 3dsmax plugin available as well as a blender plugin and rhino, softimage, revit, Cinema4d and lightwave

Info

Refractive software was aquired by Otoy, a cloud services firm. This can be interesting because at Otoy there are some smart people like the famous Paul Debevec, inventor of HDRI lighting. The Octane team now has some more ressources an will concentrate to make a final release of the renderer.

Data exchange can be done via obj format, rib or collada. Octane is a standalone renderer - or was until now - that comes with numerous exporters for 3d packages like 3dsmax, maya, softimage, blender, cinema4d. Since December 2011, a complete 3dsmax implementation is avialable. A huge improvement because you can use your preferred software to access this renderer.

Otoy now offers a Octane Render Cloud edition that is able to render scenes on a cloud in an extreme high speed. Have a look at the Nvidia presentation video link on the octane forum.

Release 1.2:

Octane now has some interesting improvements:

  • Multi-threaded scene compiling
  • Significantly improved rendering performance
  • Volumetric fog and lightshafts (very nice!)
  • Customizeable sky/sunset color and sun size
  • Dirt texture
  • Panoramic cameras (spherical and cylindrical)
  • Customizeable bokeh DOF
  • Lens distortion
  • Raytraced wireframe mode

Current version 1.1:

Bloom and Glare are now available. A new daylight system has been implemented, HDRI importance sampling to get a somoother result, shadow catchers and orthographic cameras are now available.

Current version 1.0 final:

Very interesting: The renderer is implemented as a plugin renderer for most premium 3d applications like 3dsmax, maya, softimage, lightwave, cinema4d.

Current version 1.0 beta2.46b:

3dsmax plugin released. There are a few constraints. e.g. it seems that you cannot manipulate the geometry after sending to the renderer because the current workflow moves the geometry to the GPU and modifies buids a acceleration structure there. That means any geometry manipulation would require a new translation. They have some impressive videos about the workflow on youtube, have a look at it.

 

 

Last Updated on Saturday, 21 September 2013 14:40