8

Email Notifications Rollout 33
Email Notifications Rollout
Rendering menu > Render Scene dialog > Common panel
> Email Notifications rollout
Main toolbar > Render Scene button > Render Scene
dialog > Common panel > Email Notifications rollout
This rollout lets a rendering job send email
notifications, as network rendering does. Such
notifications can be useful when you launch a
lengthy render, such as an animation, and don’t
care to spend all your time near the system doing
the rendering.
Inter face
Enable Notifications—When on, the renderer sends
an email notification w hen cer tain events happen.
Default=off.
Categories group
Notify Progr ess—Sendsemailstoindicate
rendering progress. An email is sent every time the
number of frames specified in Every Nth Frame
has completed rendering. Default=off.
Every N th Fra me—The number of frames used
by Notify Progress. Default=1.
Tip: If you turn on Notif y Progress, a lmost
certainlyyouwantthisvaluetobegreaterthan
the default!
Notify Failur es—Sends an email notification only if
something occurs to prevent the completion of a
rendering. Default=on.
Notify Completion—Sends an email notification
when a rendering job is complete. Default=off.
Email Options group
Fr o m—Enter the email address of the person w ho
initiates the rendering job.
ToEnter the email address of the person who
needs to know the rendering status.
SMTP Ser ver—Enter the numeric IP address of the
system you use as a m ail server.
Scripts Rollout (Render Scene
Dia log)
Rendering menu > Render Scene dialog > Common panel
> Scripts rollout
Main toolbar > Render Scene button > Render Scene
dialog > Common panel > Scripts rollout
The scripts rollout lets you specify scripts to run
either prior to rendering, or after rendering. The
script to execute can b e:
•AMAXScriptfile(MS)
A macro scr ipt (MCR)
•Abatchfile(BAT)
An executable file (EXE)
If relevant to its format, the script can have
command-line arguments.
The pre-render script is executed b efore rendering
(but
after
any other MAXScr ipt scr ipts that
are registered using the #preRender callback
mechanism). The post-render scr ipt is executed
after rendering has completed. You can also use
the “Execute N o w” buttons to run the scripts by
hand.