Thanks! I’m trying to make this release as polished as possible, and highly customizable.
Glad to read that!
So far so good, no interrupts whatsoever. Thanks!
And on the topic of interrupted renders, one of the reasons why I got B-Renderon is that I had problems with random crashes when rendering in the command line, and this program is supposed to be able to detect that and retry any of those renders, but I’m wondering if there’s any way to see that in the log? I mean I had crashes before but now I just don’t noticed them so is it because of B-Renderon saving me or am I just lucky I don’t have any crashes atm?
Great! Regarding blender crashes, yes if it that happened B-renderon log would have a " - Error! Starting new attempt…" line
That’s in the live log I take it? Would be nice to have it in the after-render-log as well together with the list of all the frames and their time and mem usage (if you’re up doing that of course)
No that’s in the after render log. In the live log you’d just see a blender crash message if there was one, and the usual blender initial startup log lines.
Regarding storing all frames and mem usage statistics in the after render log, I’m thinking about it! The challenge is how to keep the info easy to read and navigate with so much info. An alternative solution would be to revive a different Idea I worked on some time ago: a toggle in the live log to switch to an abridged version which showed just one line per rendered frame, (including all the info blender reports for each frame).
Btw, I just uploaded a new build that remembers the live log sizing like you suggested, thanks for the feedback!