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.

  • nutbutter@discuss.tchncs.deEnglish
    9·
    3 days ago

    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.

    • Gormadt@lemmy.blahaj.zoneOPEnglish
      8·
      3 days ago

      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.

      • psycotica0@lemmy.caEnglish
        3·
        3 days ago

        I’ve never done anything that long with Blender, so I have no experience, but I could also imagine blender CLI being a little more reliable in terms of crashing.

        Or at least when it does crash, it’ll be more obvious. I assume someone out there has made some kind of “automatically restart it from where it left off if it crashes” script, if the CLI doesn’t do that itself 😛