This should have already been set up by your sysadmin, or the person who installed the rush software:
This script will be executed not only by the user to bring up the submit-cinema4d GUI, but it will also be executed on all the render machines to run the renders.
To ensure the renders run with the proper environment, the systems administrator will need to add some lines at the top of the script to set this up. At minimum, you'll need to configure the PATH to the directory containing the executables.
In the following example, the blue lines show the Windows PATH, the red lines show the OSX path.. change the path's value as needed for your Cinema 4D installation:
############################################################## ### CINEMA 4D SPECIFIC VARIABLES -- CUSTOMIZE AS NECESSARY ### ### See Cinema 4D's documentation for more info. ### ############################################################## if ( $G::iswindows ) { # WINDOWS $ENV{PATH} = "c:/Program Files/Maxon/Cinema 4D;$ENV{PATH}"; } elsif ( $G::ismac ) { # OSX $ENV{PATH} = "/Applications/MAXON/CINEMA 4D R10.5/CINEMA 4D.app/Contents/MacOS:$ENV{PATH}"; } |
Cinema 4D may also depend on other variables; you can define them in this section.
Be sure the shortcut points to a copy on a file server, and not to local files in c:\rush\examples (windows) or /usr/local/rush/examples (unix).
Should be as simple as clicking on your desktop shortcut.
If you prefer using a terminal window, be sure to run the script with an absolute UNC path, eg:
perl //server/jobs/rushscripts/perl/submit-cinema4d.plIf you don't run it with an absolute path, the frames will fail because rush didn't have the absolute path to the submit script.
The interface should pop up. If it doesn't, verify (unix) the first line in the script's path points to the correct location of your perl binary, or (windows) the '.pl' extension is configured to correctly invoke perl.
Click the help button (buttons with '?') for any field you want to know more about.
When the GUI pops up, note there are various 'Advanced Options' available if you scroll the window down.
This should be an absolute path to your ".c4d" file. This path must be able to resolve on all the machines you'll be rendering on.
Under Windows, you should use UNC absolute pathnames, such as //server/jobs/LOGO/sc4a/cinema4d/sc4a.c4d
This is the range of frames you want to render; normally two values separated by a dash, eg. '1-100'.
You can also specify individual frames, multiple ranges, or cobinations of both, eg. '1 10 20-30 400-900', which would render frames 1, 10, 20 through 30, and 400 through 900.
In our case, lets use any 5 available cpus at the lowest priority:
+any=5@1
As the name implies, "Advanced Options" are optional. To see them, use the scroll bar to scroll down to check their settings.
Click the help button (buttons with '?') for any field you want to know more about.
This should submit your job, and a window indicating the jobid should pop up, followed by an irush interface with the jobid already set to the new job.
The next time you bring up the submit form, it will have all the values set from the last execution. Note that you can then save this as a form so you can easily recall it later.
For more info on the irush interface, see the irush tutorial.
Hit 'Frames' in irush to watch the progress of your job.
If some frames are running, or got done already, click on
some, and hit 'Logs' to see the output of the perl commands
you entered.
When you're finished with the job, hit 'Dump' in irush.