Guest dialog Posted January 24, 2014 Share Posted January 24, 2014 Looking to render about 20 different scenes...so yes 20 different max files (They all have different lighting and textures and materials). Which is the easiest way to go about this? Backburner?? Qube!?? Not sure... don't really want to babysit these things all weekend. I only have access to the one workstation as well. Link to comment Share on other sites More sharing options...
Chris MacDonald Posted January 24, 2014 Share Posted January 24, 2014 Submit each job through backburner, they'll form a queue that will then render off. You can even set priorities and things like "don't start x until y", etc. Link to comment Share on other sites More sharing options...
Guest dialog Posted January 25, 2014 Share Posted January 25, 2014 Submit each job through backburner, they'll form a queue that will then render off. You can even set priorities and things like "don't start x until y", etc. Ok great. I will try this...last time we were using backburner on our workflow was all through our network... that was a nightmare. I work %100 locally now. I will give this a shot. Thanks Link to comment Share on other sites More sharing options...
hockley91 Posted January 27, 2014 Share Posted January 27, 2014 Yes, through backburner. Works great! You will have to monitor it though. Some things can go haywire and then the whole thing'll hang on an error. Link to comment Share on other sites More sharing options...
Guest dialog Posted January 29, 2014 Share Posted January 29, 2014 Yes, through backburner. Works great! You will have to monitor it though. Some things can go haywire and then the whole thing'll hang on an error. Ya that is my worries. Link to comment Share on other sites More sharing options...
ilyafloussov Posted February 3, 2014 Share Posted February 3, 2014 Backburner is usually never the issue, anytime you have to render locally, it means you have problem within your max file. Most likely it's textures not properly pathed, missing plugins on slave machines, bad materials/geometry that run up ram usage and crash the render, inaccessible directories on slave machines, CMYK instead of RGB images, and bottlenecks in the network is the most likely scenario. You have to make sure your network switch and server can handle all the textures and geometry as well as have enough power to write out the final image. I would defiantly get your IT department on this. Do you know what the error message is when the render crashes on your slave machines? Here we use a submitter script to submit all the files to the backburner, than VPN into one of the machines to check up over the weekend if necessary. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now