![]() |
RUSH RENDER QUEUE - Rush Web GUI (C) Copyright 1995,2000 Greg Ercolano. All rights reserved. V 102.41 03/05/04 Strikeout text indicates features not yet implemented |
When you first connect to the www-rush server page, you see a panel containing several sub-panels of buttons. Pressing these buttons will let you view reports and otherwise control your job.
Reports will show up in a screen below the button panel, from which you can often make selections that let you focus on controlling individual elements in the report.
All the buttons in the upper panel affect the 'current jobid', which is shown in the upper right Jobid input field. (That is why all the buttons are grouped together in the black box) You can change the Jobid value at any time by just typing in a new jobid, and then selecting one of the buttons to control the new jobid.
The blank gray screen below is where the output of operations appears. Often, the system will let you click on report's text output, letting you control the selected items with buttons that would appear below the text window.
Assuming you have one or more jobs running, the first thing you'll want to do is set the Jobid in the Job Info subpanel, so you can work with it.
Another way to set the jobid is to hilight jobs from a Jobs report. The following shows you how to do that.
At very least, enter a hostname in the Jobid input window that is the name of your job server, then hit the Jobs button.
This will give you a report showing all the jobs being served by that machine. When the screen updates, you'll see a jobs report in the text window, followed by buttons that will let you control jobs.
Select the job you want to control by clicking on it in the text window, then hit the Set Jobid button below, to make that the new 'current job':
When the screen updates, the Jobid field will now show the 'va-222' jobid, and a message indicating the new jobid has been set.
When the screen updates, you will see a frame report for the job. Below that will be a series of 'Frame Control' buttons. By selecting frames from the frame list, you can use these buttons to change the frames selected.
As before, the buttons grouped below the text window all affect which ever items you select in the text window. Since this is a frame report, buttons relevant to controlling frames are shown.
In this case, all the frames are marked 'Done'. So we select a few of the frames, and requeue them by hitting the Queue button..
When the screen updates, it will show the output of the Queue operation.
Hit the Frames button, and a new frames report will appear.
Click on a few 'Fail' frames and hit the Logs button to see their error logs.
When the screen updates, we might see:
![]() |
In this case, the logs shows there's a disk space problem. Once we clear that up, we can requeue the frames in any number of ways:
Note that each frame log has the format:
![]() |
Rush prints a header into the log file, indicating all the information relevant to that frame. Below the header is the output of your render script.
Learn to look at your logs carefully when debugging problems; most renderers will print very useful errors that will clue you in on what may have gone wrong when rendering bad frames.
This will open up the "Frames Modify" screen, where you can type in the frame range you want to add to the current job:
When you hit the "Add Frames" button, the result of the add operation (rush -af) will be shown on the next screen:
To see an updated version of the frames report, hit the "Frames" button:
..where you can see the new frames 6-15 have been added, and have immediately started rendering.
When you hit the "Remove" button, the result of the remove operation (rush -rf) will be shown on the next screen:
To see an updated version of the frames report, hit the "Frames" button:
..where you can see the frames have been removed.