when I render my older 3ds Max 2010 scene out locally, all goes fine, no issues at all, but as soon as I submit the very same job to Deadline, I’m getting this:
[code]
Error Message
Exception during render: An error occurred in RenderTasks(): RenderTask: Unexpected exception (Error in bm->OpenOutput(): error code 12
2012/01/03 00:01:52 INF: Loaded //RAMMSTEIN/UNMANAGED_PROJECTS/DrMax_Garance/SHOTS/DM_GA_02/3D/MAX/DM_GA_02_LEKARNIK_RENDER_Max2010_loocas_001.max
2012/01/03 00:01:59 WRN: Gamma Correction is Being Enabled
2012/01/03 00:01:59 INF: Job: //RAMMSTEIN/UNMANAGED_PROJECTS/DrMax_Garance/SHOTS/DM_GA_02/3D/MAX/DM_GA_02_LEKARNIK_RENDER_Max2010_loocas_001.max
)
at Deadline.Plugins.ScriptPlugin.RenderTasks(String taskId, Int32 startFrame, Int32 endFrame, String& outMessage)[/code]
And the job just won’t render anything! It seems to fail on bitmap output. No idea why, as, again, as I said, when rendering locally (even on the same machine that fails the render in Deadline) all goes fine and the render saves correctly.
Do you have the full render log from the job (the one you get from the right-click menu in the Monitor)? I’m looking for the format of the output path that Deadline is trying to save to.
Thanks! The path format looks fine. I have seen this error occur when the output path was empty or malformed, so we’ve at least eliminated that as a possibility.
Based on Max’s SDK, error code 12 means BMMRES_INTERNALERROR, so it sounds like there may be some internal corruption, but it’s really hard to tell. Are you able to test saving to another format? Maybe switch to jpg, and if that works, try switching back to exr to see if that helps.
Hi,
I have seen this issue as well and can confirm its tied up with EXR file saving.
Haven’t had a chance to fully debug this yet. Are you saving out using the Max EXR (Cebas) plugin (Max version?) or are you using the VRay VFB? Also, are you using Max RE’s to save out the EXR as a single channel or multi channel EXR?
Hopefully your results combined with mine will help narrow down this one
Mike
OK, I think we can safely disgard FR as we don’t use that and still get this error ourselves. When you said you had no problems rendering it a year ago, can you remember what exact version of Max you were using? ie: the max2010 extension pack contained the new EXR file i/o plugin which I have a niggling feeling isn’t backwards compatible with the older Max EXR plugin. So, were you using Max2010 but without the subs pack? Alternatively, perhaps you weren’t’t saving out to EXR a year ago?
( just a few questions to see I’d we can narrow this down a bit more).
Is it possible the original file a year ago was originally created in Max2009?
Mike
I haven’t touched my 3ds Max installation since, it’s the same version as it was before.
The scene was made in 3ds Max 2010, though, with a much older build of finalRender, so, that might have to do with it?
As for EXRs, I always save to 32bit EXRs, the only exception are matte passes, but this was a beauty pass, no other passes were being rendered, no layers were being added to the EXR.
It was my bad, I remember the scene was actually crashing in Max 2011 (for some reason?) and I forgot to switch the versions in Deadline! Now when I tested it, all rendered fine!
I’m sorry to have bothered here, I should pay more attention to my submissions.