OctaneRender_for_Maya_4.0-13.18 - [ OBSOLETE ] Tweet

[BK]

Otoy® is proud to announce the availability of a new version of OctaneRender™ for Maya® Version 4
The world's fastest and most feature-rich unbiased render engine that integrates completely into Autodesk® Maya®.

Maya® Version Requirements

This release will work with Maya® Versions 2016, 2016.5, 2017 and 2018 64-bit on MS Windows operating systems.

License upgrade

Unless you have a subscription license, you will have to upgrade your version 3 licenses to version 4. This upgrade is free and can be done via these 4 steps:

1. Go to https://home.otoy.com/render/octane-render/purchase/
2. Select "Upgrade" in the top menu.
3. Click on "UPGRADE NOW" next to "Upgrade existing licenses to OctaneRender 4".
4. Select the licenses you want to upgrade and confirm.

To use this version, you need a GPU of compute model 3.0 or higher. Support for Fermi GPUs (like GTX 4xx and 5xx) has been dropped. Also make sure you use a driver of version 387 or higher and if you are working on Mac OS that have a CUDA driver installed that supports at least CUDA 9.1.


Changelog for Octane Standalone 4.0RC7 & installer here:
OctaneRender Standalone 4.00

Please read the new features implemented from Octane Standalone 4 version our blog post.


=============================================
NEW FEATURES OF THE REFACTORED VERSION
=============================================

• - Fully reworked the internal scene and animation processing, to make it conformant with nowadays Octane engine's capabilities ('cause engine's structure changed significantly since the initial development of the plugin). Now the processing is more efficient, scalable, and more easily extendable by new complex features.
  
• - Parts of Octane global settings are now re-implemented as separate Maya nodes' links (you can have many of these nodes in the scene, and use them as presets):
  1. Kernel node.
  2. Passes node.
  3. Imager node.
  4. Postprocessor node.
  5. Environment node.
  6. Environment node used for Visible Environment.
  7. Render Layer.
  
• - Implemented the new caching scene translation mechanism. Keep in mind the new global setting "Frames to pre-cache" in Octane global settings. This setting allows to set up the frames span to be pre-loaded. New plugin structure now allows to pre-load the chosen animation span into Octane engine, only changing the current frame after that when you move the animation slider or progress towards batch rendering sequence. Without reloading the data every time (if no objects were changed). This allows to only fully translate the scene before the very first rendering session, and re-translate only changed objects after that, even when changing the current timeline position within this span range. For interactive mode this span will evenly surround the current frame, dynamically adapting to the current frame position and the length of the timeline. E.g. for value of 100: 50 frames before and 50 after the current timeline position if there are enough frames around the current frame. For the frame 5 on the [0:200] timeline - 5 frames before and 95 after. For the frame 5 on the [0:10] timeline - 5 frames before and 5 after. Etc. For batch rendering it will pre-cache only the frames after the current time. When the current frame pointer goes beyond the currently loaded frames span, the span gets re-loaded basing on the current frame pointer position. If your animation is long and heavy, and you are getting errors about out of GPU memory - then lower this setting. If you working on a still image or just one current frame for a long time - setting this value to "0" will speed-up the re-translation phase of rendering when objects are getting changed.
  
• - After the first render is started (the scene data gets loaded), all subsequent renders will not reload the scene again and the render will start immediately. Only the objects that were changed will be reloaded, if any. If you want to force-reload them all (interactively) - use the "Reload" button of Maya's render view. Thus you only will experience the longer delay before rendering starts during the very first start of rendering session (if nothing significant was changed in the scene between sessions or course).
  
• - Improved the performance of batch rendering. If "Frames to pre-cache" setting is set to high value - you will experience longer delay before the first frame starts rendering, but all subsequent frames will be rendered much faster, without re-translation of the scene for every frame...
  
• - The geometry type attribute is now not needed with the new plugin structure. The plugin now tries to determine if an object is animated or not. For the cases where the plugin was not able to recognize it - there is a new "Animator data" setting in the objects, which allows to force the animation data of the object to be loaded or not loaded into the engine.
  
• - Implemented the new more flexible objects' sampling mechanism. See the new "samples per frame" settings in both global and object's settings. Usable to smooth the motion blur of only chosen fast moving objects. If object's setting is "0" - then the global setting is used for this object.
  
• - Implemented the new "ORBX material" node. Those who like to work directly with Octane shading nodegraph can now define the whole shading tree inside this material node (or import it from ORBX or OCS file), and use it the same as any other Octane material nodes in Maya scene...
  
• - Implemented the new "ORBX proxy" node. Those who like to work directly with Octane nodegraph can now define the whole geometry with its shading tree inside this node (or import it from ORBX or OCS file).
  
• - "Unpack ORBX resources" global setting controls how the resources of imported ORBX files are handled. If set, when importing ORBX files into ORBX materials and proxies - the internal resources (if any) will be unpacked into separate files which will be referenced by imported nodes directly. Otherwise - the imported nodes will have references to the imported ORBX file (which in this case will be automatically copied into "assets" section of Maya project during import).
  
