OTOY Forums

Hi,
rendering a sequence of 250 frames dropped six or more frames because of following error:
"Windows has closed the application because it was not responding" (or something close to that).
Also rendering took really long because it stopped (unnoticed) a couple of times with: "File format error - Didn't succeed to load image [looks like encoding error]".

While these errors might be corrected the system stability can vary greatly and users cause errors too, so maybe:
- Export plug-ins could redo rendering last frame while it isn't successful (no output file exists etc.);
- Octane could disable waiting on errors (and log them instead) for animations; Or better have a box to choose whether to stop, redo or to continue frame rendering if error occurs.

Hi,

It would be good indeed if the exporter would catch these and do a check if the frame was rendered.
most network render queue systems do the same.

i will incorporate it into our next exporter guidelines once we're there.
however, it's strange you get so many problems, do you have an idea why they fail ?

Radiance

I'm geeky-cautious about my system components and stability. Though I never expected that from Windows it never hangs.
Lack of RAM might be the reason. Of total 4GB, at the start of loading the scene to Octane there's only about 1.5GB left, because scene is simultaneously open in blender. A couple of times while working on scene in Octane I ended up with Windows message suggesting to "save and close" because there's no memory left.
On other hand the obj is 85MB and there's single 2048x1024 texture so it doesn't seems that bad.

hmmm, should'nt it have a large enough pagefile ?

Radiance