Goldorak wrote:Next steps as:
1) Add the final AOV in Octane core for full Altus support (working on this now)
2) Release a sample ORBX scene with the needed render layers already set up, once (1) above is working.
3) Shortly after (2) is out, release (maybe built in to Octane) a render job script node that can create the two frames+needed AOVs from an existing render target (connected via an input pin), which can also launch Altus after all output is completed by the job node. This can further be used for animations, and easily hooked up in plug-ins that support script nodes (even invisibly). Some work needs to be done around memory usage and GPU sharing, but this could be exposed in the node settings as well.
4) Once (3) above is working for users locally, and is confirmed to be stable, we will then work an the ORC version of this node to automate denoising for cloud rendered images/animations in a way that matches the local workflow.
5) Work with Innobright on license tailored for Octane users that works across local/network/ORC jobs. TBD - input is very welcome on pricing and usage expectations different than what is offered right now.
Users browsing this forum: Google [Bot] and 28 guests