• - Script graph materials are now imported from LiveDB as ORBX material nodes.
  
• - Implemented Octane rendering directly into Maya viewport (Maya 2016.5 and above). Now you can run Octane rendering session directly inside Maya viewport. You need to select the new "OctaneRender" mode in "Renderer" menu to start Octane session inside the viewport. Settings for that mode are available by selecting the square icon next to "OctaneRender" item in "Renderer" menu. Octane engine allows you to have only one rendering session active, so only one viewport can have active rendering session inside it. If you start IPR rendering inside Maya's RenderView - this will take over the session from the active viewport. After stopping the IPR session - the session will be returned back to viewport.
  
• - Maya camera's image plane is now translated into rendered image's background. You need alpha channel setting enabled and "keep environment" setting disabled for that have any effect on the image being rendered.
  
• - Implemented preview swatches for all Octane textures.
  
• - Implemented the new "Max. MV displace" setting in geometry objects. This sets the max. displace value for normalized motion vectors loaded into the object's MV channel.
  
• - Implemented the new normals-autosmooth settings for geometry objects.
  
• - Reworked output image formats setup UI in global settings.
  
• - Integrated the Stable 4.0 rendering engine, implemented its feature-set support. New OSL nodes, OSL camera, etc...
  
• - Implemented uploading of the current scene to Octane cloud directly from inside Maya (menu "Octane -> Upload to Octane cloud").
  
• - Implemented saving of render state of IPR and Interactive modes. If render was going on for time period more than set threshold ("State save threshold" in Octane global settings, in munutes), then after stopping the render you will be offered to save the render state. Next time when IPR or Interactive rendering is started (even after Maya or computer reload), if there is a saved render state for that scene, you will be offered to continue with the saved state or start rendering from scratch. This way you can e.g. start rendering in IPR session, then if you liked the result, stop it (saving render state), and later continue with this state in Interactive rendering session.
  
• - Implemented indication of GPUs used for OS display (Windows only so far). It's better to avoid using these for rendering.
  
• - You can now render several Octane layers in one batch render session - just specify the comma-separated list of layer numbers in Octane global "Batch render layers" setting.

Changes since the OctaneRender_for_Maya_4.0RC7_-_13.16-STABLE:

- Quick fix on GPU setting in CUDA tab for demo versions.

Known issues:
- Octane engine has a bug with scene export. Mostly the scene export will work correctly, but in some special cases some file attributes of some nodes could be linked to non-existing files.
- Maya API's native UI gradient control is not flexible enough to support Octane data type for gradient texture UI, so this node still has "color-array-like" UI. I'll look into possible workarounds for it later. You can use Octane ORBX material if you like to use the native Octane UI gradient control.
- Autodesk developers are working on a new context-driven API for plugins. It started with Maya 2018, and in theory it must dramatically improve the scene translation performance for Octane when this API gets completed and polished. But in current state it is just partially implemented, and even those parts implemented are buggy and do not work correctly (even lead to Maya crashes sometimes when the plugin tries to use this new API).
So, Octane plugin now uses this new API whenever it is possible, but only in aspects where it works correctly. It already allowed to eliminate scrolling the timeline back and forth during scene translation for some particular objects that did not support context-driven data output earlier. But some Maya objects (like nHair for example) still don't support any kind of context-driven data output - neither old approach nor the new Autodesk API. And some objects which now (with Maya 2018) show some signs of starting to be supported by the new API (like e.g. instancer) - still don't work correctly with the new API and even crash in some cases.
Thus for now: for the scenes having such objects in them, expect the timeline is still scrolled back and forth during translation of the scene (this happens only when "Frames to pre-cache" is set to some noticeably-high value and only during the first translation or when such objects got changed during rendering session). This does not affect the rendering quality, it is mostly the matter of visual attraction of how Maya API supplies the plugin by objects' data from different time-contexts...
- Maya has few matrix data bugs in its API happening when moving a camera in a viewport. Currently, I've implemented workarounds for Octane to make it work properly, but it might slightly lower the efficiency of movements during viewport rendering session. Autodesk confirmed these bugs after I reported them. So after they fix it - Octane will work even more efficient in the viewport rendering mode.


Windows DOWNLOAD
OctaneRender for Maya 4.0 - 13.18
OctaneRender for Maya 4.0 - 13.18 Demo

Linux DOWNLOAD
OctaneRender for Maya 4.0- 13.18
OctaneRender for Maya 4.0- 13.18 Demo


MacOSx DOWNLOAD
OctaneRender for Maya 4.0- 13.18
OctaneRender for Maya 4.0- 13.18 Demo



=====================================
Subscription Studio Downloads
=====================================

OctaneRender for Maya Studio V4.0-13.18 [Windows]

OctaneRender for Maya Studio V4.0-13.18 [MacOS]

OctaneRender for Maya Studio V4.0-13.18 [Linux]

[teammach]

dear octane team,

