Autodesk Maya 2016 With Mentalray Download Free

Posted on  by

Thank you for downloading Autodesk ® Maya ® 2016 Service Pack 5.

Install Autodesk Maya 2016 and Mentalray on Ubuntu 16.04 - maya2016mentalray.sh. The Maya installation directory contains an installer for mental ray renderer. This version of mental ray is used only for local rendering on the same computer as Maya. To run mental ray locally. Install mental ray renderer, using the installer. In Maya, select Windows Settings/Preferences Plug-in Manager. The Maya installation directory contains an installer for mental ray renderer. This version of mental ray is used only for local rendering on the same computer as Maya. To run mental ray locally. Install mental ray renderer, using the installer. In Maya, select Windows Settings/Preferences Plug-in Manager.

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

To view all Maya release notes, see www.autodesk.com/maya-release-notes.

Contents

What's New

What's Fixed

Mental Ray Download 3d Max

Limitations and notes

Additional Resources

What's New

New StingrayPBS features

In the StingrayPBS node Attribute Editor, the Parent Material drop-down list has been renamed to Preset Material.

Mental Ray Tutorial

The In Engine Material attribute has been renamed to Parent Material.

In addition, the Engine Resource attribute has been added that allows you to assign a material name for your StingrayPBS. When you send your assets to the Stingray via File > Send to Stingray, this name will be used for your material in your Stingray project.

Mental

Return to Top

What's Fixed

The following list contains bug numbers and corresponding descriptions for issues fixed in this release.

