Thank you for downloading Autodesk® Maya® 2015 Service Pack 3.
This document describes known limitations, issues and fixes in Autodesk Maya 2015 Service Pack 3. It is strongly recommended that you read this document before you install this release. For reference, you should save this readme to your hard drive or print a copy.
For complete instructions about uninstalling and installing this product see: Maya Installation Help
To learn about new features in this release see: What's New in Maya
For complete documentation and resources, see: www.autodesk.com/maya-docs
For certified hardware, see: www.autodesk.com/graphics-hardware
For more Maya Support, see: www.autodesk.com/maya-support
Fixes included in this release are detailed in the following list containing bug numbers and corresponding descriptions.
| Bug Number | Description |
| Animation Character | |
| MAYA-39263 | Fixed an issue with blendShape DG evaluation |
| Animation General | |
| MAYA-38633 | Skinning : some vertices change position after skinning |
| MAYA-39722 | GraphEditor : file will not save after changing keys in graph editor |
| Bifrost | |
| MAYA-34091 | Collider : full DAG name not recognized, causing name clashing |
| MAYA-37475 | Bifrost : Address overwriting user caches |
| FBX | |
| MAYA-36106 | Update FBX SDK to version 2015.1 (see FBX Help for more information about this update) |
| Foundation | |
| MAYA-38274 | Fixed an issue with libc.so.6: version GLIBC_2.12 not found on Linux |
| MAYA-39444 | Update to OpenSSL 1.0.1h on Windows |
| Installer | |
| MAYA-38601 | mental ray for Maya 2015 patch cannot be uninstalled correctly |
| MAYA-39064 | Speed up Maya 2015 patch install time |
| mental ray | |
| MAYA-35143 | Fixed the initial delay before first image when progressive rendering |
| MAYA-36872 | GPU cache deforming animation does not change during batch rendering |
| MAYA-38026 | Remove the little white frame when progressive rendering |
| MAYA-40003 | maya_volumefog default for refractions/reflections is off |
| MAYA-40039 | mayabase.lib missing from mentalray devkit 2015 |
| MAYA-40393 | createMentalRayQualityTab.mel triggers error about missing control |
| Multiple Representation | |
| MAYA-35169 | Maya crashes when editing keys of scene assembly nodes / assets in channel box |
| Rendering | |
| MAYA-36887 | Fixed a crash when opening a legacy scene with mental ray area light |
| MAYA-37004 | MPxShaderOverride not always consolidating |
| MAYA-38304 | Transparent instances are being drawn twice in the legacy pipeline |
| MAYA-39524 | Allow for API access to shared QGLWidget to allow customer widgets to share GL contexts |
| XGen | |
| MAYA-39003 | Fixed an issue with soft selection not working on guides |
| MAYA-34137 | Add support for xgen_ptex_lookup, xgen_hair_length_mapping, xgen_root_tip_color_blend shaders, providing more control in customizing the XGen hair shader |
The following section describes limitations, workarounds (where applicable) about this release.
| Bug Number | Description |
| Bifrost | |
| MAYA-32190 | Due to limitations in the viewport and some missing libraries, the viewport mesh shader will not resemble the MR render for the bifrostLiquidMaterial. Vorticity is not supported in the viewport and diffuse weight remap is handled differently. |
| MAYA-32763 | The default value of 0.5 for Master Voxel
Size may be too small to generate voxels on some emitting meshes below
a specific scale, including primitives. For example, no voxels will be
generated for a default polySphere with radius=1. Workaround : To generate voxels, either lower the Master Voxel Size or increase the size of the sphere. |
| MAYA-32869 | Bifrost scene is getting evaluated over
and over during batch render when runup is enabled.
Workaround: Disable Runup. |
| MAYA-33411 | Bifrost: Separate thickness required for
shell and solid. The default thickness for an emitter is 0. This is good for a solid but for a shell it produces no results. Must be at least set to 1. For colliders, the default thickness is set to 1. This is fine for solids, but for shells, even at high resolutions this results in penetrating liquids. It must at least be set to 2. |
| MAYA-33644 | Bifrost: Resulting Simulation motion seems
incorrect and seems due to Collision objects Conversion Thickness. Fluid will react with a surface tension type behavior even when stickiness is set to zero. |
| MAYA-33722 | Bifrost: Interior Particle Density requires a hard set minimum limit of 1. |
| MAYA-33828 | Currently, setting keys attributes found on the bifrostLiquidContainer is not a supported workflow. |
| MAYA-34114 | Bifrost will still render even after
disabling the display of particles and voxels in the Bifrost Shape Workaround : Hide the Bifrost object (set visibility=off). |
| MAYA-34177 | The default maximum particle viewport display number is set to 1 million. This creates repetitive looking patterns for higher resolution simulations. Respecting the limits of your graphics card, you can increase the number for a more accurate representation of the simulation. |
| MAYA-34338 | Certain mesh colliders will crash Maya |
| MAYA-34412 | Self-intersecting attached mesh will fail to emit Bifrost particles |
| Cache Representation - Alembic | |
| MAYA-39350 | Alembic cache exported by Alembic 1.5.4 may crash Maya 2013 (Alembic 1.0.4) and Maya 2013.5 (Alembic 1.0.5) when importing through gpuCache and Alembic importer. This is a forward compatibility problem. Alembic only maintains backward compatibility, but not forward compatibility. |
| Cache Representation - Baked Geometry | |
| MAYA-31013 | Maya will crash during Windows remote
desktop session if you try and import a gpu cache. Workaround : 1. On the host system, set Viewport 2.0 as the default renderer for the workspace. You cannot do this using the client. 2. Access Maya on the host system using the client. |
| Foundation | |
| MAYA-30309 | OSX 10.9: Hotbox and marking menus will
not work on second screen of a dual screen setup Workaround: under System preferences > Mission Control > [ ] Displays have Separate Spaces Uncheck the "displays have separate spaces" option. This will bring the OSX work spaces behavior back to the way it was before 10.9 |
| MAYA-38390 | Problem: On OSX, the Apple Magic Mouse can
cause Maya to crash unexpectedly. Workaround : Another type of mouse should be used. |
| Installer | |
| MAYA-20117 | Install fails on a clean Windows 8
computer with a message about an internet connection Workaround : in windows command shell (cmd.exe) type gpedit.msc and press enter This will open The Local Group Policy Editor In here do Local Computer Policy > Computer Configuration > Administrative Templates > System Under the System category, find and double click the policy setting titled: "Specify settings for optional component installation and component repair" In the settings that open check "Enabled" and Under the Options: check "Contact Windows Update directly to download repair content instead of WSUS" Then, download .NET 3.5 from microsoft website and install Then, Maya should install and not get hung at the .NET 3.5 portion and return an error saying no internet connection. |
| Localization | |
| MAYA-18046 | If you a running Maya in a Simplified Chinese environment, switch between the standard view and full-screen view of the current panels using the Ctrl + Shift + Spacebar hotkey. |
| MAYA-28299 | 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 |
| Multiple Representation | |
| MAYA-19686 | Scene Assembly nodes do not handle file reference representations well if they have proxies |
| MAYA-20004 | The Attribute Editor's texture sample
preview will show a broken swatch icon (red X) when loading a Scene
Assembly containing an object with a texture. Workaround : Leave it un-previewed. or set in the Maya preferences under the Display categories Max res. for swatches something larger than the estimated texture size. |
| MAYA-21565 | The currently active tool (move, rotate, scale, etc...) manipulator handle focus will be lost at Scene Assembly representation switching. |
| MAYA-21592 | Attempting to open the Namespace Editor on a complex Scene Assembly scene (1000's - 10,000's of objects) will hang Maya for an undetermined period of time until the Namespace contents have been loaded. Namespace Editor workflows are not recommended for complex Scene Assembly Scenes. |
| MAYA-22055 | Using the python() MEL command with MFnAssembly may crash Maya |
| MAYA-22088 | Undo after Reference/Scene Assembly
Reference edits have been made does not completely clear out the edits Workaround : Remove the zero'ed out edit by using the remove edits function. |
| MAYA-22191 | Attaching a Scene Assembly scene file representation to a motion path is not currently supported |
| MAYA-22211 | Blend shapes fails to function when used to create Blends between Assembly members and other objects |
| MAYA-22222 | Set Driven Key workflows are not currently supported when the Scene Assembly scene representation object is used as driver |
| MAYA-22361 | Character sets is not supported by Scene Assembly |
| MAYA-22410 | Deleting anim curves connected to a SA reference may produces incorrect edits |
| MAYA-22446 | Importing ATOM of set driven key data fails on Scene Assembly |
| MAYA-22643 | Un-parenting representation from Assembly Reference node will display the un-parented node twice in the outliner |
| Rendering | |
| MAYA-16289 | When the Double Sided Lighting option
under the DirectX 11 Shader Attribute Editor is enabled, backfacing
polygons caused by negative scaling may turn black. Workaround : You should reverse normals after scaling negatively. |
| MAYA-18501 | When running the scene view in overlay
render mode, you may not be able to override your renderer. For example, when running the marqueeTool from the devkit, when the marqueeTool plug-in is executed, you enter into overlay render mode. If you then try to override your renderer (by switching to a custom renderer via the Renderer menu), the heads up display still indicate Viewport 2.0 even though the custom renderer radio button is selected. To work around this issue, refresh the scene view by tumbling the camera. |
| MAYA-23695 | 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. tring $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-24576 | When depth peeling is chosen as the transparency algorithm for Viewport 2.0 (in Hardware 2.0 Renderer 2.0 Settings window), MSAA can only take effect on opaque objects but not transparent objects. |
| MAYA-30655 | For scenes with nCloth, if you execute the
following commands multiple times: 1. "currentTime n1" 2. "runup -mxf n2" Viewport 2.0 cannot reach frame n2; instead, it always remains at frame n1. |
| MAYA-30985 | When both backface culling and GPU instancing is on, negative-scaled objects may show inconsistent culling result in VP2. The work-around so far is to temporarily turn off GPU instancing in VP2 option dialog. |
| MAYA-35665 | Older drivers for 1800M may crash Maya. Workaround : Please update to a newer driver. |
| Scripting Python | |
| MAYA-17358 | "os.path.expanduser()" returns different
results when on the GUI on Windows. Workaround : 1) Initialize the Maya environment within mayapy. import maya.standalone maya.standalone.initialize() Now os.path.expanduser() will return the same value in mayapy as it does in Maya. 2) Set the HOME environment variable before starting up Maya. Whatever you set it to will be used by by os.path.expanduser() in both Maya and mayapy. |
| UI Architecture | |
| MAYA-7804 | The Ctrl-W hotkey cannot be assigned to Maya functions. It is reserved. |
| UI General | |
| MAYA-1688 | Auto-complete python commands in the script editor will run the codes inside a Python property block, not just returning the function/property list, but actually running the property itself. The same is true when you hit return to accept and fill that function/property in the script editor. |
| XGen | |
| MAYA-23962 | XGen is not compatible with merged meshes |
| MAYA-28065 | XGen: Clumping preview refresh issue When having a bad preview after altering clump maps, press preview again. |
| MAYA-35042 | Loading Xgen may crash Maya if
fabricengine plugin is installed. Workaround : Rename the PySide folder under the fabricengine install directory. |
| MAYA-36215 | Xgen Tube Groom requires tubes to have transformations frozen |
| MAYA-37306 | Do not use spaces for your XGen project's name on Mac. |
| MAYA-37969 | Xgen and the geo that it is bound to have to be in the same namespace. It is not supported to import an XGen description or collection on a piece of geo in a different namespace. |
| MAYA-39333 | Xgen control guides Soft-select falloff colour is not yet supported. |
Copyright © 2014 Autodesk, Inc.