we are using octane since version 2.x here as a production renderer. unfortunatly since the very beginning motionblur was a big issue in octane.

It is not possible to get a proper motionblur on like spinning wheels. Even in this new 4.0 release motionblur it still fu#%ed.

The entire wheel is getting bigger or smaller and blurry all over the place...

We are working in the automotive business...motionblur on wheels is essential! there must be a way

please see attachments for what i mean.

[Refracty]

Yeah, that's a big problem of the Maya plugin. We need to render parts of the scenes with 600 fps to minimize those problems.
I can't understand why it is still in there.

dear octane team,

we are using octane since version 2.x here as a production renderer. unfortunatly since the very beginning motionblur was a big issue in octane.

It is not possible to get a proper motionblur on like spinning wheels. Even in this new 4.0 release motionblur it still fu#%ed.

The entire wheel is getting bigger or smaller and blurry all over the place...

We are working in the automotive business...motionblur on wheels is essential! there must be a way

please see attachments for what i mean.

[leehenshall]

Is this issue isloated to Maya plugin only? I'm having some movement even in my standalone scene. The wheels are animated over 100 frames but maybe that's not enough frames still.

I'm still slightly baffled as to why Octane makes animating motion blurred wheels a problem. Motion blur should just be a checkbox and it should react to real world values on both animation speed and camera settings (f-stop, shutter speed etc)

[Jolbertoquini]

dear octane team,

we are using octane since version 2.x here as a production renderer. unfortunatly since the very beginning motionblur was a big issue in octane.

It is not possible to get a proper motionblur on like spinning wheels. Even in this new 4.0 release motionblur it still fu#%ed.

The entire wheel is getting bigger or smaller and blurry all over the place...

We are working in the automotive business...motionblur on wheels is essential! there must be a way

please see attachments for what i mean.

This is setting issues Guys is not explained well basically add subsamples at 10 should be fine for that. at Render settings "frames to pre-cache" set "0" default samples per frame set "10" we are rendering a lot car here is working pretty well if you have a really fast Motionblur maybe add extra subsamples like 20 but is not nescessary.

One thing to keep in mind if you want change the time line while doing IPR here a problem you need set the "frames to pre-cache" the amount of frame on you shot let's say animation 1-120 set "120" and then you can change time line this is cool but not fine with heavy scenes so set 0 and restart iPR before change frames.

Cheers,
JO

[Jolbertoquini]

Yeah, that's a big problem of the Maya plugin. We need to render parts of the scenes with 600 fps to minimize those problems.
I can't understand why it is still in there.

dear octane team,

we are using octane since version 2.x here as a production renderer. unfortunatly since the very beginning motionblur was a big issue in octane.

It is not possible to get a proper motionblur on like spinning wheels. Even in this new 4.0 release motionblur it still fu#%ed.

The entire wheel is getting bigger or smaller and blurry all over the place...

We are working in the automotive business...motionblur on wheels is essential! there must be a way

please see attachments for what i mean.

Not need anymore "default samples per frame" is there for that!

[leehenshall]

Is it possible to add support for 2d pan zoom and filmback settings?

[calus]

@teammach, @Refracty and @ leehenshall

Hey guys, I'm not sure if you are aware of the new per object motion-blur subframe sampling feature in the new Maya plugin :

Motion blur interpolation is always linear in Octane = no rotation motion-blur, so more transformation samples are needed for proper rotation motion-blur,
this can be done in the Maya plugin now by increasing the "sample per frame" attribute of the transform node with the rotation animation.

Also there are still some weird motion-blur bugs when you have a baked camera animation supposed to follow exactly the motion of the car,
but this is not the same problem I guess, more a precision issue when the plugin translate animation of the camera and car to octane (the easy workaround is to just parent the camera under the animated car transform).

[leehenshall]

Thanks,

I didn't know O4M had this control......it looks very similar to geometry samples in V-Ray.

Do you know where can I find this feature in standalone?

[teammach]

dear octane team,

we are using octane since version 2.x here as a production renderer. unfortunatly since the very beginning motionblur was a big issue in octane.

It is not possible to get a proper motionblur on like spinning wheels. Even in this new 4.0 release motionblur it still fu#%ed.

The entire wheel is getting bigger or smaller and blurry all over the place...

We are working in the automotive business...motionblur on wheels is essential! there must be a way

please see attachments for what i mean.

This is setting issues Guys is not explained well basically add subsamples at 10 should be fine for that. at Render settings "frames to pre-cache" set "0" default samples per frame set "10" we are rendering a lot car here is working pretty well if you have a really fast Motionblur maybe add extra subsamples like 20 but is not nescessary.

One thing to keep in mind if you want change the time line while doing IPR here a problem you need set the "frames to pre-cache" the amount of frame on you shot let's say animation 1-120 set "120" and then you can change time line this is cool but not fine with heavy scenes so set 0 and restart iPR before change frames.

Cheers,
JO

damn, you are totally right. that fixes the problem! how coud i have not seen it...thx man