Bug Number Description
Animation
MAYA-42895 Dragging Trax track past last track disables animation
MAYA-45414 Evaluation HUD constantly echoes in the Script Editor
MAYA-51652 Maya FBX Export does not support export of custom attributes driven by other custom attributes
MAYA-52688 Expression node is not evaluated for mental ray nodes
MAYA-53520 Maya crashes when using the dgtimer command with Evaluation Manager (EM)-based evaluation
MAYA-53889 SoftMod does not update when animated
MAYA-54723 Channel Box doesn't refresh when changing the value using middle mouse drag unless asset is selected
MAYA-54788 Maya crashes with maya.standalone skinning
MAYA-55220 Free image planes lose animated texture when duplicated with input graph
MAYA-55540 Cannot re-implement schedulingType() for deformers
MAYA-58612 Maya reverts to serial EM evaluation when animating camera aim
MAYA-58664 Assets break Channel Box multi-edits
MAYA-59718 Graph Editor normalize view has glitches
MAYA-60667 Editable motion trails can be slow when used with animation layers
MAYA-60668 Maya can become slow after deletion of animation layers
MAYA-60971 EM manipulation stops working in some cases
MAYA-61007 Maya crashes when playing or scrubbing animation
MAYA-61828 Mesh problems in Viewport 2.0 with trax clip duplication and split
MAYA-62340 Maya crashes when evaluating scene in parallel
MAYA-62469 Maya crashes on some scenes with HIK and Editable Motion Trails
MAYA-62966 Curves not being normalized in the Graph Editor when using the middle mouse button
MAYA-63605 EM manipulation becomes disabled in the Graph Editor
Color Management
MAYA-62049 Color management using OCIO slows down Viewport 2.0 performance
General
MAYA-52656 (Windows and Linux) Temporary files written when creating Playblast are not deleted
Interoperability
MAYA-55165 Playblasts to Quicktime format cannot save to temp directory and fails
MAYA-61812 FBX plug-in lost support for DX11 shader
MAYA-62220 GameExporter: Locked Translation or Rotation will prevent move to origin operation from completing
mental ray
MAYA-40310 Incorrect motion vector pass with scanline disabled
MAYA-60061 Very long mental ray renders for a specific scene
MAYA-61062 mental ray standalone creates huge log files when used on Red Hat Enterprise Linux
MAYA-62630 Maya now uses mental ray version 3.13.1.10
Modeling
MAYA-45686 Falloff result appears incorrect in perspective view when size units is set to screen pixels
MAYA-61023 Adjusting UVs in UV Editor causes a crash
MAYA-61391 When 'autoFit' is enabled, Bevel does not apply curvature conform on all edges as expected
Rendering
MAYA-57577 Switching presets in the StingrayPBS node in the Hypershade crashes Maya
MAYA-58258 Performance regression with motion blur
MAYA-58476 Cannot start Maya from remote shell on Linux
MAYA-58925 .tx and .tex image files not showing in image file browser
MAYA-60298 Selecting shape node with same name in a different group causes Hypershade error
MAYA-60973 Hypershade is very slow to open if a large hierarchy is selected when it is launched, and lags when selecting big groups of geometry
Scene Assembly
MAYA-21981 DAG-path not included in edit strings when needed for uniqueness
MAYA-60644 Material connections are not maintained when API calls are made to duplicate the assembly node
ShaderFX
MAYA-60954 Renaming or editing a node that was exposed as a material input causes a crash
MAYA-61429 StingrayPBS material crash when switching parent material in a docked Attribute Editor
MAYA-61583 StingrayPBS material Make Unique button doesn't refresh Attribute Editor
Turtle
MAYA-61762 Default values need to be adjusted to improve quality of result
User Interface
MAYA-36493 (Mac OS X) Click release mouse event has a lag when dragging from the viewport over top of Attribute Editor
MAYA-54752 Maya overrides the standard Qt tree control drawing
MAYA-58393 Deleting a bookmark in the Node Editor is wiping out per component shading (groupID nodes)
MAYA-62308 Marking menu can sometimes become stuck and continually appears upon a simple mouse click
Viewport
MAYA-48439 Walk Tool doesn't work in Z-Up world coordinate system
MAYA-55644 Screen-space ambient occlusion with multisample anti-aliasing makes the grid visible through geometry in Viewport 2.0
MAYA-59468 Memory leak with nucleus evaluations when display smooth mesh mode is enabled
MAYA-60098 Viewport 2.0 displays EXR images with a lineOrder of decreasing-y 'upside down'
MAYA-61651 HUD operations are no longer (incorrectly) affected by scene operation filters for MRenderOverrides
MAYA-62016 DG mode performance: shading groups with no material always evaluate their inputs
MAYA-62225 Fixed common viewport crash #1 reported via online crash report system
MAYA-62258 Re-loading reference crashes Viewport 2.0
MAYA-62626 Previously, pressing 3 to display a smooth mesh when using the OpenSubdiv Catmull-Clark subdivision method may cause Viewport 2.0 to turn black on the Mac OS X platform. This issue has now been fixed.
MAYA-62760 Motion Blur or depth of field with multisample anti-aliasing makes the grid visible through geometry
MAYA-62871 Fixed common viewport crash #2 reported via online crash report system
MAYA-63539 Broken swatch of plug-in shader such as hwPhongShader
MAYA-63686 The Grease Pencil tool now works correctly in wireframe mode. See also the Limitations and notes section below.
XGen
MAYA-61476 Clumping create/modify maps does not save expressions
MAYA-62532 Second Clump Control Map setup settings are lost after first setup

Return to Top

Limitations and notes

The following section describes limitations and workarounds (where applicable) about this release.

Bug Number Description
Animation
MAYA-59834

The Maya Developer Kit splatDeformer and sseDeformer plug-ins have been updated to serve as better examples of how to accelerate plug-ins so they work with the new Evaluation Manager. Both plug-ins now work correctly in serial and parallel evaluation modes. The splatDeformer plug-in now use TBB instead of OpenMP.

The Developer Kit is available online at Autodesk Exchange at https://apps.exchange.autodesk.com/MAYA/en/Home/Index.

API
MAYA-55943

In Maya 2016, setDependentsDirty was not called for MPxLocatorNode, MPxDeformerNode and MPxComponentShape on the Mac OS X platform. The cause of the problem was that on Mac OS X, the API version was not set as a global symbol in the dynamic library (.bundle).

