NUKE Plugin - progress update
Posted: Thu Sep 18, 2014 2:27 amNUKE plugin - progress update with video
The OctaneRender for Nuke plugin is well progressed, so we have posted a video showing the work to date (please excuse the sound quality).
The main features of the plugin are:
- Rendering of an imported OCS or ORBX file exported from one of the other Octane plugins, or from Octane Standalone. This includes rendering of the correct form from the ORBX/OCS (where there is an alembic animation in the ORBX/OCS).
- Rendering of all the passes available in Octane 2.10. These passes can be used as you would use any pass from a multi-layer EXR/PNG in Nuke. Info passes are rendered prior to beauty passes.
- Rendering of the Nuke 3d scene (ie. replacement of the Nuke Scanline renderer node). There is an addition Nuke node for Octane materials, which can be plugged into the Nuke 3d scene object so that the Octane material for that geometry can be assigned. Geometry can be subdivided using the existing Octane subd features.
- Tracking of the Nuke camera - plug the Nuke camera node into the Octane Render node, and the Octane camera position will be synchronized to the Nuke camera (incl for animations)
- Rendering animations - this is still be to worked out, since each frame of the animation will need to be rendered in the Octane node to when the Max Samples are reached. Most probably this will be implemented by having the Octane node manage the rendering of the animation, rather than using the Nuke "Render All" function.
- There may be an option to edit the Octane materials from an imported OCS/ORBX, and in particular assign a Nuke image sequence to an Octane Image node. The viability of this is still to be determined.
- There will be a limit of one OctaneRender node in Nuke at any one time, since having multiple Octane scenes rendering simultaneous may cause issues.
- A python interface is being considered, so that Octane nodes from the imported OCS/ORBX can be queried and edited via python. The viability of this is still to be determined.
We welcome feedback for other features that will be useful additions to the plugin.
The OctaneRender for Nuke plugin is well progressed, so we have posted a video showing the work to date (please excuse the sound quality).
The main features of the plugin are:
- Rendering of an imported OCS or ORBX file exported from one of the other Octane plugins, or from Octane Standalone. This includes rendering of the correct form from the ORBX/OCS (where there is an alembic animation in the ORBX/OCS).
- Rendering of all the passes available in Octane 2.10. These passes can be used as you would use any pass from a multi-layer EXR/PNG in Nuke. Info passes are rendered prior to beauty passes.
- Rendering of the Nuke 3d scene (ie. replacement of the Nuke Scanline renderer node). There is an addition Nuke node for Octane materials, which can be plugged into the Nuke 3d scene object so that the Octane material for that geometry can be assigned. Geometry can be subdivided using the existing Octane subd features.
- Tracking of the Nuke camera - plug the Nuke camera node into the Octane Render node, and the Octane camera position will be synchronized to the Nuke camera (incl for animations)
- Rendering animations - this is still be to worked out, since each frame of the animation will need to be rendered in the Octane node to when the Max Samples are reached. Most probably this will be implemented by having the Octane node manage the rendering of the animation, rather than using the Nuke "Render All" function.
- There may be an option to edit the Octane materials from an imported OCS/ORBX, and in particular assign a Nuke image sequence to an Octane Image node. The viability of this is still to be determined.
- There will be a limit of one OctaneRender node in Nuke at any one time, since having multiple Octane scenes rendering simultaneous may cause issues.
- A python interface is being considered, so that Octane nodes from the imported OCS/ORBX can be queried and edited via python. The viability of this is still to be determined.
We welcome feedback for other features that will be useful additions to the plugin.
