Maya 2018.4 crashes when calling MLL export plugin.

Maya 2018.4 crashes when calling MLL export plugin.

Anonymous
Not applicable
726 Views
3 Replies
Message 1 of 4

Maya 2018.4 crashes when calling MLL export plugin.

Anonymous
Not applicable

We have a maya exporter (a .mll plugin that has a subclass of MPxFileTranslator) that we've been using for some time.  After a recent update (to Maya 2018.4 I believe) I'm getting the following behavior:

1) The exporter loads successfully.

2) When I try to export the maya file maya hits an exception before every calling my MPxFileTranslator::writer function and consequently never calls my writer function.

Is this a known issue?  I have rebuilt the plugin thinking that maybe I just needed to link in new libraries but that doesn't seem to have fixed it.  Any support would be helpful.

 

Chip

Accepted solutions (1)
727 Views
3 Replies
Replies (3)
Message 2 of 4

Anonymous
Not applicable

I'm having the same issue here. No hard crash for us, just a non-responsive call, however we did not recompile our exporter for 2018.4. The plugin itself did load into maya, but did not work.

 

Rollback is a pain, you cannot uninstall the update even with the methods described on this forum. It required a full uninstall to get back to a working version; 2018.2

 

I was under the impression from Autodesk sales staff that Autodesk were embarking on a new way of updating their software that would not require re-compiles of plugins for ANY updates. At least that's what I was told in our recent meetings.

0 Likes
Message 3 of 4

Anonymous
Not applicable
Accepted solution

As a follow up: I was able to resolve this issue by making a copy of the Autodesk sample plugin for rawexport and then merging our code into that project while deleting the sample code. I never really determined what was causing the issue, but I suspect it was either a project setting or an older lib we were linking into our project that we no longer needed.

Message 4 of 4

Anonymous
Not applicable

I was running into the same issue trying to build a plugin for 2019.2. It turned out that we needed to enable the "/GR" compile flag for run time type information.

0 Likes