V-Ray errors on image writing (but succeeds in writing the file)

[Fredrik Averpil]

We've been using the stable 3.40.04 build (version 27010) from 161025 and I'm getting reports on numerous scenes generating the "cannot write output image file" error in the V-Ray for Maya 2016 render log, although the EXR files are being written properly.

The real issue with this is our render farm managers sees this as a failed render and performs an auto-retry of the render. On the second attempt it marks the render as failed.

I haven't had time to investigate or dig into the scenes which are exhibiting this, so here I am just merely wanting to hear if anyone might have seen this too or if possible this is something someone at Chaosgroup recognizes as having been fixed in the recently released 3.40.05 official release...?

[ydm]

Is this 100% reproducible or it just happens from time to time?

The cited message should be followed by an error on the same line. Can you please share the full line with us or, better, send us the full rendering log.

Pastebin it or, if it contains sensitive information, send it to support@chaosgroup.com . If you choose the latter, please also include the URL of this thread.

[Fredrik Averpil]

My colleague will be back with a reproducable scene. It has something to do with the multimatte render element.

[ydm]

It would be great to have a reproducible scene! Thank you for your efforts!

[vlado]

My colleague will be back with a reproducable scene. It has something to do with the multimatte render element.

It will be great if you have a reproducible case. We've had a number of reports for similar issues but I'm not quite sure what's causing them. We'll patch the official builds on the site too. Thanks for the report!

Best regards,
Vlado

[vlado]

Nevermind, I found it... the error message will be gone for the next nightly/stable builds.

Best regards,
Vlado

[Algehov]

Alright, I have a simple scene that reproduces the problem. I think, all you have to do to reproduce it yourself is to add a multimatte, and set it to Use material IDs. No need to set any ID numbers or anything. This will cause the error.

Ill send the scene anyway just in case its something else within the prefs thats causing it, but if I delete the multimatte it renders fine again.

Here is a link to the scene:
https://mega.nz/#!WthDCRiD!lFwpKhuXp...sYmJAMNDQMBcKg

And here is the error log:
http://pastebin.com/jZhAeLzT

[Algehov]

Nevermind, I found it... the error message will be gone for the next nightly/stable builds.

Best regards,
Vlado

Im too slow, dammit!
Thanks for the update. When do you think a new stable with this fix will be out? I would like to update all our projects with this error asap. Will go for the nightly if it will be a couple of days though.

Cheers again!

[vlado]

When do you think a new stable with this fix will be out?

Tomorrow, but if you are in a hurry we can run the builds today.

Best regards,
Vlado

[Algehov]

Tomorrow, but if you are in a hurry we can run the builds today.

Best regards,
Vlado

Ah, no tomorrow works great Thanks for being quick about it

[Fredrik Averpil]

That's great, thanks Yordan and Vlado!