SUCCESS!!
I have solved the problem by enabling the 3 GB switch and turning up the virtual memory to 6GB - this has worked on a AMD Athlon quad and a intel Q6600 quadcore both have 4 gigs 800 speed ram in them.
Lasst night they both rendered a complex scene with 500 res fluid hitting multiple objects!!
Go Blender.
Dont forget to raise the mem cach tp 1024 as well. Find this by dragging down on your top bar in blender.
This is a render node running off of a mapped drive and twice now blender will not render past frame 60 its crashes every time. If I manually render the frames individually past 60 they are fine.
A major point of me using blender are these huge animations and I haven’t heard of any limitations, or others seeing such problems.
I will try to write the rendered files to my desktop instead of the mapped drive but this is driving me crazy.
Even running a version of 2.48a that is installed on the render node and writing files to the desktop on the render node it is still crashing at frame 60. It will not start at 60 and continue either it crashes every single time.
starting at 70 it is now rendering normally- but why does it stop at frame 60 every time?
It does this on two different computers now?
I start animation on frame 59 crashes on frame 60 crashes on frame 61 crashes on frame 62 crashes
If I start at 70 then it renders all day long till 150 again!
It does this on two different computers as its loading scene data it hits an unexpected error and its done!
SO I rendered out frames 60 -63 as single images and now blender is ripping through the frames why wont it render 59-63 as animation frames? only as render single and then manually save…
We might need a bit more information on the problem
I am assuming you are running windows?? (because you said mapped drive)
what are the system specs of both machines
how are you connected to the mapped drive? (wireless? ethernet, usb)
What are you trying to render? anything CPU intensive happening in frames 59-63
(particles?, raytracing?, SSS?)
it sounds like a memory issue or something similar
But it is not a good idea to render to your desktop - this will slow down any OS
but try to render to a folder on the local machine and see if you are still having the same problem
does the terminal window give you any information when it’s rendering or crashes?
OK both machines running Win XP Pro -
As of right now I have two 2.5quads and dual 3.2 from AMD.
I have a third computer that is my second quad core, and this machine crashes after 1 frame no matter what -
and the scenes are very intense - fluid at 500 resolution hitting at least 15 objects for 250 frames, all 3 machines have 4 gigs of 800 speed ram. 3 gig switch on the old quad and the dual workstation.
Maybe I enable the 3 gig switch on the new quad core and get back to you - memory usage is less than 1 gig in the scenes I am trying to render.
It seems that I was using more than a gig on the new quad core which might have been causing it to crash if it was getting up near the 2Gb mark. I have rendered 3 frames in row of the most intense scenes frames in teh late 30’s and it seems to work fine right now! I also upped the virtual memory to 6000Mb as I have 4 gigs of ram.
SUCCESS!!
I have solved the problem by enabling the 3 GB switch and turning up the virtual memory to 6GB - this has worked on a AMD Athlon quad and a intel Q6600 quadcore both have 4 gigs 800 speed ram in them.
Lasst night they both rendered a complex scene with 500 res fluid hitting multiple objects!!
Go Blender.