- AUTODESK MAYA 2017 MESH LIBRARY MAC OS X
- AUTODESK MAYA 2017 MESH LIBRARY MOVIE
- AUTODESK MAYA 2017 MESH LIBRARY INSTALL
- AUTODESK MAYA 2017 MESH LIBRARY MAC
- AUTODESK MAYA 2017 MESH LIBRARY WINDOWS
You can store shelves in a location accessible by different groups who then set the MAYA_SHELF_PATH variable for their workstation. Specifies the directories that Maya searches to access the shelves. You must either change or remove the variable. After setting the variable, you cannot change the location of the project folder from the Preferences window. In the Preferences window, under File/Projects > Project Settings, the folder location is displayed as Default projects directory. Specifies the location of your project folder.
AUTODESK MAYA 2017 MESH LIBRARY MAC
under your Home folder, in Library/Preferences/Autodesk/ Maya.īeginning Maya 2013, for the Linux and Mac platforms, there are checks to ensure that the directory pointed to by lastLocalWS is accessible before Maya attempts to use it.under your Home folder, in Library/Preferences/Autodesk/ Maya/.Instead, use the following alternate locations:
AUTODESK MAYA 2017 MESH LIBRARY MAC OS X
Since Mac OS X architecture makes it difficult to access the contents of the Maya application package, we strongly discourage the use of MAYA_LOCATION on Mac OS X.
On Mac OS X, Maya is installed as /Applications/ Maya /Maya.app. If it is not set, it defaults to /usr/autodesk/ MayaVersionNumber (Linux) or C:\Program Files\Autodesk \ MayaVersionNumber (Windows). The path for the Maya installation directory.
AUTODESK MAYA 2017 MESH LIBRARY MOVIE
This variable is used to override the directory where movie files are found. You can avoid this problem by only specifying file paths that do not include spaces. If you use spaces in a file path that you create, you may have problems accessing icon image files stored within that directory, because the file path does not appear in Maya. The following tables list the default paths, which will always follow any path that you specify. See the individual descriptions of these variables below and Distributing Maya Plug-ins in the Maya Developer Help for more information.
AUTODESK MAYA 2017 MESH LIBRARY INSTALL
Maya will append subdirectories of this install location to the following path variables: MAYA_PLUG_IN_PATH, MAYA_PRESET_PATH, MAYA_SCRIPT_PATH, PYTHONPATH and XBMLANGPATH. A module file describes the install location of a plugin which has been distributed as a module. See XBMLANGPATH as this variable should be used instead.ĭefines the search paths for Maya module files. This variable has become obsolete since Maya 3.0. See Customizing the list of node attributes for more information. By default, your templates are saved to $MAYA_APP_DIR///prefs/viewTemplates/, but you can override the default location by setting this environment variable to the location that you desire. You can customize the list of attributes displayed for each node by creating a custom attribute list template.
AUTODESK MAYA 2017 MESH LIBRARY WINDOWS
This environment variable supports multiple paths that can be separated with on Windows and : on Mac OS X/Linux.įor use with the Node Editor. You can share these templates with other users on the network by setting this environment variable to the network location at which the custom templates are found. The next time that you create the same node, Maya searches for an existing template, and if one is found, then your node is displayed with the custom attribute list that you created. When used with the Node Editor: you can customize the list of attributes displayed for each node by creating a custom attribute list template. The default is the scripts\AETemplates folder of the Maya install directory. When used with the Attribute Editor: this variable is used to override the directory where custom Attribute Editor templates are found. Plug-ins can add to this path with their own content directories by adding to the environment variable in their module template files, or by using the assetBrowser -addContentPath flag. This variable obtains the paths to the content directories with which you can populate the Examples tab in the Content Browser. The content in the Script Editor displays in both the Script Editor and the designated output location.