Maya 2018.3 OSX slow at start up

[mrwallin]

Been running Maya 2018 on my iMac Pro for the past month with no issues. Updated to 2018.3 a few days ago and now get a freeze (beachball) at start up for a couple minutes. I've tried total uninstall and reinstall numerous times and keep getting the same issue. I even tried going back to the previous version 2018.2 which was working fine and it also has the same issue. 

Also, if I try to "login" with my account in the Maya interface, it also kicks back a beachball and won't let me ever get the dialogue box to login.

I've deleted old prefs and all. Still no avail. Any ideas? 

I do see a few strange errors in the script editor at start up and have attached them below:

file -f -new;
// untitled //
commandPort -securityWarning -name commandportDefault;
onSetCurrentLayout "Maya Classic";
// Error: file: /Applications/Autodesk/maya2018/plug-ins/xgen/scripts/xgmToolRegistration.mel line 58: Cannot find procedure "xgmToolManagerRegisterTool". //
// Warning: file: /Applications/Autodesk/maya2018/plug-ins/xgen/scripts/igInitialize.mel line 78: Couldn't source xgmToolRegistration.mel //
// Warning: file: /Users/megatron/Library/Preferences/Autodesk/maya/2018/prefs/filePathEditorRegistryPrefs.mel line 4: filePathEditor: Attribute 'aiImage.filename' is invalid or is not designated 'usedAsFilename'. //
// Warning: file: /Users/megatron/Library/Preferences/Autodesk/maya/2018/prefs/filePathEditorRegistryPrefs.mel line 5: filePathEditor: Attribute 'aiPhotometricLight.aiFilename' is invalid or is not designated 'usedAsFilename'. //
// Warning: file: /Users/megatron/Library/Preferences/Autodesk/maya/2018/prefs/filePathEditorRegistryPrefs.mel line 6: filePathEditor: Attribute 'aiStandIn.dso' is invalid or is not designated 'usedAsFilename'. //
// Warning: file: /Users/megatron/Library/Preferences/Autodesk/maya/2018/prefs/filePathEditorRegistryPrefs.mel line 7: filePathEditor: Attribute 'aiVolume.filename' is invalid or is not designated 'usedAsFilename'. //
// AbcExport v1.0 using Alembic 1.7.5 (built Feb 7 2018 13:51:52)
evalDeferred "shaderBallRendererMenuUpdate";
// Warning: line 1: filePathEditor: Attribute 'aiStandIn.dso' and label 'Standin' have been saved already. //
// Warning: line 1: filePathEditor: Attribute 'aiVolume.filename' and label 'VDB' have been saved already. //
// Warning: line 1: filePathEditor: Attribute 'aiImage.filename' and label 'Image' have been saved already. //
// Warning: line 1: filePathEditor: Attribute 'aiPhotometricLight.aiFilename' and label 'IES' have been saved already. //
import arnold
// Successfully imported python module 'arnold'
import mtoa
// Successfully imported python module 'mtoa'
import mtoa.cmds.registerArnoldRenderer;mtoa.cmds.registerArnoldRenderer.registerArnoldRenderer()
// Successfully registered renderer 'arnold'
// Warning: file: /Applications/Autodesk/maya2018/Maya.app/Contents/scripts/startup/autoLoadPlugin.mel line 35: Loading plug-in "mtoa" has resulted in changes to the scene that may need to be saved. //
// AbcImport v1.0 using Alembic 1.7.5 (built Feb 7 2018 13:51:52)
updateRendererUI;
updateRendererUI;

[Anonymous]

Can you launch Maya from the command line and see if there’s any abnormal output?

Cheers,
Mike

[mrwallin]

Good suggestion. I have launched from the command line and am still seeing the same slow “beach balling” open. Its like its hung up on a particular process that it cannot complete or is struggling to resolve.

[Anonymous · Accepted solution]

Do you have anything set in the Maya.env file? If so, try clearing and see what happens. If you don’t, try adding the following lines:

MAYA_DISABLE_CIP=1
MAYA_DISABLE_CLIC_IPM=1

If you use TextEdit, make sure you put it in Plain Text mode (Format > Plain Text).

The first line disables your participation in the Customer Involvement Program (which pings Amazon), and the second will disable the in app licensing menu (CLIC for license and IPM for ‘in product messaging’).

Cheers,
Mike

[mrwallin]

Brilliant! Your suggestion 100% fixed it. Maya now launches almost instantly. 

Thank you! 

[Anonymous]

Great to hear! I don’t run macOS, but I have these variables set as well. No need for them, not going to waste resources on them. And they are also well known to fix macOS problems back to 2016/2016.5.

Cheers,
Mike

[Anonymous]

I want to thank you too. I have the same iMac Pro and it was taking forever to start but now, Maya starts up almost instantly for me too. YAAAYYYYY

[Anonymous]

Thank you! I am on a MacBook Pro and every time Maya 2018 would launch I would have to wait for over 5 minutes to load and sometimes the rainbow loader would just hang there. I added your 2 lines of text to the .env file and it is finally starting quick!! Thanks again

[Anonymous]

hi, could you please describe how to and where to insert the file, the directions you give (the folder) doesnt exist on my mac Mojave for Maya 2018.

Thank you!

[JORGE_RAMOSRR66S]

Hello,

I have Maya 2018 (Mac High Sierra) and have the same issue of Maya taking too long to start up and also crashes when using the channel box most times if I stop using Maya and go back to it later.

I've read your reply about using command line (Terminal) and that it worked for some people.

My problem is that i never use command line before and although it doesn't seem to difficult and don't know what the lines are to startup Maya from command line and fixed my issues. You provided two lines MAYA_DISABLE_CIP=1
MAYA_DISABLE_CLIC_IPM=1 , but don't I need a line to startup Maya first and what else do I need? Can anybody else help please. I would truly appreciate it.

Jorge

[Anonymous]

Go to Finder > Go > Go to Folder 

Type ~/Library in the text field

This will open the library folder 

Locate Preferences -> Autodesk -> Maya-> 2018 

Maya.env should be there

Hope this helps

[avtpro5]

MAYA_DISABLE_CIP=1
MAYA_DISABLE_CLIC_IPM=1


I had a crazy beach ball problem and this fixed it immediately. Soon as I take it out of the Maya.env, then it stalls again. Never had the problem with Maya stalling like this but this worked. Thanks

[Anonymous]

Thank you! I was stuck in this issue too, wasted a lot of time searching answers and asking to forum. Finally your help was decisive to solve my problem. It works wonderfully now! I'd drop a ton of kudos