CompuServe Messages

Alan, More directly, we do have some proprietary issues at stake. However, our "RenderGarden/Farm/Jungle" operates transparently to 3D Studio – It actually "looks" like a normal network setup to 3D Studio. Our "Greenhouse" process monitor software takes care of the traffic control. To your question about a single 3DS file taking 98% of available RAM – 3D Studio network rendering distributes rendering data one frame/field at a time. Each assigned processor gets a frame – just like a normal network setup. After submitting the rendering job, the animator's machine is available to all 3D Studio functionality. After making changes, it is possible to submit the same job stream as a second concurrent job stream. Processors may be assigned exclusively to job streams through the use of "Greenhouse." The same limits that apply to current network rendering still apply to the swapping and file size issues. With the exception of render time – on this issue we have "optimized" 3D Studio network rendering functionality. Roughly, our entry level "RenderGarden" has accomplished a >4 hour project in 39 minutes with only 4 of the 5 avilable processors on-line. Also, proprietary components have been developed and manufactured to take advantage of critical performance areas. This machine is smart enough to sense a power failure and call or page the animator for his response. Basically, AM Labs personnel have both the hardware and software knowledge to integrate a very powerful "parallel" processing machine with the best animation software on the market.