Here's a summary of newsgroup items that I find myself referring
people to often via email:
* OPEN SUBMIT-MAYA FORM WITHIN MAYA [edit: 04/21/2012]
MEL APPROACH (userSetup.mel)
----------------------------
You can set up Maya so that artists can bring up the
'submit-maya' form from within Maya's 'Rendering" menu bar:
http://seriss.com/cgi-bin/rush/newsgroup-threaded.cgi?-view+1631
Basically, a modification to the scripts/startup/userSetup.mel
PYTHON APPROACH (userSetup.py)
------------------------------
If you want to use the python equivalent for "userSetup.py", see:
http://seriss.com/cgi-bin/rush/newsgroup-threaded.cgi?-view+1951
For the entire thread on this subject, see:
http://seriss.com/cgi-bin/rush/newsgroup-threaded.cgi?-view+1631+1631+1632+1633+1634+1635+1636+1637+1638+1778+1951
* OPEN SUBMIT-AFTERFX FORM WITHIN AFTER EFFECTS
You can set up After Effects so that artists can bring up the
'submit-afterfx' form from within AE's File menu:
http://seriss.com/cgi-bin/rush/newsgroup-threaded.cgi?-viewthread+2113+2359
* OPEN SUBMIT-NUKE FORM WITHIN NUKE
http://seriss.com/cgi-bin/rush/newsgroup-threaded.cgi?-viewthread+1971+1972+1973+1974+1991+1992+1993
[Updated: 07/08/12 -ed]
* USING MAYA + VRAY WITH RUSH
There are a few techniques to get old submit-maya scripts to work
with Vray; see this thread for details:
http://seriss.com/cgi-bin/rush/newsgroup-threaded.cgi?-viewthread+1922+1933
* DETAILS ON RUSH'S "FIFO" SCHEDULING FEATURE
FIFO scheduling was introduced in 102.42a9, and a maintenance fix
in 102.42a9c made it stable for multiple job servers. There are some
details on how Rush's FIFO scheduling option works here:
http://seriss.com/cgi-bin/rush/newsgroup-threaded.cgi?-viewthread+1871+1872+1873+1874
* [OSX] SETTING UP NFS MOUNTS ON BOOT
Apple has many GUI ways to configure file server mounts, but
it's hard to automate, and has invisible behaviors that are sometimes
not appropriate for 24/7 operation. A better, more 'unixy' approach
is to make a boot script that runs regular mount(8) commands.
Such a script can then be easily distributed to all workstations/rendernodes
(with e.g. rsync(1) or scp(1)) to ensure consistent mount behaviors. More info here:
http://seriss.com/cgi-bin/rush/newsgroup-threaded.cgi?-view+1847+1847
* [OSX] SETTING UP A SMALL NFS NETWORK
If you are new to OSX, and need to get a small network of OSX
talking to each other, see this posting for details on setting up
a small OSX network using regular unix commands:
http://seriss.com/cgi-bin/rush/newsgroup-threaded.cgi?-viewthread+1295+1297+1298+1839
* [WINDOWS] DEALING WITH DRIVE MAPS
If you're using drive letters (instead of UNC paths), then you need
some way to make them work reliably, as they are erratic by design:
http://www.seriss.com/rush-current/rush/rush-td-faq.html#TDFAQ-UNC
If you *must* use drive letters, here's ways to force them to work:
a) With Maya, you can configure the MEL 'dirmap' command in the
Maya startup scripts to replace drive letters with UNC equivalents:
http://seriss.com/cgi-bin/rush/newsgroup-threaded.cgi?-view+1312
-- OR --
b) Configure the submit script to force drives to be mapped:
http://seriss.com/cgi-bin/rush/newsgroup-threaded.cgi?-view+1222
I've had several confirmations the (a) approach works well, and is likely
the best solution when maya is involved, as it ensures UNCs are actually used.
The (b) approach tries to force Windows to make drive maps work,
and will probably work 'most of the time', but using UNCs is best.
Note that in recent releases of Windows (Vista, Windows7), actual
working 'symbolic links' are now an option. For details on making
symlinks under windows, see this thread:
http://seriss.com/cgi-bin/rush/newsgroup-threaded.cgi?-viewthread+1553+1554+1555+1556+1557+1566
* CUSTOM 'DONEMAIL' MESSAGES FROM RUSH
Some folks like to configure custom email messages when a job finishes
so that they can email their pagers/cellphones with short, specific contents:
http://seriss.com/cgi-bin/rush/newsgroup-threaded.cgi?-view+1589
* USING EYEON'S "FUSION" WITH RUSH
Fusion 5.1 (and higher) can now be used with Rush:
http://seriss.com/cgi-bin/rush/newsgroup-threaded.cgi?-viewthread+1530
* HOW TO GET RUSH TO SEE "csh" STYLE ENVIRONMENT VARIABLE SETTINGS
Unless you are submitting CSH scripts, CSH settings in .cshrc files
will not be 'sourced' by the perl submit scripts. Here's some ways
to manage csh environment variables from within perl scritps:
http://seriss.com/cgi-bin/rush/newsgroup-threaded.cgi?-viewthread+1502
There are some other articles regarding user environment variables
with respect to network rendering; see:
http://seriss.com/cgi-bin/rush/newsgroup-threaded.cgi?-viewthread+1501+1502+1503+1506+1505+1504
Also, some details on how to pass environment variable info
from the user's environment during job submission to your render scripts:
http://seriss.com/cgi-bin/rush/newsgroup-threaded.cgi?-view+761+761
* [OSX] A COMPARISON OF AFP/SMB/NFS
Often people ask about whether they should use AFP or SMB or NFS on OSX.
The short answer is NFS. For details, see the following link that compares
the different network file systems:
http://seriss.com/cgi-bin/rush/newsgroup-threaded.cgi?-view+1062+1062
Also related: In Tiger, Apple broke AFP and SMB for multiuser access; see:
http://seriss.com/cgi-bin/rush/newsgroup-threaded.cgi?-viewthread+1013+1014+1015+1019+1020+1021+1024+1595
* HOW TO PARSE RUSH COMMAND LINE OUTPUT
Here are some examples and insights into parsing rush's output into
other scripting languages (including parsing error messages)
with examples in perl:
http://seriss.com/cgi-bin/rush/newsgroup-threaded.cgi?-view+1371+1371
* HOW TO MAKE CUSTOM VERSIONS OF SUBMIT SCRIPTS FOR OSX
This shows how to make a copy of a submit script with a different name,
and be able to open it from the Finder:
http://seriss.com/cgi-bin/rush/newsgroup-threaded.cgi?-viewthread+1378#1378
[Added 06/30/14]
[[ These items were culled from emails between me and customers via: ]]
[[ egrep seriss.com.cgi-bin.rush.newsgroup </path/to/my/mailbox> | sed 's/^[ \t]*//' | sort | uniq ]]
|