CompuServe Thread

#R4 won't net render

9 messages in this thread
#141404From: David R. WestDec 12, 1994 3:12 PM
My two machine network is not picking up the slave machine when rendering in R4. I went back to R3 and it works fine but in R4 only the master is working. Are there different settings for R4 ? Thanks, David West
#141914From: Mark YankeeDec 14, 1994 10:57 PM
David, << My two machine network is not picking up the slave machine when rendering in R4. I went back to R3 and it works fine but in R4 only the master is working. Are there different settings for R4 ? >> 3ds has a problem with network slaves being a mix of r3 and r4. You should upgrade your slave to r4. Mark
#141968From: David R. WestDec 15, 1994 8:32 AM
It is upgraded to R4.
#142116From: Don LandisDec 15, 1994 11:49 PM
>>3ds has a problem with network slaves being a mix of r3 and r4. You should upgrade your slave to r4. Really! I've been rendering with a mix of R3 and R4 for several months now. What is it that doesn't work for you with this combination? I've been just lazy at not upgrading my slaves.
#142146From: Jonas Ruikis [ADESK]Dec 16, 1994 8:00 AM
Hi Don, << Really! I've been rendering with a mix of R3 and R4 for several months now. What is it that doesn't work for you with this combination? >> FWIW. A large installation was reporting random field order toggling in a (R3/R4) heterogeneous network environment. It was resolved by having a complete (R4) homogeneous network environment. jonas[adesk]
#142210From: Don LandisDec 16, 1994 12:47 PM
Thanks for the warning, but so far I've done quite a few renderings with no problem with field order. Maybe they had a few 3DS.set files messed up???? Currently I have my two workstations loaded with 3DSr4 and the two slaves with 3DSr3. Unless I'm in a time deadline that's close I usually am rendering with 3 slaves and modeling on one of the machines, usually the one that has the PAR and where all the files are put. I still don't network render directly to the PAR as I haven't purchased the NDUMP yet. Hope this info is useful.
#142226From: Jonas Ruikis [ADESK]Dec 16, 1994 2:16 PM
thanks.
#142701From: Matt ArmstrongDec 19, 1994 7:23 PM
Don, We were one of installations having the random field ordering problem. We think that submitting our jobs from R4 to R3 slaves along with not having the network clock synched caused the problem. Everything is fine now with those two items fixed… Good luck. Matt / AM Labs
#142762From: Don LandisDec 20, 1994 1:07 AM
Interesting! I have four machines running this past weekend. 2 were R4 and two were R3. I do sync the net clocks with each 3ds launch with statements in the launch batch file. I have not had any problems with field ordering. It might be possible that you had the field order different in some of your 3DS.set files.