Thank you for downloading Autodesk® Maya LT™ 2016 Extension 2 + Service Pack 4.
This document describes known limitations and important information about Autodesk Maya LT. It is strongly recommended that you read this document before you install this release.
This section provides important installation information about this product:
For a complete list of new tools and improvements, as well as links to new and updated information, see What's New in Maya LT 2016 Extension 2 in the Maya LT Help.
Bug Number | Description |
---|---|
Animation | |
MAYA-62970 | Graph Editor with normalize mode has display issues |
MAYA-62722 | Crash in parallel evaluation mode |
MAYA-60667 | Performance issue with Editable Motion Trails and animation layers |
MAYA-55220 | Free image planes lose animated texture when duplicated with input graph |
MAYA-61467 | (Windows) Playblast temporary files are not removed |
FBX | |
MAYA-61812 | FBX plugin has lost support for DX11 shader |
MAYA-57630 | Game Exporter and FBX Export should not change the scene modified state when exporting |
MAYA-51652 | FBX Export does not support export of custom attributes driven by other custom attributes |
Modeling | |
MAYA-61637 | Create LOD Group is causing crash on exit |
MAYA-61023 | Adjusting UVs in UV Editor causes a crash |
Rendering | |
MAYA-61988 | Hypershade is very slow to open if a large hierarchy is selected when it's launched |
MAYA-60298 | Selecting shape node with same name in different group causes Hypershade error |
MAYA-58258 | Performance regression with Motion Blur |
MAYA-57577 | Crash when switching presets in the Hypershade |
MAYA-61465 | Crash when switching parent material in a docked Attribute Editor |
ShaderFX | |
MAYA-60954 | Renaming or editing a node which was exposed as a material input causes a crash |
Turtle | |
MAYA-61762 | Default baking values need to be adjusted to improve quality of result |
User Interface | |
MAYA-63506 | Deleting a bookmark in the Node Editor affects per component shading |
MAYA-62501 | Marking menu appears unexpectedly with a simple click |
MAYA-36493 | (Mac OS X) Click release mouse event has a lag when dragging from viewport on top of attribute |
Viewport | |
MAYA-61790 | Walk Tool doesn't work in Z-Up |
MAYA-55644 | Screen-space Ambient Occlusion + MSAA makes the grid visible through geometry |
MAYA-62760 | Motion Blur or DOF + MSAA makes the grid visible through geometry |
MAYA-62049 | Color management using OCIO slows down viewport performance |
MAYA-39908 | (Mac OS X) Drag selection makes viewport go black (Open Sub-D) |
Creating an LOD group using Edit > LOD (Level of Detail) > Generate LOD Meshes fails if any of the selected meshes is not the unique child of a top-level transform. If you have an existing lodGroup hierarchy, it fails if any mesh under the LOD_0 node is not the unique child of a transform whose parent is LOD_0.
Workaround: To generate lower resolution meshes from multiple meshes, each selected mesh must be the unique child of a top-level transform. This groups the meshes directly under LOD_0 in a flat hierarchy by making the parent of each mesh a direct child of LOD_0.
Similarly, to re-generate lower resolution meshes from an existing LOD hierarchy, each mesh must be the unique child of a parent transform, and that transform must be a direct child of LOD_0.
If you delete the history of a mesh (Alt + Shift + D), then freeze its transform (Modify > Freeze Transformations), generating lower resolution meshes with Edit > LOD (Level of Detail) > Generate LOD Meshes or can result in deformed lower resolution meshes.
Workarounds: 1. Reverse the order of the operations, freezing the transform before deleting the history. 2. Export the frozen mesh as an FBX file, then import it before applying Edit > LOD (Level of Detail) > Generate LOD Meshes.
Exporting to FBX with the Triangulate option on can corrupt the scene (trash the shading). This occurs if you delete history then export an object containing per-component shading.
Workarounds: 1. Save the scene before doing the FBX export, then re-open the scene (without saving again) after the export. 2. Avoid using the FBX Triangulate option, and triangulate use Mesh > Triangulate instead.
All release notes available for Maya LT 2016 at: http://www.autodesk.com/mayalt-releasenotes
Find learning resources for Maya LT at: http://www.autodesk.com/mayalt-learningpath
Find support and troubleshooting resources at: http://www.autodesk.com/products/maya-lt/support
For the latest list of certified hardware to run Maya LT, including graphics cards, refer to the Certified Hardware tool: http://www.autodesk.com/hardware
Find the Maya LT 2016 minimum system requirements at: http://www.autodesk.com/mayalt-systemreq-2016-enu
The first time you start Maya LT, the Customer Involvement Program dialog box appears. If you choose to participate in the Customer Involvement Program, Maya LT automatically sends Autodesk information about your system configuration, what features you use most, any problems that you encounter, and other information helpful to the future direction of the product. For further information, see http://www.autodesk.com/cip.
We are able to improve the stability of Maya LT largely because of the Customer Error Reports (CERs) that users of our products submit. We thank you for taking the time to fill out these reports and ask that you include as much information as possible about what actions you were performing at the time the error occurred. These details raise the value of the report immensely and are very much appreciated by the Autodesk Maya LT Engineering team.
For further information about CERs refer to http://www.autodesk.com/cer.
Autodesk, Backburner, FBX, Maya, Maya LT, MotionBuilder, Mudbox, Softimage, and 3ds Max are registered trademarks or trademarks of Autodesk, Inc., and/or its subsidiaries and/or affiliates in the USA and/or other countries. All other brand names, product names, or trademarks belong to their respective holders. Autodesk reserves the right to alter product and services offerings, and specifications and pricing at any time without notice, and is not responsible for typographical or graphical errors that may appear in this document.