From: Greg Ercolano <erco@(email surpressed)>
Subject: New Rush 102.42a6 released
   Date: Tue, 13 Jun 2006 01:55:49 -0400
Msg# 1313
View Complete Thread (1 article) | All Threads
Last Next
Rush 102.42a6 was released today -- upgrade is Free to all customers.

Just contact me directly via email, erco [at] seriss.com from your
business email address, and I'll supply you with the download info
for the upgrade.

Feature highlights (with pretty pictures):
http://www.seriss.com/rush-current/features/

Detailed release notes (dry descriptions/no pretty pictures):
http://www.seriss.com/rush-current/rush/release-notes.html#102.42a6

Outstanding fixes/features:

    o rush -ljf bug that caused extra daemons on unix repaired

    o vfork() now used (unix) to prevent memory overhead on large job servers
      Useful for /large/ facilities with busy unix based job servers.

    o irush now warns about license expirations

    o 'rush -lah' shows warnings if there are too many hosts in the rush/etc/hosts file

    o Irush has resizable columns -- officially released
      (some of you have this already from previous updates or beta tests)

    o Submit-maya6 has some new features and detailed docs.

          o Floating point frame rendering
          o You can now mix Batch Frames and frame increments
          o RenderMan rendering
          o Improvements for MentalRay Standalone rendering with Batching
          o "Help" button (at bottom of submit-maya6 form) has details on how
            to use the multiple modes of submit-maya6.

    o submit-shake-quicktime now supports many new codecs, thanks to submitted
      data from one of the new Rush evalers.

** LINUX/OSX USERS **
   The 'rush -ljf' fix is an *important fix* for those of you have
   unix/osx machines as job servers, and use automated scripts for gathering
   data using 'rush -ljf'. This bug caused multiple rushd daemons to appear
   if the jobid argument to 'rush -ljf' no longer exists. The daemons would then
   fight each other over network messages, causing intermittent 'unknown jobid'
   responses when viewing jobs, and/or other oddities.

   Those of you sometimes noticing frames restarting themselves, or getting
   intermittent responses of 'unknown jobid' for your jobs should take this update
   to solve the problem.

Last Next