max 2018 Job Failed but flagged as done

[eqko]

We recently upgraded to 3ds max 2018 and are using it with RenderPal (been using RP successfully for quite some years now wioth max 2015)

for some reasons, since the move, jobs that show to have had errors in the output log still show as done in RenderPal, where previously
they would've shown as erroneous (or at least restarted)

is this something that I've done wrong in the renderer settings for 2018 or is it max 2018 itself reporting errors in rendering in a different way ?
Still on RenderPal 2.12.2 btw, because up un till now, it wasn't broken and if it ain't broke, don't fix it.
but this might be something that I need to update ?

any help appreciated.

[Shoran Support]

When encountering problems, you should always first update to the latest version. We have not yet tested 3dsMax 2018. You should post an output log of one of the failing renderings.

[eqko]

See attached for the output log.
eventhough it's states there were errors, the job get's flagged as done.

(the first part is a but to make sure I have no max instances hanging around from previous renders and does not affect anything else)

[Shoran Support]

It seems that the new version of 3dsMax doesn't return an error code, so RenderPal cannot catch that the rendering failed. One solution is to add an output filter for "Error occured while rendering job" which aborts the job.

[eqko]

and how would I go about doing that ?

[Shoran Support]

Modify the renderer using the renderer management. Just add a new output filter to 3dsMax.

[eqko]

ok, will look into it. thx for the info.