I started it around noon, then did some running around until about 3, Blender crashed after I left. (My system uptime was over 60 days at that point, so that’s my fault)
I started it again from a couple frames before it crashed, an hour later I went on a date and got back around 9. As I was about to leave I saw a text from my roommate saying that we lost power at 4:30.
When the power came back at 10ish I started it again.
Only about 2000 frames to go out of the 14472 frames in the render. And at about 1.25 seconds per frame, It shouldn’t be too much longer.
If I didn’t have to have this done before tomorrow (I’ve got a couple projects that need to finish this week) I would have just had round 3 go while I was sleeping and dealt with any potential problems (like another crash) in the morning.

tis why at minimum a proper computer lab has 5 machines: router, firewall, LAN, servers, & work.
Renders should be left to either LAN or servers to work, while you game.
gamers hate being told you don’t propercomputer labbattlestation without at the least 5 machines running. Routers, firewall, and, servers should be up 24/7.Unfortunately before my NAS got it’s much needed upgrade to be for offloading rendering tasks to, component prices went to the moon.
That’s bs&ʧ problem. The’re datacenters waiting to be properly distributed to the needy. You only need a party of 5 to cut off a DC, take a rack, and serve yourselves.
I’m pretty sure there has been a kernel update in the last 60 days, which could make your renders 0.2s/frame faster. Also, in my case using blender cli also renders a little faster.
I run Kubuntu so my kernal isn’t exactly “at the forefront” of development lol
I didn’t know about Blender CLI before your comment, I might have to take a look at it in the future for some other projects that’ll inevitably take awhile.
This one took so long because it was 1 shot of 14472 frames, my next version of it is def gonna take longer to render.



