Page 1 of 1

new coop - PRIORITY!

Posted: Wed Aug 06, 2008 1:08 pm
by deflix
Many of you are probably already aware of this info but thought I'd post it anyway. Unfortunately problems with network rendering seem to relate primarily to general instability and unreliability of maxwell itself. I have recently started using Maxwell in additiion to Vray in our studio, and am keen to prove its worth in a commercial environment.

I have found that Maxwell is able to achieve significantly better results with far less effort although this is offset by a very large difference in render speed - almost 10 times in some instances.

What this means therefore is that network rendering is ESSENTIAL in a professional environment unless you are only producing simple product design images.

And this in turn demonstrates the critical importance of a robust and reliable network rendering interface - something that clearly needs more work.

The main problems with the coop mode is that there is no fall-back if for any reason one or more nodes fails (no way o recovering any succesfully created MXi files) and no auto recovery.

This effectively renders coop mode irrelevant as it is much better to render a seperate MXi on each machine instead. This takes time when you have 6 nodes like we do - but it takes alot less time then having to continually close each one down and reopen them everytime some tiny error causes the whole thing not to work!? which leads me to the following question: why does coop mode not just do this aswell??

top of the list I think NL! - thanks for listening.....

Posted: Wed Aug 06, 2008 11:23 pm
by Bubbaloo
I'll agree that coop mode needs a remote shutdown and restart of Maxwell Server on remote computers. Also, an auto recovery/resume mxi from failed render nodes would be awesome.

Posted: Thu Aug 07, 2008 10:35 am
by QuakeMarine1
in the meanwhile you can have a look to pstools http://technet.microsoft.com/en-us/sysi ... 96649.aspx
wich allows you to remotely start application without vnc or remoteDesktop
a simple batchfile + taskill or direct start cmd and you can easy admin your 14 nodes

Posted: Thu Aug 07, 2008 10:47 am
by KurtS
QuakeMarine: thanks for the tip! A useful work-around that saves me a lot of remote login/logout that is driving me nuts...

Posted: Thu Aug 07, 2008 3:23 pm
by Bubbaloo
Those look like great tools. Anyone feel like showing me how to use these tools step-by-step for a dummy? I tried running psexec but no worky.

Posted: Thu Aug 07, 2008 3:55 pm
by Bubbaloo
After I run psexec, it a cmd box opens up and it says connecting to bradj... and then when it connects, the cmd box disappears. How can I get that box to stay put? I'm just starting with something simple like ipconfig but since the box disappears, I can't read it.... :?:

Posted: Thu Aug 07, 2008 4:21 pm
by Bubbaloo
Nevermind, I figured it out... :)

Posted: Thu Aug 07, 2008 4:42 pm
by Bubbaloo
Do you guys know of any way to set affinity for used cores remotely?

Posted: Thu Aug 07, 2008 4:52 pm
by Bubbaloo
Nevermind again.

Posted: Tue Aug 19, 2008 12:51 am
by JCAddy
Damn Brian, you turned this into a one man thread.

Posted: Tue Aug 19, 2008 2:08 pm
by Bubbaloo
I said NEVERMIND! :lol:

Posted: Fri Sep 12, 2008 10:51 pm
by cgbeige
coop render needs to be implemented much like mental ray for Maya, where if you hit render from within Maya, it still references the file with links to slave machines. This would save a lot of time.

But first it needs to simply work (on OS X at least)