Maya 2014 Extension Download
Maya 2018.2 Update. Maya 2018. Maya 2017.
Maya 2016 Extension 2. Maya 2016 Extension 1. Maya 2016. Maya 2015 Extension 1. Maya 2015. Previous versions of Maya To install the Maya Help to your computer or to a local network location, click an installer from the supported language and operating system choices in the table below. For more information, follow these links:.
Windows Mac OS Linux English Japanese Simplified Chinese Important Notes:. Installers above that are marked Ext include documentation for both the major version and the subsequent Extension in the same help system. The zip files posted here do not include an exe file to install the local copy of the Help. You need to extract it first and double-click index.html to open the Help.
Limitations The following section describes limitations, workarounds (where applicable) about this release. Bug Number Summary Component/s Limitation/Workaround Bullet Nodes are documented in the Maya Help in the Bullet Reference section Bullet Node Documentation The Maya Node Help omits information that concerns the Bullet nodes so Bullet Node links in the UI return an error.
Bullet Nodes are documented in the Maya Help in the Bullet Reference section. MAYA-21806 Fixed a problem with resolving file names permanently File Referencing, FileIO Maya Scene files containing unfound Reference file(s) can now be permanently resolved when using the 'Make path changes permanent' checkbox along with the 'Browse' option (enables the user to browse to where the reference file is located) in the 'Reference file not found' dialog. If the 'Make path changes permanent' checkbox is not used, then the path changes used to resolve the unfound Reference files are not made permanent.
This option does not work on scenes containing nested file references. This works on Top-Level Reference files only.
In order to permanently resolve nested references, the nested reference scene files must be independently opened and resolved. Additionally, the 'Remember these settings' option in the 'Reference file not found' dialog now works with the 'Abort File Read' option for scene files containing unfound file references. When the 'Remember these settings' checkbox is enabled, and you select 'Abort File Read', all references that are normally read and loaded into the scene at File Open are ignored (in other words, no unresolved references files are loaded). MAYA-27931 Heavy caches ( 2G) exported by gpuCache/AbcExport cannot be imported back by gpuCache and produces one error when imported by AbcImport Cache Representation - Alembic, Cache Representation - Baked Geometry This problem is caused by a limitation of Visual Studio 2010 and is fixed for Maya built-in Alembic/gpuCache plug-ins by patching the headers of Visual Studio 2010. However, you may encounter the same problem when trying to build Alembic/GPUCache plugins with Visual Studio 2010 by yourself. Workarounds: 1.
Customize the headers of Visual Studio 2010 and rebuild Alembic libraries. Use Visual Studio 2012 or newer version.
Autodesk Maya 2014 Extension Download
More details about how to patch the headers of Visual Studio 2010: FPOSOFF macro is used in both fstream and iosfwd. In Visual Studio 2010, it's defined as FPOSOFF(fp) = (long)(fp). In Visual Studio 2012, it's defined as FPOSOFF(fp) = (long long)(fp). Fp is truncated to a 32-bit integer from a 64-bit integer in VS 2010. MAYA-28353 XGen: default Renderer is set to 'none' XGen Manually set to mental ray in the Preview output tab. MAYA-23332 XGen: 'Seexpr' shader not working XGen To use seexpr, the variable must be referenced by setting its name in the Name 0, Name 1. And so forth slots of the seexp attribute page.
This means that there is a limitation of 8 custom shader parameters. For example, if you are rendering normals, you can set the seexpr expression to $N. You must also take the extra step of setting Name 0 to N. You can also reference custom shader parameters in the Customs box at the bottom of Seexpr. MAYA-23047 XGen: mental ray can crash with higher densities XGen MAYA-28299 / MAYA-26243 XGen cannot be loaded under Windows user name with upper ASCII characters XGen, Localization XGen does not support file names or file paths with upper-ASCII characters and double byte characters. As a workaround, users should: - install Extension for Maya 2014 using a lower-ASCII user name in Windows - avoid installing Maya to a custom location with upper-ASCII and double byte characters - avoid saving or opening scene names with upper-ASCII and/or double byte characters MAYA-28239 'kPolyCBoolOp' has been added to the end of the MFn::Type enum.
API, Documentation MFn::kLast for Extension for Maya 2014 is one greater than that of Maya 2014. Plug-ins built against Extension for Maya 2014 that wish to retain backward compatibility with Maya 2014 must therefore avoid using MFn::kPolyCBoolOp, and should either avoid using MFn::kLast or take suitable steps to make sure that its value is decremented by one before using it in Maya 2014. MAYA-23695 saveImage command doesn't work correctly for shaded objects Rendering, Scripting The saveImage command does not work as expected for shaded objects. To workaround this problem, you can execute the following script to take a snapshot of the current scene view and save it as a endSnap.jpg file, to the images directory of your project directory. This workaround can be used for both the default viewport and Viewport 2.0.
String $ws=`workspace -q -fullName`'; evalDeferred 'string $wsp=$ws + '/images '; evalDeferred 'sysFile -makeDir $wsp'; evalDeferred 'string $wspf = $wsp + '/endSnap.jpg '; evalDeferred 'refresh -cv -fe 'jpg ' -fn $wspf;'; MAYA-28254 Maya 2014 SP 1 crashes when invoking Send To from Softimage 2014 SP 2 File I/O Workaround: Ensure that both Softimage 2014 SP 2 and Maya 2014 SP 1 or SP 2 are running before using the One Click functionality.