Thank you for downloading Autodesk® Maya® 2015 Service Pack 1.
This document describes known limitations, issues and fixes in Autodesk Maya 2015 Service Pack 1. 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
This release addresses the Heartbleed security vulnerability with an update to OpenSSL.
Additional fixes are detailed in the following list containing bug numbers and corresponding descriptions.
|MAYA-35912||Fixed a crash when switching from vertex to object view with IK spline handle selected|
|MAYA-36199||Geodesic Voxel Binding : Fix smoothing due to errors in one-ring vertex neighborhood|
|MAYA-36359||Maya's auto-connecting "inverseScale" attribute of joints when they get parented is problematic|
|MAYA-33464||Bifröst: Submitting more frames after stopping BGC ruins the simulation and timeline display|
|MAYA-33541||Bifröst: "Stop" button creating gap in scratch cache|
|MAYA-33615||Bifröst: startFrame doesn't appear in the Channel Box|
|MAYA-34373||BifröstLiquid mental ray framebuffers don't render (affects render passes support)|
|MAYA-34834||Bifröst Scratch Cache lost when going back to first frame with animated parameter|
|MAYA-35064||Bifröst shader doesn't render with alpha|
shader is missing the swatch in the Attribute Editor
|MAYA-35524||Bifröst: Loading a scene with user cache needs to go to frame 1 to read the cache|
|MAYA-36953||Add Help Table Entries to Bifröst option windows|
|MAYA-37253||Fixed a random crash when rendering mental ray swatch after new scene|
|MAYA-36023||Export Selected is not retaining unloaded reference information|
|MAYA-36578||gzipped files incorrectly get renamed upon resaving existing scenes|
|MAYA-34909||Fixed a crash when deleting a group of nodes|
|MAYA-21070||mental ray IBL Emit Light is much darker in IPR versus Render Current Frame (fixed on Mac and Linux only)|
|MAYA-34280||XGen: Cannot Render Dense Hair with mental ray
|MAYA-35098||mila: reordering layers with bump or weight connection is broken (fixed on Mac and Linux only)|
|MAYA-35306||mental ray ptex shader: additional parameters for hair rendering are ignored (fixed on Mac and Linux only)|
|MAYA-35749||mental ray builtin_object_light missing from 2015 release (fixed on Mac and Linux only)|
|MAYA-36068||Some mental ray shader nodes saved in .mb files are not compatible between 2014 and 2015 (fixed on Mac and Linux only)|
|MAYA-24165||Fixed a crash with (polyengine - TvertexEdgeIterator - next)|
|MAYA-32504||Performance improvements for setting component creasing values on large meshes|
|MAYA-30867||In Viewport 2.0, default or scene lighting
is applied to the shader during weight painting instead
of flat shading like the standard viewport
|MAYA-30877||Joint drawing in Viewport 2.0 is slower
than it was in Maya 2014 or in the Legacy Default
|MAYA-34403||Viewport 2.0 shows incorrect active trim edges on NURBS with trimmed islands|
|MAYA-34870||Noise shader fails on Mac OS X in Viewport 2.0
|MAYA-35711||Viewport 2.0 Settings UI doesn't reset on File > New: appears out of sync|
|MAYA-36035||Viewport 2.0: Alpha doesn't work in many TIFF files on Mac OS X|
|MAYA-36607||Depth Peeling only: Particle sprite and
transparent geometry disappear in Viewport 2.0
|MAYA-36827||Fixed a joint local axis issue|
|MAYA-36980||Fixed a crash when zooming in/out the camera after importing the nParticle example|
|MAYA-34628||Using the Python API function maya.api.OpenMaya.MFnComponentListData.length() crashes maya|
|MAYA-36024||mayapy crashes on Mac 10.9 with interactive input in the prompt|
|MAYA-35251||HUD buttons no longer working in Maya 2014/2015|
|MAYA-32377||XGen: Tube Groom is slow|
|MAYA-35343||XGen: Object Shadow by directional lights disappear when adding description|
|MAYA-36904||XGen: mental ray is too slow where rendering patches with a lot hair and a lot of faces|
|MAYA-32190||Due to limitations in the viewport and some missing libraries, the viewport mesh shader will not resemble the mental ray 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.
is getting evaluated over and over during batch render when runup is
Workaround: Disable Runup.
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.
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||Bifröst: Interior Particle Density requires a hard set minimum limit of 1.|
|MAYA-33828||Keying Master Voxel Size disables scratch cache.|
still render even after disabling the display of particles and voxels
in the Bifröst Shape.
Workaround : Hide the Bifröst 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. You can increase the number for a more accurate representation of the simulation while respecting the limits of your graphics card.|
|MAYA-34338||Certain mesh colliders will crash Maya.|
|MAYA-34412||Self-intersecting attached mesh will fail to emit Bifröst particles.|
|Cache Representation - Baked Geometry|
will crash during Windows remote desktop session if you try and import
a gpu cache.
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 the second screen of a dual screen setup.
Under System preferences > Mission Control > [ ] Displays have Separate Spaces, disable the Displays Have Separate Spaces option. This will bring the Mac OS X workspace's behavior back to the way it was before 10.9.
|MAYA-20117||Install fails on a clean Windows 8
computer with a message about internet connection.
In the Windows command shell (cmd.exe), type gpedit.msc and press Enter.
This will open The Local Group Policy Editor.
Here, select Local Computer Policy > Computer Configuration > Administrative Templates > System.
Under the System category, find and double-click the policy setting: Specify settings for optional component installation and component repair.
In the settings window that appears, select Enabled, and under Options, select Contact Windows Update directly to download repair content instead of WSUS.
Download .NET 3.5 from the Microsoft website and install.
Maya should now install and not get hung at the .NET 3.5 step nor return an error indicating that there is 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.
|MAYA-19686||Scene Assembly nodes do not handle well file reference representations 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.
In the Maya Preferences window, Display category, set the Max res. for swatches to a value larger than the estimated texture size.
|MAYA-21565||The currently active tool (move, rotate, scale, and so forth) 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 fail 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 the driver.|
|MAYA-22361||Character sets is not supported by Scene Assembly.|
|MAYA-22410||Deleting animation curves connected to a Scene Assembly reference may produce 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 legacy 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 the Hardware Renderer 2.0 Settings window), Multisampling Anti-aliasing 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||Occasionally, when your instances have
negative scale and you have other features such as
backface culling enabled, your lighting may appear incorrect. In
general, if you have negative scales and your instancing
appears incorrect, disable GPU instancing.
drivers for 1800M may crash Maya.
Workaround : Please update to a newer driver.
returns different results on the GUI on Windows.
1) Initialize the Maya environment within mayapy.
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.
listed (such as Ctrl+D) in a Maya
drop down menu does not update custom hotkey mappings until after Maya
has been restarted.
Workaround : Restart Maya
|MAYA-7804||The Ctrl+W hotkey cannot be assigned to Maya functions. It is reserved.|
|MAYA-9651||Non alphabetic shifted hotkeys do not work
with the Control modifier.
Workaround : Assign a different key
|MAYA-23390||If you delete a grooming XGen description and then undo, grooming splines will no longer be visible.|
|MAYA-23962||XGen is not compatible with merged meshes.|
Clumping preview refresh issue
If the preview appears inaccurate after altering clump maps, press preview again.
|MAYA-35663||XGen: Can't use Motion Blur with Mental Ray 126.96.36.199.|
Return to Top