![]() Projects that use the Irradiance Cache (Legacy) function cannot be rendered using Team Render.This problem can generally be eliminated by using computers with exactly the same configuration - this will produce identical results for a single scene.Ĭache files can be uploaded to the Team Render server for GI calculations (see also GI and animation). Generally speaking, effects should be baked for such projects. The reason for this is the differing calculation precision of each computer’s math units (FPU - Floating Point Unit). Particles will in part be rendered at different locations on various computers. In heterogeneous networks with different computers (in particular different CPUs), differences can occur when calculating various effects such as video textures (different video frameworks) particle streams, cloth, hair, Dynamics, Delay Effector or GI.Surprisingly high amounts of traffic can be generated in particular when sending various cache files in conjunction with GI over the network (example: a test render of a still on 3 computers with activated Irradiance Cache and Light Maps can generate 500 MB of traffic (or more) - with a render time of only 50 seconds). A fast TCP/IP network is recommended because the amount of traffic back-and-forth between server and render clients can be immense.This is correct because the actual rendering is indeed finished but the server is still processing the Clients’ images. It may appear that individual machines are no longer taking part in the rendering even though the job is still running. A similar problem as described above occurs if you render animations that are very long and whose individual frames are rendered very quickly.Even if a still requires only a few seconds to render, using Team Render will NOT speed up rendering for the same reason. If the frequency with which the rendered Buckets arrive is too high, the traffic overhead on the network will simply be too great and will actually slow rendering. Why: Each rendered Bucket is sent across the network to the server. The following applies to rendering stills: The faster an image’s Buckets can be calculated by a single computer, the less sense it makes to use Team Render.All corresponding plugins and other elements (e.g., Houdini versions, if used in short, all third-party software needed for rendering the scene) for a given Project file must also be installed on all render clients.Server and render clients must have the same software versions.Render Client: The computer(s) to which the server sends render jobs via Team Render (this can be a regularly-installed version of Cinema 4D or a Team Render client installed via the installer).This can be a normal installed version of Cinema 4D or a Team Render server. ![]() ![]() Server: The computer from which the Team Render rendering is initiated.In the following description, numerous references are made to servers and render clients: Once the Project file has access to all textures/XRefs/Assets or other external files, they will automatically be distributed to all computers and rendering will begin. Done (note that the Projects/textures must first be distributed to the computers, which can take a while in some circumstances).Īll you have to do now is wait. Select the Team Render to Picture Viewer option from the main Render menu.The check box at the left of each computer must be enabled to use it for Team Render. Enter the Security Token (which can be defined individually for each computer) and click on OK. Right-click on the computers you want to use and select Verify. In the window that opens, all computers located within the local network will be displayed.Select the Team Render Machines command from the main Render menu.Make sure that the Enable Team Render option is enabled in the Preferences menu.Proceed as follows to render using Team Render: More information is available under The Team Render Server. If desired, a Team Render server can be started that makes the Team Render functions available per remote control via a website.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |