Maya fatal error when saving a scene with Arnold renderView open

[Anonymous]

I have this strange probleme and I didn't see anything like it online, I'm posting this now because another colleague of mine has the exact same issue so maybe you have some information about it.

Basically each time I save my maya scene with arnold renderView on, it causes a crash, it just does the "fatal error, attempting to save blabla..." and it doesn't even successfully save the scene in temp. I hope you can help me because with this probleme I have to always close my arnold renderViewer before a save which slows the workflow a lot, and I can't even use autosave anymore.

I'm using Maya 2015 with the latest version of maya to arnold (MtoA 1.4.1.2 - Core 4.2.16.1)

My config is : 

Xeon CPU E5-2643 3.30Ghz (16CPUs)

Nvidia Quadro K50000

[Anonymous]

Hello,

If I'm going to be brutally honest, I don't think you're going to get any help from AD on this. 2015 is 3 releases behind latest, so support is likely to be nonexistent at this point. Is this occurring with the latest Arnold release, or with any of the 1.4 series? I may suggest reaching out to Solid Angle support on this as well, see if they can test this in house.

What version of 2015 are you using? Do you have any service packs installed or the extension?

[Anonymous]

You got a valid point and I agree, it's just at my workplace I have to wait till they deploy the new maya version on all the company, which takes time with all the testing and internal plugins integration etc etc... And since everyone else is already happy enough with 2015, they don't seem to try go faster, that's why I'm currently stuck on 2015.

Anyway currently the workaround I do is by a small script I made, it basically closes the arnold render view window with the command : 

cmds.arnoldRenderView(mode="close") 

Then it saves, and it re-opens the same window with :

cmds.arnoldRenderView(mode="open")

 It still slows down my workflow sicne I have to re-update the scene and re-render each time I save.

I'm using the latest arnold version, I contacted solid angle and they said they can reproduce this error on maya 2015 too but not on 2017. The mysterious thing is we didn't have this error before, and the moment I started having it, another colleague of mine started having it couple days later, and then another colleague is having it too. And no matter what we do (reset prefs, reinstall arnold etc...) the problem stays.. It's contageous and once you get it, it never leaves ! 

EDIT : forgot to answer your question about maya version, it's maya 2015 SP5 no extention

[Anonymous]

Now that is interesting. It's good that SA was able to reproduce it, though. Did they mention anything about looking into providing a fix, or maybe giving you guys a hot fix build until the next official release?

If anything, I would talk with your lead or IT person who determines what software you guys use and see if the version you're on now has any killer features that are necessary to production, compared to the previous release.

I was going to say that maybe there was something wrong with a central install (if that's what you do) but since SA could see the same, that pretty much nullifies it.

[Anonymous]

I wish it was as simple as getting an IT for the issue ^^' it's way bigger than that hence more complicated, anyway we are trying our best to be able to use maya 2017 at least on our small team that work on CG films, not sure if we'll have to pay extra or it's just a matter of updating the software for free.

For solid angle, not sure about a hot fix, but they said they are looking into the problem, I received a message from them saying that reseting prefs work, but it didn't work for me.

[Stephen.Blair]

Also, it's not reproducible. Tested on three different machines so far.

I did repro once, but after resetting the preferences, it was no longer repro.