#Net Render
8 messages in this thread
Michael:
>> Does each workstation load a driver in the config.sys?
No.
>> How much memory is needed for the slave workstations?
Same as for any other rendering workstation, the rules are the same!
>> Is this a Novell only kind of thing?
Any network will work fine.
>> what is the upgrade charge?
$495
Short but to the point (for a change!),
Greg Pyros
Greg,
How much memory does the TSR take? I am assuming this works like the Macintosh
stuff… There is a program loaded at startup that waits in the background
looking for render jobs to come it's way.
Is this how this works? What, exactly, is the way in which this nifty feature
works?
-Mike.
Michael:
>> How much memory does the TSR take?
What TSR? There is no TSR!
>> What, exactly, is the way in which this nifty feature works?
You just run the executable and it looks out on the net for something to do.
It will render a frame at a time, not a portion of one.
When it finishes, it looks out there for another, and another, and…
Greg Pyros
Greg,
>> You just run the executable and it looks out on the net for something to >>
do. It will render a frame at a time, not a portion of one. When it >>
finishes, it looks out there for another, and another, and….
Sounds like a job description for a freelance animator <G>.
James
James:
>> Sounds like a job description for a freelance animator <G>.
Well put!
Greg Pyros
Greg,
> run the executable and it looks out on the net for something to do.
How does 3ds know what computers on the "net" to use? What if you are on
system A and you start rendering. Does it use ALL systems on the network to
render, even if someone is using them or does it look at some list of systems
to use/not use?
For us network neophytes, can you please give a CLEAR example of how it works?
Thanks…
Steve Ormonde
A new 3DSNET.SET file contains information about how a machine "registers"
itself on the network (every machine has a unique ID#). They then share a
networked subdirectory by writing control files back and forth, and looking for
new things to do. The network topology is dynamic, meaning that as systems
become available, they get frames from the current rendering process, and as
they go off-line, their frames are reassigned to other machines.
– G
Ah, O.K. Thanks for the explanation, Gary!
Steve Ormonde