From: Greg Ercolano <erco@(email surpressed)> Subject: New Rush 102.42a8 released Date: Fri, 16 Feb 2007 12:28:52 -0500 |
Msg# 1479 View Complete Thread (3 articles) | All Threads Last Next |
Hi All,
Rush 102.42a8 was released on 02/15/2007 -- upgrade is Free
to all existing customers. You can use your existing license files.
Go here to take the free upgrade:
http://www.seriss.com/rush/upgrade-102.42a8/
Or see the new main page (you may need to hit "reload")
http://www.seriss.com/rush/
102.42a8 Highlights
-------------------
o A critical OSX fix was included that caused the rushd.log on some
Mac machines to grow very large very quickly. The cause is a bug in
the OS itself; the fix was a workaround for that OS bug.
o A small modification was added to the Windows version of Rush
to support Microsoft Vista.
o IRUSH has a new 'search filter' making large reports more manageable.
Short demo here: http://seriss.com/rush/flash/irush-report-demo.html
o All submit scripts now have a new file chooser option:
Edit -> Preferences -> Use native filechooser
When enabled, this flag turns on the local OS's own file chooser for
the 'Browse' buttons in the submit forms, so you can use the OS's own
native browser to find scene files.
o submit-maya now has:
> An optional Project: directory prompt
> New "-field" command line options lets you preset fields in the
submit form from the command line. See 'submit-maya -help' for more.
> New 'mi-gen' option lets you generate just the MI files
(either incremental, or one-file-per-frame MI files) without rendering.
o A new 'submit-harmony' script was added so that ToonBoom/US Animation
"Harmony" software can work well with Rush. "Harmony" is popular
with 2D animation companies for managing traditional animation. This
script is actively being used in production on the new Simpson's movie.
o All program's help screens now have selectable text, so you can paste
directly from the help screens.
o Added maya 8.5 and 8.0 example variable settings.
o Linux install script now creates /etc/profile.d/rush-render-queue.{csh,sh}
files, instead of directly hacking /etc/profile and /etc/csh.{cshrc,login}.
o Fixed problem where some windows machines would not show up in rushtop
because of the error:
PdhValidatePath('\Memory\Pages Input/sec'): The specified object is not found..
|
From: Dan Murray <dmurray@(email surpressed)> Subject: Re: New Rush 102.42a8 released Date: Wed, 28 Feb 2007 11:02:57 -0500 |
Msg# 1489 View Complete Thread (3 articles) | All Threads Last Next |
Hi Greg;I'm wondering if there's a way to restore the state of the queue prior to the upgrade? That is, once the upgrade is done and a user starts iRush, I'd like them to be able to see their old jobs. The main reason for this is that typically, the upgrade is done early in the morning or on the weekend. If a user had jobs in the queue running the night before, they can't check the status of the job via iRush if the logs are all cleared. If this is dangerous or bad practice to try and do this, I'll accept that but as stated, I'd prefer to restore the system state prior to the upgrade. Thanks, Dan Greg Ercolano wrote:
|
From: Greg Ercolano <erco@(email surpressed)> Subject: Re: New Rush 102.42a8 released Date: Wed, 28 Feb 2007 15:20:00 -0500 |
Msg# 1490 View Complete Thread (3 articles) | All Threads Last Next |
Dan Murray wrote: I'm wondering if there's a way to restore the state of the queue prior to the upgrade? That is, once the upgrade is done and a user starts iRush, I'd like them to be able to see their old jobs. It depends on what version you're upgrading from. (Sometimes the file format of the caching files changes.) The files to preserve would be everything in the rush/var directory. Assuming you preserve those files, you will probably be able to resurrect the old jobs. Do this on each machine you upgrade. You can just copy these files over from the 'renamed away' version; copy them over just before starting the daemon (ie. *after* running the install script) *Under Windows* be sure the permissions on these files (after you copy them) are read/writable to all users, eg: c:\rush\etc\bin\install.bat <-- first run the install script copy \rush.old\var\* c:\rush\var <-- copy over the files cacls c:\rush\var\* /e /c /g everyone:f <-- open the perms net start rushd <-- start the daemon If you have any trouble, please follow up here. If this is dangerous or bad practice to try and do this, I'll accept that but as stated, I'd prefer to restore the system state prior to the upgrade. I can say that it's for sure unsafe if you jump from 102.41 -> 102.42. But if you're moving from 102.42a -> 102.42a8, its 'probably' fine. -- Greg Ercolano, erco@(email surpressed) Rush Render Queue, http://seriss.com/rush/ Tel: (Tel# suppressed) Fax: (Tel# suppressed) Cel: (Tel# suppressed) |