CompuServe Messages

Jonas, I have been having field order problems as well on my network. I haven't mentioned them because I've learned not to bother mentioning any problem that I have until someone else has it too. I've got three machines — all with r4. All the .set files have the default "field order = 1" value. But: sometimes the log file will show the field order as "0" on all machines. No matter what I do (restart all machines one by one, delete the job and start over, etc) it will continue as "0". The interesting thing is that I believe that the log file showing field order as "0" is an error. It appears that the actual field order is "1" — in spite of what the log file says. I can't be sure about this because I don't know how to determine what the real field order is. I have rendered a targa job with the field order set as "1" and shown as "1" in the log file and then I have re-rendered some of those targas which suddenly show up as field order "0" in the log file. When I brought the targas into the PAR, I expected to have problems between the two groups but there is no noticeable differance — so my conlusion is that the log file is not accurate. Alec Jason P.S. I need to know what differences there are between r3 and r4 regarding network rendering. I have still had other severe problems during network rendering and I'm wondering if I should have done something more than just copy over the r4 3ds.exe files onto the other two machines.