OTOY Forums

BK wrote:Hello!! Solomonfl & Rikk The Gaijin

We are working on 3.07sdk support for the current branch. We will get a test build out hopefully this week or early next week.

Cheers

Hi,BK
I am waiting for 3.08 ,my project need for Toon shading

Hi, Renma,


Sure !! When does your project start? The 3.08 SDK will be available after we release our refactored plugin branch.

BK wrote:Hi, Renma,


Sure !! When does your project start? The 3.08 SDK will be available after we release our refactored plugin branch.

Thanks ,BK
Next week my project will be start,the software render is so slow,and my renderfarm base on octane,so.....let 3.08 come soon

Thanks ,BK
Next week my project will be start,the software render is so slow,and my renderfarm base on octane,so.....let 3.08 come soon

Hi, Renma,

oh sorry..... next week is not quite possible because OSL implementation is another huge task, maybe a month or more. We plan to start 3.08 implementation after the refactored plugin is released.
Can the toon shading and rendering process be done in SA?

cheers

Hi.
In batch render (cmd) I get this message;
Warning: file: C:/Program Files/Autodesk/Maya2017/scripts/others/mayaBatchRenderProcedure.mel line 651: Renderer returned an error while rendering 'defaultRenderLayer', please verify the output image.
Scene Z:\TN_THE_NODE\TN_COMPO\TN_Maya3.0\scenes\TN_SEC08_Sepa_360\TN_SEC08_Sepa_360_05.mb completed.

I am using maya 2017 update 4. I have also tried exporting the scene to octane standalone, but when it starts to export, maya closes.
I do not know how to solve this, but I need a solution to finish this project.

Maskeline wrote:Hi.
In batch render (cmd) I get this message;
Warning: file: C:/Program Files/Autodesk/Maya2017/scripts/others/mayaBatchRenderProcedure.mel line 651: Renderer returned an error while rendering 'defaultRenderLayer', please verify the output image.
Scene Z:\TN_THE_NODE\TN_COMPO\TN_Maya3.0\scenes\TN_SEC08_Sepa_360\TN_SEC08_Sepa_360_05.mb completed.

I am using maya 2017 update 4. I have also tried exporting the scene to octane standalone, but when it starts to export, maya closes.
I do not know how to solve this, but I need a solution to finish this project.

Hi Maskeline,

My apology for the late response. Are you still having the same issue? Maya Command line render require setting the windows environment variable, please check this viewtopic.php?f=28&t=43908
Also, if there is any format string is used in the File Name Prefix parameter, please try removing.

Is it possible to email a sample scene file to investigate, you can delete/replace the geometries with simple primitives if they are copyright materials?

Cheers

Hi BK
thanks for the reply. I sent you a private message with the scene.
The environment variable is well set, but I will try to place only the file name and the render engine.

Maskeline wrote:Hi BK
thanks for the reply. I sent you a private message with the scene.
The environment variable is well set, but I will try to place only the file name and the render engine.

Thank you for sharing us the sample file. we have investigated and the command line worked and please use the export animated Orbx with v3.07-11.11[ viewtopic.php?f=109&t=64443].
Please check your PM.

I just get crashes when I render with Maya 2018.2 on macOS. Doesn't seem to be scene related. IPR works fine.

cgbeige wrote:I just get crashes when I render with Maya 2018.2 on macOS. Doesn't seem to be scene related. IPR works fine.

My apology for the late response. Currently, Octane engine SDK has a known issue with its callback system on OSX, during a batch render or render currently frame operation.
Our core team is aware of it and would be looking into this and resolve it as soon as possible.
So, as a workaround, we can use IPR to save out a single frame and if it's for animation, we would require exporting the whole scene as an ORBX format package which takes few minutes/secs then use Octane Standalone to batch render the scene.

Sorry for the inconvenience !!