AWS Thinkbox Discussion Forums

An Unexpected Error has Occured.

When submitting netrenders through backburner complex scenes somtimes return An Unexpected Error has occurred. Can you tell me 1) Is this due to backburner or max and 2) Does deadline suffer from teh same problem?

Hi Khye,



I’m not overly familiar with Backburner, so I can’t answer question (1)

specifically. As for number (2), we always try to retrieve the best

error message we can from Max, but this isn’t always an easy process,

especially when Max just crashes during the render. For example, when it

comes to complex scenes, it’s very possible to run into memory issues

which can cause all sorts of unexpected results, which could explain a

generic “An Unexpected Error has occurred” being returned from

backburner. In these cases, Deadline is usually quite good at catching

Access Violation errors, which is another way of saying “There Was A

Memory Problem”.



There is still an odd chance that Max can crash before the error message

is propagated up to Deadline, in which case Deadline returns a more

generic “Max has crashed” error. When this occurs though, we suggest

looking at other errors for the job, as most of them were likely

propagated to Deadline properly and can give you a general idea of what

the problem is.



Here’s a list of known error message that Deadline gives for 3dsmax, and

possible causes/solutions:

http://www.franticfilms.com/software/support/deadline/3dsmaxerrormessages.php



Cheers,

Privacy | Site terms | Cookie preferences