Our 3D rendering platform is a living system, constantly evolving to stay one step ahead of increasing demand. When we have a large backlog of models to process, we’ll be able to spin up as many cloud machines as we need, burn through the queue, and tear down the machines when the queue is empty again. We use 'Royal Render' as Render Manager, and with 3dsmax 2015 this system is not working anymore, too The developer is trying to get support of Autodesk to fix it, but they are not answering or helping for weeks now. In addition to using our existing farm, we plan to utilize cloud computers to help out our in-house servers. This is NOT just a Backburner Problem, it is a 3dsmax Command Line Render Problem.
#AUTODESK BACKBURNER RENDER FARM SOFTWARE#
Today there are a variety of software and cloud based render management solutions that we can take advantage of.
#AUTODESK BACKBURNER RENDER FARM MOVIE#
The entertainment industry has been investing into systems to improve rendering of movie frames for years. Fortunately we are not at the forefront of figuring out distributed rendering and complex job management.
We are at the forefront using photo realistic rendering to help sell furniture and home decor.
mixing 3ds Max and 3ds Max design on a render farm for more information. In order to continue to scale we started evaluating other render management systems. As of Deadline 10, Autodesks Backburner is no longer required to be installed. We didn’t find a magic solution to this instability, so we worked around it by automatically retrying renders that failed up to four times, assuming that if it didn’t work after that, there was actually something wrong with the model. We began to notice that renders frequently failed, but when we retried them, most succeeded. Though Backburner helped prepare us to scale up the throughput on our platform, it wasn’t a perfect solution. CPU Utilization with Backburner: our farm nodes were kept nearer to 100% utilization
0 kommentar(er)
