Autodesk Maya 2015 Service Pack 2 Release Notes 

Thank you for downloading Autodesk® Maya® 2015 Service Pack 2.

This document describes known limitations, issues and fixes in Autodesk Maya 2015 Service Pack 2. 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:

For certified hardware, see:

For more Maya Support, see:

Return to Top

Fixes included in this release are detailed in the following list containing bug numbers and corresponding descriptions.

Bug Number Description
Animation General  
MAYA-18743 AnimLayers : Command does not return unique names when queried
MAYA-35713 Fixed a crash when loading some Maya 2013 files
MAYA-34435 Cannot perform render layer override on any Bifrost nodes
MAYA-36566 Bifrost: Scratch cache is affecting Batch with User Cache
MAYA-36704 Bifrost voxel display displays incorrectly with anomalies in wireframe mode.
MAYA-38193 bifrostLiquidMaterial renders black
Cache Representation - Baked Geometry  
MAYA-35582 Graphic card info cannot be detected correctly by gpuCache on the new Mac Pro
FileIO Maya  
MAYA-37309 MPxFileTranslator cannot resolve URI paths
mental ray  
MAYA-37089 Mental Ray IBL: IPR doesn't update automatically when changing the "emit light" features
MAYA-37371 Deleting single layer in mila_material AE interface causes error
MAYA-24623 Insert Edge Loop in Multi-Cut and Quad Draw does not always work correctly
MAYA-26003 If a shape node is named the same as a default camera name (top, side, persp, front) changing to that camera view via the Hotbox creates a new camera
MAYA-31834 Quad Draw, Relax Border Vertices - Shift+MMB drag in area of mesh which doesn't include border vertices will crash
MAYA-33650 Quad Draw fill hole function can sometimes create polys with inverted normals
MAYA-33753 Multi-Cut Slice Tool results are not always correct
MAYA-34671 Files that contain meshes with their tangent space coordinate system set to left-handed don’t re-load properly back into Maya
MAYA-35385 UV texture Editor, Image Range is not working correctly
MAYA-35789 In some cases material assignments are missing after bevel
MAYA-35795 Edit Mesh ->Duplicate options is missing
MAYA-35982 Maya may crash turning on Smooth Mesh Preview (3 key) when the Subdivision Method is OpenSubdiv and a UV Set named “map11” is present
MAYA-37327 MFnMesh getClosestPoint fails without accelerator
MAYA-37420 Some runtimeCommands incorrectly expose variables at a global scope, and those variables can't have their type changed
MAYA-37703 Breaking the connection between a texture node and a displacement node on a mesh using OpenSubDiv method may cause crash
MAYA-34377 Image Plane - attribute change display issue (default renderer)
MAYA-36298 Viewport 2 with large models causes graph editor slowdown
MAYA-36713 Renaming Paint Effects stroke node breaks visibility in VP2.0
MAYA-38044 Crashing with MacPro AMD 500/700 with Softmodification in VP 2.0
UI Attribute Editor  
MAYA-32418 AE errors occur when 'short' node name is not unique
MAYA-36994 Can't drag and drop connections onto torn off/copied tab of Attribute Editor anymore
UI General Editors  
MAYA-9496 Fixed an issue with channelBox -attrColor and -attrBgColor flags not being supported
MAYA-35663 XGen: Can't Motion Blur with mental ray

Return to Top
The following section describes limitations, workarounds (where applicable) about this release.

Bug Number Description
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 - 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.
MAYA-30309 OSX 10.9: Hotbox and marking menus will not work on second screen of a dual screen setup

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.
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.
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 well file reference reps 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.
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-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
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.
MAYA-38479 Problem : Maya Vector renderer can cause Maya to crash.
Workaround : Another renderer should be used.
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

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 Python Autocomplete Running property blocks
MAYA-9651 Non alphabetic shifted hotkeys do not work with Control modifier
Workaround : Assign a different key
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.

Return to Top

Copyright © 2014 Autodesk, Inc.