This problem has now been addressed for Maya 2016 Service Pack 5.

Download the latest version of the Maya Developer Kit (version 2016.3), then recompile your plug-ins against the updated version of the buildconfig file, or use the updated versions of the Xcode project file.

If you have custom plug-ins with your own build environment, you can modify the buildconfig file or Xcode project files as follows:

Update the devkit buildconfig file in order to promote the symbol to global scope:

  1. Edit devkit/plug-ins/buildconfig.

    Replace:

    with

  2. Rebuild the plug-in.

For Xcode projects, you must add -Wl,-exported_symbol,_MApiVersion to Other Linker Flags in the compile settings and rebuild the plug-in.

The Developer Kit is available online at Autodesk Exchange at https://apps.exchange.autodesk.com/MAYA/en/Home/Index.

FBX
MAYA-61009 Exporting to FBX with the FBX triangulate option may corrupt the main Maya scene (shading assignments are lost). This occurs if the export was performed on an object containing per-component shading and has had Delete History performed on it.

Workaround 1: Save the scene before performing the FBX export, and re-open the scene (without resaving) after the export.

Workaround 2: Avoid using the FBX triangulate option, and triangulate using the Mesh > Triangulate in Maya instead.

Viewport
MAYA-32937

MGeometryExtractor now supports the following:

  • Multiple UV map sets for texture co-ordinates in plug-in shaders
  • Named map sets for Tangent and Binormal co-ordinates in plug-in shaders

Set the environment variable MAYA_API_NAMED_TANGENT = 1 to take advantage of this fix.

MAYA-63686

The performance improvement provided in Maya 2016 Service Pack 4, where shading nodes are not evaluated for viewports in wireframe and bounding box shading mode, has been disabled by default.

To re-enable this behavior, set the environment variable MAYA_VP2_DEFER_SHADER_UPDATE_UNTIL_NEEDED to any value. However, the grease pencil tool will not work in wireframe mode as a result.

The performance improvement provided for individual objects (for example, shading nodes are not evaluated for objects that are hidden or in template mode) is still enabled and does not require you to set an environment variable.

Return to Top

Additional Resources

For complete instructions about uninstalling and installing this product see Maya Installation Help.

To learn about new features in this release, see the Maya Help.

For complete documentation and resources, see www.autodesk.com/maya-docs.

For the list of hardware that is certified to run Maya, including graphics cards, see Autodesk Certified Hardware.

For more Maya Support, see www.autodesk.com/maya-support.

Customer Involvement Program

The first time you start Maya, the Customer Involvement Program (CIP) dialog box appears. If you choose to participate in the CIP, Maya 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.

Customer Error Reports

We are able to improve the stability of Maya largely because of the Customer Error Reports (CER) submitted by users of our products. 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 Engineering team.

For further information about CERs, see http://www.autodesk.com/cer.

Autodesk, the Autodesk logo, Backburner, FBX, HumanIK, 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.

© 2015 Autodesk, Inc. All rights reserved.

Return to Top

This compound automates the process of creating an efficient MPM granular simulation setup. It computes the intersection of an animated object with a piece of terrain and builds three useful pieces of geometries which can be used for the MPM simulation: (1) A 'source' geometry for sourcing the MPM particles only where the animated object intersects with the terrain geo, (2) A 'container' geometry used as a collision object in the MPM sim, which holds the granular particles in place (lest they fall down due to gravity), and (3) A 'carved_terrain' geometry which simply returns the terrain mesh, post-carving. It can be useful to scatter points around the granular sim, for rendering purposes. Note that the terrain needs to be of planar topology, e.g. one-sided - not like box. The terrain and the animated object need to be supplied in the form of file-caches (Alembic .abc or .bob). A frame-range must also be specified so that the carver knows which frames to consider for the intersection between the animated object and the terrain. NOTE this compound was recently updated to work with Bifrost 2.1.0.0 or later.