Maya 2018.4 - crashes importing .mb or .ma

[Anonymous]

We are having a "seemingly" random issue where Maya will crash when trying to import a .mb or .ma file.  Could be a simple or heavy file.  Crashes, saves crash file, send error report.  Once it happens, the problem will persist with new instances of Maya and importing any maya file until the workstation has a full shutdown & reboot.  Sometimes the same file will import without issue, other times not.  Tested many workstations, new Maya preferences, the most basic scenes... can not find the issue here.  Only has started since updating 2018.3 to 2018.4.  Need to stay on this version due fixes made when rendering MASH...

Windows 10, Maya 2018.4

I have the log files from our most recent crash.  

-Scott

[sean.heasley]

Hi @Anonymous

Thanks for providing all of that informtion!

Can you please provide the crash logs as well as the CER Report number that is generated when you send the error report to us?

Please let me know if anything changes!

[Anonymous]

Attached are the crash files generated by Maya.

-Scott

[sean.heasley]

Hi @Anonymous

The crash log is pointing to dome dll files and there have been a few similar issues lately with these types of files.

To fix this, you'll want to make a back up of the problem .dll file or files and then remove them from their folder and then try to work in Maya.

The most common .dll file causing this issue is igdrclneo64.dll. 

You can find these dll files here:

C:\Windows\System32\DriverStore\FileRepository

Please let me know if this works or if you need any more assistance!

If one or more of these posts helped answer your question, please click Accept as Solution on the posts that helped you so others in the community can find them easily.

Kudos are greatly appreciated. Everyone likes a thumbs up!

[Anonymous]

I can't locate that file on my system.

[mspeer]

Hi!

In Preferences make sure to use Render Setup (and not Legacy Render Layers).

[Anonymous]

Render Setup is not an option for us at this time.  Our pipeline is built around render layers, and more importantly, some plugins do not like render setup.  The attribute editor goes buggy and does not display tabs properly.

[Anonymous]

New info:  I can reference a file, then import the reference just fine...

[mspeer]

Hi!

That's a bug in Maya 2018.4.

The workarounds are:

a) Reference...Import, and

b) copy/paste

[Anonymous]

A bug that Maya will have a fatal error importing it's own file types?  I'm sorry but that is ridiculous... a big monkey wrench into any studio's workflow.

[sean.heasley]

Hi @Anonymous and @mspeer

This is a known issue that was logged a few weeks ago. It's only happening with Legacy Render layers so you can either follow the steps mspeer provided and/or use our standard Render layer set up if you wish to avoid this issue.

[Anonymous]

If use "Legacy Render Layers", try to import a file after unloading "renderSetup.py" from Plug-in Manager.

It will not crash.

[Anonymous]

This works, thank-you. 

Is an update coming that will fix this?  I have tried turning off auto load for that plug-in, but it will still force it's way back.

[Anonymous]

As a temporary solution to the problem, set scriptJob in userSetup.py.

evalDeferred is useless in this case.

def unloadRenderSetupPlugin(*args):
    cmds.unloadPlugin('renderSetup.py')
cmds.scriptJob(runOnce=True, e=["idle", unloadRenderSetupPlugin])

[StudioPoint]

I can confirm that the same problem exists in Maya 2018.5 so no fix for this and it looks like Autodesk does not care about the problem even I am sure they know about it. It is VERY ridiculous when you can not import maya scene files in maya like you should be able to do... And excuses about using legacy render layers... ... Amazing..!

[slimboJoe]

Holy moley, it's always something!

This problem is stupid.

And it affects the EFFECT EXAMPLES, too.  So, trying to load an included example scene causes Maya to crash.  What an intro to a new user.  Like driving a new car off the lot, only to have the steering wheel come off and drive straight into a brick wall and burst into flames.

[Anonymous]

Hiya, 

I am having this issue where I can open up an .mb file but not an .ma

I have checked the crash log for the one that mentioned at the top of the conversation and its not there.

I have checked the Render settings and they are not Legacy.

mb files open fine.

What do I do please?

Thanks, 

Sinead