lolPalad1 said:well, now, feel free to post and state that you have 4gigs in your iMac so I can look like a pompous prick
Dafke said:maybe there is somebody with a brand new quad that can help you. if someone has this cinema app ass wel, maybe someone would like to test how fast his/her quad can do it.
even a better idea is to start an 'Apple Mac Hardware - Cinema Test', make your scene downloadable and people will want to see how fast they can do it. They do have to hand in the result off course.
Palad1 said:I'd rather not pay his monthly bandwidth bill if he were to do this...
:}
hcuar said:It'll be fine... they are spec'd to run that way. Granted you are causing wear and tear... however most people think that just starting up your computer daily causes more than using it!
RHMMMM said:Sure, let it go for as long as you want. The worst thing that can happen is it will die, in which case you still have the balance of a year's warranty and you can get a new one!
Mac Kiwi said:Whatever you do save out as tifs or even better tga files.If you crash you still have all your frames up to the point of the crash.If you use say .mov youre screwed if you crash.
atomcoeur said:well, i have 4 scenes with 900F each.. but with different cameras shots etc it must come up to around 5000 frames and im rendering at 640x360. The antialising is on geometry and im only using shadow maps. The only really intensive thing in my animations is lots of smoke pyrocluster effects although I have the volumetracer at 20 World step and it does not cast or accept shadows so its not really slow. I'm also using lots of volumetric (omni) lights and very luminous/reflective surfaces but thats about it. No AO, no GI, no caustics. The 2 weeks estimate came about by simply multiplying 5 min per frame times 5000 frames = 17 days.
A worrying thing I have noticed is that as the render goes on the slower it gets; for example last night I put on a batch and within say 2 hours it had rendered 20 frames but in 14 hours it had rendered 30! Too much memory saturation perhaps? :S
I've been rendering in .mov until now - do u think rendering in stills would make things faster?
Thanks!
dubbz said:Thanks for the tip. Can't believe I haven't thought of that before....
Doesn't crash often, but when it does, it's damn annoying.
Mac Kiwi said:Great thing about stills is you can also run an action or make a droplet to tweak stuff in post.
3D animation is one of the most processor intensive things your computer can do. Thousands of consecutive images rendered each needing calculations of lighting, textures, reflections, movement, motion blur, particles, camera movements and post processing. All that and after the two weeks of rendering you will end up with about 15 to 20 minutes of footage (+or- depending on complexity).dops7107 said:
Sorry, i don't actually have anything useful to tell you ... but wow, leaving a computer to "compute" for 2-3 weeks. I know nothing about Cimema4d. What takes that long to calculate??
It all depends on what is in the render frame at the time. your animation may progressivley become more complex as it moves along. a reflective object that is not in the rendered frame in the beginning of the clip may slow the process as it enters into the picture and logically speed up the render as it leaves.atomcoeur said:A worrying thing I have noticed is that as the render goes on the slower it gets; for example last night I put on a batch and within say 2 hours it had rendered 20 frames but in 14 hours it had rendered 30! Too much memory saturation perhaps? :S