- Mon Jul 24, 2006 12:57 am
#173227
I finally got a chance to play with network coop rendering this weekend. It seems to work fairly well in most cases with a few exceptions.
1. When trying to render out a large image 2500x1875 I have issues. I would open the mxs in the viewer and send it out to my massive two computer render farm
. It then would sit there forever (3hrs) with recieving scene in the status for both nodes, but nothing was happening on the server end. I could not stop it or cancel the render either when it was in this state. I had to go to each machine, and close the server to make it let go which crashed the manager by the way. I did specifiy a mxi path in the viewer, and opend the mxs first in the viewer so that cant be the issue. Like I said I have got it to work before, so I am confused.
2. Next I though I will turn on HD in the viewer and see if this helps because of the size maybe. I dont think HD has anything to do with actually kicking the render off, but maybe it does. It did start, and each node switched to rendering status. Checked the servers, and they were rendering. About 20 minutes into the render when it tries to save the first jpeg from the render the server kicks back an error saying Hard Drive option not available with Multilight and crashes the server. Minutes later the same thing happens on the other server. Funny thing is I did not have ml checked off in the viewer or in the scene file that it was using so I dont know how I got that error.
Concluding my dilemma here. Has anyone else had issues rendering large images with network coop? Does HD work with network coop, and if so do i need to enable it in the mxs file or the viewer, or does it matter. Since I only have two computers right now I just decided to render them manually in the viewer on each machine with different seeds, and manually merge them. So far each machine is producing an image. I would like to have this working though. I am anticipating buying a few more render slaves to set up a mini-farm. Thanks in advance for any help.
Also if any of the admins read this maybe there could be a sticky, or category for network rendering. There seems to be a lot of questions on this spread out all over the forum. I did searches before asking the above questions, but the info is so spread out, and unfocused. Since this feature is so important to getting an image from maxwell in a reasonable time it deserves its own category I think. At least a sticky?
1. When trying to render out a large image 2500x1875 I have issues. I would open the mxs in the viewer and send it out to my massive two computer render farm

2. Next I though I will turn on HD in the viewer and see if this helps because of the size maybe. I dont think HD has anything to do with actually kicking the render off, but maybe it does. It did start, and each node switched to rendering status. Checked the servers, and they were rendering. About 20 minutes into the render when it tries to save the first jpeg from the render the server kicks back an error saying Hard Drive option not available with Multilight and crashes the server. Minutes later the same thing happens on the other server. Funny thing is I did not have ml checked off in the viewer or in the scene file that it was using so I dont know how I got that error.
Concluding my dilemma here. Has anyone else had issues rendering large images with network coop? Does HD work with network coop, and if so do i need to enable it in the mxs file or the viewer, or does it matter. Since I only have two computers right now I just decided to render them manually in the viewer on each machine with different seeds, and manually merge them. So far each machine is producing an image. I would like to have this working though. I am anticipating buying a few more render slaves to set up a mini-farm. Thanks in advance for any help.
Also if any of the admins read this maybe there could be a sticky, or category for network rendering. There seems to be a lot of questions on this spread out all over the forum. I did searches before asking the above questions, but the info is so spread out, and unfocused. Since this feature is so important to getting an image from maxwell in a reasonable time it deserves its own category I think. At least a sticky?