Weekly Dev update [02/02/2017] Tweet

[BK]

Hey guys


Thanks heaps for your feedback, so please keep it posting.
Our latest OctaneRender for Maya 3.05.3 - 9.34 Octane Lens Shift is now linked to Camera Film Offset.

Here is a quick post on our progress since last weekly update.


OctaneRender for Maya 3.05.3 - 9.34

Implemented support of Maya's camera film offset. It is now used instead of Octane's lens shift.
Fixed issue with disabling network rendering in batch mode.


OctaneRender for Maya 3.05.3 - 9.32

Minor fixes and improvements...


OctaneRender for Maya 3.05.3 - 9.31

Improved gradient nodes to not assume the first non-existing color array element (lost in previous versions after saving) to always be black. It will still be assumed black when opening the previous versions scenes, and converted automatically to an explicit black first color element (which now will not be lost after saving). Now gradient nodes are resistant to screwing up position values of different elements.
+ One more quick-fix: messing with position values when IPR is active is more robust now.
Minor fixes and improvements...

OctaneRender for Maya 3.05.3 - 9.29

Quick fix: gradient node UI regression.


OctaneRender for Maya 3.05.3 - 9.28

Batch rendering mode now disables Octane network rendering if Octane is not chosen a scene renderer.
Implemented the ability to connect textures to Octane gradient nodes.
Minor fixes and improvements...


OctaneRender for Maya 3.05.3 - 9.27

Fixed gradient texture bug.


OctaneRender for Maya 3.05.3 - 9.26

Quick follow-up release: improved the new "use all GPUs" functionality; cleaning up UI...
Other changes here: viewtopic.php?f=109&t=58846


OctaneRender for Maya 3.05.3 - 9.25

Implemented extended GPU settings support.
Minor fixes and improvements...


OctaneRender for Maya 3.05.3 - 9.24

Added region feather border width to render settings.
Added "Use all GPUs" switch.
Minor fixes and improvements...


OctaneRender for Maya 3.05.3 - 9.23

Quick fix release: one more region render bug fixed.
Other changes here: viewtopic.php?f=109&t=58787


OctaneRender for Maya 3.05.3 - 9.22

Relaxed the requirement of unique transform names for Maya versions including and later than 2016.
Fixed the region rendering bug.



**Octane Standalone Update**

Changes since version 3.05.2 to Standalone version 3.05.3

Fixed texture environment mapping when X axis translation is set to anything different from zero (see viewtopic.php?p=300203#p300203 ).
Fixed a crash when setting any displacement texture UV transform scale component to zero (see viewtopic.php?f=86&t=58483 ).
Fixed a regression in the box mapping of 3.05.1.

[itsallgoode9]

Thanks for all the updates over the past couple months. Support has been much improved from where we were!

Any chance you can give us a bit of a looking forward roadmap? Are all the features from standalone implemented in Maya Plugin now? Are there new maya specific workflow features that are being worked on or is it basically minor bug fixing until 3.1 comes out?

[BK]

@ itsallgoode9

Any chance you can give us a bit of a looking forward roadmap? Are all the features from standalone implemented in Maya Plugin now? Are there new maya specific workflow features that are being worked on or is it basically minor bug fixing until 3.1 comes out?

very good questions? Yes, we have a roadmap for Octane and plugins. So, please stay with us !!
Technically yes, we are trying to implement the Standalone feature in Octane Maya plugin. If any request please post on the forum or feel free to PM me.
Currently, there is no new Maya workflow, it was just an improvement step to make easier for Artist.

thanks J

[haze]

We will have a better idea of the roadmap in general in a couple of weeks, but we intend to focus on features such as support for XGen, Bifrost and PhoenixFD 3.0, and also UX - with an emphasis on the latter.

[calus]

We will have a better idea of the roadmap in general in a couple of weeks, but we intend to focus on features such as support for XGen, Bifrost and PhoenixFD 3.0, and also UX - with an emphasis on the latter.

Please consider as a priority to add the "ORBX proxy" feature to the Maya plugin : viewtopic.php?f=111&t=58521
This would solve many issues :
- a solution for some missing Octane features, half implemented features or broken features in the Maya plugin.
- a way to solve at once many different Maya user's requests.
- a workaround/solution for several bugs, for example this one : viewtopic.php?f=110&t=55917

This feature is implemented in the Modo plugin the way I expect it to be initially implemented in Maya :
https://docs.otoy.com/#modo-v3-orbx-proxy-files

ORBX Proxy Files
A Modo Mesh Item can be replaced in the Octane Viewport by an Octane OCS or ORBX files geometry. To do this, specify the OCS or ORBX file in the Mesh->Octane Mesh->Proxy Filename. You can still transform the Mesh and the position, scale and rotation will be applied to the proxy.
The OCS/ORBX file used as a proxy must has a single disconnected Mesh item in the scene, or must have a geometry object plugged into a Rendertarget node, or it must has a Geometry Out node, so that the plugin can determine which geometry to render as the proxy.
The Modo timeline is applied to the OCS/ORBX proxy, so if there is an animated mesh in the proxy, it will be rendered as per the current Modo timeline.