Can't render AOVs in exr format on win8.1

[Anonymous]

First of all ,I have many years of experience in both Maya and Arnold and my workflow until this moment was Maya 2015 with the latest compatible mtoa...

But about every three years I update to a more recent version of Maya and test for a little while before switching.
The issue/bug I 'm having is that I can't render aovs in an exr format. It's a very strange bug that happens always in every scene.
Freshly installed Maya 2018.5 with resetted preferences and many versions of Mtoa. It only happens on a Windows 8.1 pc. Specifically it writes the exr but in an unreadable file(Nuke or PS). If I change the driver in any other file(tif,jpg,etc) it writes normally. I did the tests with most of the available aovs. The Z aov works,that has data type float(i don't know if it's changed from the previous versions but the pass was written on the rgb than the alpha). I tried every parameter tiled, different compression, merged AOVs....

Beauty pass is fine, Arnold render view AOVs is fine,
To narrow down the problem and test, I uninstalled/install different versions of Mtoa (3.0.1 to 3.1.2.1). Everything is ok in a Windows 10 pc. In the same os there are Maya 2013/2015/2016/2018. The first test I would do if I could is to test in another win 8.1 machine, but I only have access to win 7 and 10 setups.
So the bug happens in Win 8.1 . Maya 2016/2018 and Mtoa 3.0.1 to 3.1.2.1

[Stephen.Blair]

Can you post an Arnold log?

[Anonymous]

Yes of course: in verbosity level : Warnings this is it:

[mtoa.ext] aiAOVDriver Found no translator named "maya" 00:00:00

[Stephen.Blair]

That warning can be safely ignored. It happens anytime you batch render (the maya translator exists only when you're rendering in non-batch mode).

Could you post the full Arnold log and the exr too?

[Anonymous]

log-simplescene-exr.zip

yes. I'll upload the log and the exr file. I set the vebosity level to debug.

[Anonymous]

Do you have any news;

[Stephen.Blair]

I don't see any problems. The exr you sent appears to be the indirect diffuse, and it's a valid exr

[Anonymous]

thanks for checking!

Oh. Crazy bug in my system! I didn't check the image in another computer.
You are right, the images are opening normally in my surface pro on Windows 10. I 've never had a similar bug in so many years.
If I save the images in the surface pro as a copy, they open normally in the win 8.1 pc. So strange....
But the original file can't be red properly. In Nuke the are the typical messed up exr errors (the file format number's version flag field contains unrecognized flags,reader did not set channels,reader did not set bounding box).
I'm wondering is there something (anything) different in the way the aovs exr are written(OpenEXR tags,I don't know) than the beauty pass(which works ok)that in can be a problem in an older os?and because i cant find a lot of reports its probably something rare and unique in my system...that it happens only in the latest Mtoas. (all aovs exrs from mtoa 1.2.7.3) .

Anyway i don't know what more to investigate. I will keep this setup and put another os(Win 10) in the same system,(but fore some reasons i wanted to keep this setup(win 8.1) also and be functional)

@Stephen Blair

[Anonymous]

another update. As a quick test I used the images in maya 2018 as texures and they work normally. Is it possible that (the aovs exr) cant be red in older software(Nuke 6.3v4,Ps 2015 CC ) ?

[Anonymous]

Ok after many tests , the answer that I'm leaning is that newer versions of mtoa write AOVs exrs that are not compatible with older versions of Photoshop ( 2015) or Nuke (6.3v4), can you confirm this? Maybe there are different openEXR specifications. I will update in another computer but I would like to keep that as it is...you can write it documentation if it's true. Thanks