From: Greg Ercolano <erco_mlist@(email surpressed)> Subject: Cinema 4D R16: how to update your submit-cinema4d.pl scripts for new command line rendering Date: Sat, 15 Apr 2017 14:13:07 -0400 |
Msg# 2409 View Complete Thread (2 articles) | All Threads Last Next |
Wow, cool, Cinema 4D finally made a console mode command line renderer, making things much better for distributed rendering with C4D. This is great; so if you're using Rush + Cinema 4D rendering, and are on C4D R16 (or higher), I suggest you make the following simple one line change to your submit-cinema4d.pl render scripts to take advantage of C4D's new "commandline.exe" renderer. At the top of your submit-cinema4d.pl script, find this line: $G::C4D_COMMAND = "start /b /wait \"parentconsole\" \"${G::C4D_DIR}\\CINEMA 4D.exe\""; ..and change it to read instead: $G::C4D_COMMAND = "\"${G::C4D_DIR}\\Commandline.exe\""; That's it. This should really improve execution of the renderer, and will allow the renderer's output to appear in the frame logs (finally!), allowing better error reporting, offer real time progress, etc. Example output showing this new renderer command line, highlighting that you can now see error output and progress info. _______________________________________________________________________________ ### ### tahoe.46: 0055 ### --------------- Rush 103.07 -------------- -- Host: render007 -- Pid: 19388 -- Title: ARM_OXI_PAK_TEST -- Jobid: tahoe.46 -- Frame: 0055 -- Tries: 1 -- Owner: johndoe (-/-) -- RunningAs: rush (100/100) -- Priority: 1 -- Nice: 10 -- Tmpdir: C:/TEMP/.RUSH_TMP.10 -- LogFile: //server/projects/arm/shot/arm_files/pack_render.c4d.log/0055 -- Command: perl //server/library/scripts/rush/perl/submit-cinema4d.pl -render //server/projects/arm_files/pack_render.c4d.log/submitinfo.in -- Started: Thu May 22 12:00:29 2014 -------------------------------------------- Cinema 4D File: //server/projects/arm/shot/arm_files/pack_render.c4d Output Images: Output Format: default Output Resolution: default Multipass Output Path: Threads: default Submit Info: //server/projects/arm_files/pack_render.c4d.log/submitinfo.in Batch Frames: 5 (55-59) Retries: 3 (Fail after 3 retries) MaxLogSize: 0 Path: c:\Program Files\MAXON\CINEMA 4D R18;c:\rush/bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Python27;c:\rush\bin; Executing: "c:\Program Files\MAXON\CINEMA 4D R18\Commandline.exe" -nogui -render //server/projects/arm_files/pack_render.c4d -frame 55 59 Application start : 05/22/14 at 12:00:29 Executable : 64 Bit Version / Build : 18.041 / RB190167 Debugger : not available Memory model : release Startup path : c:/Program Files/MAXON/CINEMA 4D R18 Application path : c:/Program Files/MAXON/CINEMA 4D R18/Commandline.exe Application executable : c:/Program Files/MAXON/CINEMA 4D R18/Commandline.exe [..snip..] Cpu Speed (MHz) : 2600.000 Application Type : Modular Command line arguments : "-nogui" "-render" "//server/projects/arm_files/pack_render.c4d" "-frame" "55" "59" Loading c:/Program Files/MAXON/CINEMA 4D R18/modules/c4dplugin.xdl64 with module(s) net.maxon.c4dplugin [..snip..] -------------------------------------------------------------------------------- Loading Project: //server/projects/arm_files/pack_render.c4d [..snip..] Rendering frame 55 at <Thu May 22 12:00:33 2014> Rendering Phase: Setup Progress: 0% Rendering Phase: Main Render Progress: 0% Progress: 2% [..snip..] Progress: 90% Progress: 92% Progress: 95% Rendering Phase: Finalize Rendering successful: 384.829 sec. --- CINEMA4D SUCCEEDS: EXITCODE=0 |
From: Greg Ercolano <erco_mlist@(email surpressed)> Subject: Re: Cinema 4D R16: how to update your submit-cinema4d.pl scripts Date: Thu, 24 Aug 2017 17:43:35 -0400 |
Msg# 2410 View Complete Thread (2 articles) | All Threads Last Next |
On 04/15/17 11:13, Greg Ercolano wrote: > Wow, cool, Cinema 4D finally made a console mode command line renderer, > making things much better for distributed rendering with C4D. > > This is great; so if you're using Rush + Cinema 4D rendering, > and are on C4D R16 (or higher), I suggest you make the following > simple one line change to your submit-cinema4d.pl render scripts > to take advantage of C4D's new "commandline.exe" renderer. > > At the top of your submit-cinema4d.pl script, find this line: > > $G::C4D_COMMAND = "start /b /wait \"parentconsole\" \"${G::C4D_DIR}\\CINEMA 4D.exe\""; > > ..and change it to read instead: > > $G::C4D_COMMAND = "\"${G::C4D_DIR}\\Commandline.exe\""; I should add, with this change, rushd can be configured normally as a service, and C4D renders will run properly. This didn't used to be the case; the older versions of c4d couldn't be run from a service. So with the newer C4D versions, you are no longer required to run rushd as a non-service (such as from an autologin DOS window). |