9.5.2

76 • TROUBLESHOOTING
 If you’re using textures or texture movies that can be processed only
under a specific operating system then, in a heterogeneous network,
the scenes will be rendered only by the clients which can do so.
Imagine a scene that contains QuickTime and PICT textures. This scene will be
rendered only by clients running under Mac OS. All Windows clients will abort
with an error and continue with the next job.
 If you’re using QuickTime textures in a CINEMA 4D scene on a Macintosh,
make sure that the movie is attened (meaning that all data is in the data fork,
not split between data and resource fork). Otherwise the texture cannot be
transferred.
 On a Macintosh, system dialogs (e.g. the one telling you of a server shut
down) freeze the whole system as long as they remain unanswered by the user.
Even the C4DN client can then not render.
Before you leave a render unsupervised you should load a system conguration
(using the control panel Extensions Manager) in which you have switched off
anything that could cause such a problem e.g. AppleShare. (Remember that
CINEMA 4D NET Render depends only on TCP/IP …)
 During rendering, CINEMA 4D NET Render creates BodyPaint 3D (B3D) les
and sends them to the clients. B3D is used because, at time of writing, it is
the only known format that supports both 16-bits per channel and multi-
passes. The B3D les will be deleted automatically once rendering has been
completed.
 CINEMA 4D NET Render is unable to generate AEC les — you must generate
the AEC le manually using the Save button. Save the AEC le in the same
folder as the multi-passes, otherwise After Effects will be unable to nd the
multi-passes when you import the AEC le.
Limitations
 Although NET Render can write RLA and RPF les, they won’t contain any
3D data.
 Animations are limited to a maximum frame number of 9999.