iKKe

Sorry I didn't reply sooner, I had a few very busy weeks. The total project incl. assets was about 1Gb in size, so I couldn't just upload it. I've tried to isolate the problem, I did not succeed, as soon as I reduced the project there was no problem rendering, it didn't matter what parts of the project I deleted. I guess it was a weird coincidence, it just happened at the wrong time for me. I managed to render all scenes by deleting all inactive objects for the specific scene, which is strange, I never had to do such a thing. It was a 90 sec animation, after rendering I had about 2 hours for the compositing, including render and compression, to get the animation on time at a presentation........ Cheers Hans

Not sure what the problem is, I tried to isolate it, but I can't... My next guess was a network problem, so I replaced the switch and a few cables, and Renderama still quits after about 30 - 60 min. Renderama quits without warning, all I can find are these messages in the console: 6/5/10 20:25:01 PM com.apple.launchd.peruser.501[212] ([0x0-0x17b17b].com.electricimage.renderama[4187]) Exited abnormally: Broken pipe 6/5/10 20:27:55 PM /Applications/3D/EIAS 8.0.0/Renderama.app/Contents/MacOS/Renderama[4269] ATS: Invalid FontObjectID (3) - only low 16 bits are being passed in. I use renderama all the time, even for all testrenders, haven't seen this before, weird... My next guess would be a faulty ethernet port... Does anyone have another suggestion? Maybe I will make it a feature request, to let Renderama not quit on a lost connection, but display a message ;-) BTW: All slaves have fixed ip adresses, and are present on the same subnet. Cheers Hans

Renderama quits, without any message, while all the slaves keep on rendering... I reinstalled Renderama, deleted the renderama prefs, deleted all slave temp files. Renderama is running on a intel core 2 Duo, OSX 10.6.3 (verified the Disk and Disc Permissions with Disk Utility) Then I collected all files to render again from a fresh project. Renderama keeps quitting after 20 - 30 frames without warning. Weird, haven't seen this before, and these things always happen on a tight schedule..... Any Tips? Cheers Hans