So, I have succeeded in getting my render farm set up again.

I decided to log the steps so that others may benifit.

This setup only requres A:M being installed on the Render Server machine.
Note: I only use PCs so I'm not sure Macs can be set up this way. They may need A:M installed on each Macintosh to function.

1. Create a data repository on one machine and put a copy of all the project files you need to render there. Make sure any unique materials, etc. are put here too. I just mirror my entire A:M data folder. (I use a Linux box for with simple Samba share for this job, although a windows machine with a simple share will work too. EDIT: If you have more than ten slave machines, you will need a server version of Windows to allow access from more than ten machines at a time.)

2. Install the Network version of A:M on the machine you wish to use for the Render Server.

3. Share the Hash installed directory (i.e. - C:\Program Files\Hash Inc\V13.0) as "AMRoot" or something similar of your choice.
NOTE: Firewalls will kill this unless you are allowing windows shares to pass.

4. Create a network shortcut to 'RenderMessenger.exe'. The 'Target' should look similar to this in the properties.

'\\RenderServerMachineName\AMRoot\RenderMessenger.exe'.

EDIT 05/11/2007: If you share your hash install directory as "AMRoot" or something similar, this will allow you to upgrade A:M on the server machine and all your shortcuts will still function. You just unshare the old major release and then share the new release (i.e. - unshare "V13.0" and then share "V14.0" as "AMRoot"). I have included screen shots of the shortcut and render messenger properties below.

5. Copy this shortcut to your data repository or the hash share so all the slaves can find it.
NOTE: If you are using your normal A:M design/modeling machine for a render slave, you will have to rely on the local files being the same as the Render Server. i.e. - The entire V13.0 folder must be identical.

6. From each slave, locate and copy over the network, the new Render Messenger shortcut you just created to it's desktop.

7. Run RenderServer.exe from the Render Server machine. (Make sure you have your dongle in place with drivers installed)

8. From each slave, run the Render Messenger shortcut and follow the prompts to put the information in for each slave (slave name, etc.). Each slave should show connected to the Render Server shortly after running.
NOTE: Unless you have some kind of unique ports you wish to use, take the default port that Render Messenger prompts you with. Normally this is port 1750, make sure it's open if you have any firewalls running.

Now to test your farm.

1. Create a new pool, then create a new job within Render Server.

2. Name your new job 'Test' and browse the network for a small project to test with. (I used the 'Dance' project from the A:M CD as I copied my CD data to the data repository too.)

3. Render Server will verify the project and prompt you to verify the choreography and camera to render. Click next.

4. Select the format. I prefer Targa sequence as it retains the most A:M information.

5. Select the output filename by browsing to your remote data repository and either create a folder in your project for the rendered frames or a generic holding area for your frames in the base of your repository. Use the name 'test0000.tga' for your initial test. NOTE: As of this writing if you do not browse to the network to set this path. The render will fail!

6. Frame range and resolution should be set, just click next for the test.

7. Select the Quality of your render. For this test, choose 'Final'.

8. Click Finish.

9. Now drag your slaves one at a time into the window area just under you job in the pool window to start them. This is the point at which you will note errors if there are any.

10. You should see each slave start up and begin loading and rendering frames.

Congratulations! You have built a rendering farm.

Nice work, we are just in the process of moving but I want to set up a server for mutiple uses. ftp, rendering and such.
You seem to have the hard part figured out.
would it be possible to pick your brain on what i need for hardware, OS and such to put everything together to get started anyway?
Would the render farm render all settings or is that still a issue?



If you want to email or skype or both let me know.

I can give you a list of software that we are looking at and such.

just need some basic guidance, we animators aren't that smart ya know!

john at
kueppervision@gmail.com

Jody,
Excellent job of explaining the setup of a render farm!!
The linux box really simplified things for me (once I got it figured out).

The only thing I don't do yet is run Render Messenger off the Server machine. That looks like it would really make upgrading to new versions a snap. So can you copy the shortcut to the Linux box project directory?

If the project is not huge (or have 3ds props in it as they seem to take a while for the slaves to load their information) you can start all the slaves at one time. I usually drop them in 4 at a time just to be safe.

Very nice work!!
David

Keup,

I actually have the Linux box for FTP, Web Server and File Serving.

The Render Server (PC) is also acting as a slave in the farm.

General hardware for slaves is basically whatever you can run A:M on with at least Windows 2000. NT would probably work, but is no longer supported by Microsoft.

Faster is of course better. If you have large amounts of decals, your slaves will quickly eat through RAM. I have at least 256MB on each machine, 512MB where I can.

As to other software I use. I use VNC to remote control the server and slaves (if I can't get to them easy) and SyncBack to syncronize my file systems and do backups to other machines. TGAs can be put together with A:M although some people prefer to use Adobe Premier.

Rendering all the settings? Hmm... there was an issue in the past rendering hair, but I think that's been addressed. I'd have to check through the A:MReports to see. Most things should function just fine.

David,

As to the slaves using LOTS of network bandwidth for starting up and getting files. You could use SyncBack to syncronize all the slaves to the file server ahead of time and use local files for project stuff. But seeing as how cheap Gigabit network stuff is nowdays it's almost a moot point.

Again, I haven't had really LARGE projects like you probably have, so I'll blow up that bridge when I come to it.

All my stuff is 10/100, my desktop is the only thing with a gigabit (dual) card in it. Switches are 10/100 too.

One of my largest projects is about 900 Mb for the project directory. I have a tendency to leave extra things in them "just in case".

Kuep
My slaves are running win 2k and winXP Home.
AMD processors will out render Pentiums hands down, keep away from Sempron's, stay with Athlon XP's or 64's (64's are about 25% faster then XP's).

David

There is a "network" version of A:M? I didn't know that. Where can I get one?

You will have to call Hash and ask for the NetRender version of A:M.

This will buy you two things... one, a USB dongle which will allow you to fire up A:M without the CD (with the Network Version installed)... and you can still use the regular version with the CD for all your design main design work.

This dongle also allows you to run NetRender server which is the heart of a render farm.

I think there is more than one type of NetRender package... again, ask Hash for details and pricing.

There is a 3 machine liscense, and an unlimited version.
Might be more but I don't think so..........

I got mine years back when there was only the unlimited... lucky me.

Just got my USB dongle at the Hash Bash... Wheeee!!!

Minor update to the setup document. The new information allows for going from one major release to another without having to rebuild the shortcut for the slave machines.

I've also included a few screen shots showing my slave shortcut settings and each slave's messenger settings.

Enjoy!

How do you install A:M on two computers?

Can you do that or is there a restriction for installing on just one pc?

Do i install all of A:M ib both pc's or do i select a certain installtion setting?

Elliot

Elliot,
What is being described here are setups based on Netrender, a separate program which at this time may not be available.
Hash Inc may field it again in the future if there is sufficient interest and support for it.

As far as running A:M on two separate computers:

Install on each computer.
- Start up A:M
- Move your CD to each computer and start up each one in turn.

One program... one user... more than one computer.

When it comes to networked solutions you'll want to contact Hash Inc.
But... be ready to pay for that support.