Nope-- you can mix and match 32 and 63 bit slaves at will. Keep in mind that if you're rendering a very large data set the 32 bit systems might not be able to handle it. This should be rare, though. The farm slaves do not have the added overhead of AutoCAD.
I will be updating the farm software in a day or two.
It's free right now. Current plan is to start selling it by 11/15. No firm pricing yet-- $200-$300 has been bandied about as an introductory price-- $600 as a final price. Free eval of 2-node farm will always be available.
There are no masters on the render farm, only slaves-- and these can be either 32 or 64 bit or mixed. Physical RAM doesn't matter at all in this discussion-- it may matter to performance but it will not prevent a slave from running.
On the other hand, it is possible (but unlikely) to generate a very complex model or high res rendering that 32 bit slaves will not be able to render. This has nothing to do with physical memory. It has to do with the limitations of address space that occur with all 32 bit processes. This limitation is either 2GB or 3GB depending on your system (almost all 32 bit systems can be upgraded to run 3GB address spaces-- again nothing to do with physical RAM.)
I have another question of render farm, can it run on linux with wine?
it was because I want to set up a render farm sets of computer. if I have 4nos. computer, I need 4nos. windows os. If the render farm can run on linux with wine ( I want use ubuntu linux), I will more flexible on the system.
"I use the AutoSave feature in Nxt, only should you forget to save a new name for another rendering it over writes the pervious one, thereby losing hours of work. I believe it either should auto-number the renders like AR4 and before or take the name…"
"Try this for general layer material assignment issues.
If you are using AutoCAD Architecture and trying to assign materials to components such as window frames, the bottom of this page has an explanation of how to assign material to ACA…"