The latest Service Pack from Autodesk for Autodesk® 3ds Max® 2010 and Autodesk®  3ds Max®  Design 2010 software includes nearly 30 fixes for issues with undo, performance, responsiveness, viewports, material workflow, and mental ray® software. Specific areas addressed are Biped, Bitmap Pager, Bitmap Proxies, Containers, Edit Poly, Interoperability, Licensing, Materials, mental ray, Particle Flow, Performance, Photometric Lights, ProOptimizer, Render To Texture (RTT), Rendering, UVW Unwrap, and Viewports.

Autodesk 3ds Max 2010 SP1

http://usa.autodesk.com/adsk/servlet/ps/dl/item?siteID=123112&id=13642460&linkID=9241178

• At times, if you canceled out of the Load Figure File dialog and clicked Undo, 3ds Max/3ds Max Design could become unstable. This is resolved.

• Some scenes rendered slowly because of the Bitmap Pager. The option to disable the Bitmap Pager functionality is now available in the Bitmap Proxies global settings dialog.

• In some circumstances the Bitmap Proxies code could be accessed before it had been properly initialized when launching the program. This would produce a program error. This has been fixed.

• When setting an In-Place Edit rule via MAXScript, an Access Content property was not being set. This has now been corrected.

• When applying the Shell Modifier to an object with deleted faces, 3ds Max/3ds Max Design presented the following error: “Object ‹object name› has a mesh with invalid texture vertex indices - can't render.” This issue has been corrected.

• The startup error encountered when running 3ds Max/3ds Max Design via Remote Desktop (RDP) has been corrected with D3D initialization.
• When launching 3ds Max/3ds Max Design, an error could occur if the required .NET components were not installed. All .NET required components are now verified during startup.
• When launching the 32-bit version of 3ds Max/3ds Max Design, an error could occur when the application attempted to interact with the Application Frame before it was properly initialized. This has been corrected by initializing the Application Frame before this interaction occurs.
• Previously, starting 3ds Max/3ds Max Design after changing the Windows Regional Settings caused the software to crash. This has been resolved.

• The internal Microsoft^® Windows^® messaging system in InfoCenter could make 3ds Max/3ds Max Design unresponsive during CPU-intensive tasks. 3ds Max/3ds Max Design is now more responsive during CPU-intensive tasks.

• Autodesk^® Revit^® nodes identified by metadata strings that did not begin with “Revit” were not being recognized. This was resolved so that all metadata strings that include "Revit" are recognized.

• When a license on a network server was in use the license server would not release the license if the machine using the license went idle. The license server now releases an idle license back to the license server. This TIMEOUT value is user definable in the LMtools license manager. See the LMtools documentation for details on setting this value.

• In custom Material Libraries that contain bitmaps, the bitmaps would not load properly between sessions. Custom Material Libraries from MAT and MAX files now load properly.

• When using 16-bit gray-scale Adobe^® Photoshop^® (PSD) files, 3ds Max/3ds Max Design would not work when using drag and drop to assign the PSD file. This error has been corrected.

• Materials would not display correctly when assigning a material in a Multi/Sub-Object material on any model that contained three or more material IDs. Only the first and second material ID would display in the viewport. All the IDs now display properly in the viewport.

• The Anisotropic Specular highlight in the Arch & Design material displayed in a different position in the viewport than it did when rendered. The highlight now displays correctly in both.

• When using shared nodes in mental mill^® and loading the resulting XMLS file into the DirectX Shader, the resulting render would not render all aspects of the material, for example Specular Highlights. Shared nodes are now properly supported.

• When using root nodes connecting to Phenomena in mental mill, the output did not support multiple outputs for mental ray. Multiple outputs are now supported, such as when using Math_color_abs.

• When using the Iterative rendering optimization, render elements were saved. Render elements should not have been output when using the Iterative feature.

• When using Final Gather (FG) Interpolation mode with the Arch & Design and Double-Sided materials, some faces would render black on the flipped side. They will now render correctly. This did not occur when using FG in Brute Force mode.

• Using double-sided materials with Multi/Sub-Object Materials could result in the process hanging. This no longer occurs.

• If the Particle View window was open when closing 3ds Max/3ds Max Design, the executable was not always ended properly and would be listed in the Task Manager. This is fixed.

• When creating keys with Set Key and moving keys in Track View on animation rigs, performance would be degraded. This has been fixed.

• Rendering complex scenes could cause the operating system to become unresponsive. This was due to the time interval that the software used to manage Windows messages. This interval has been increased so the operating system is more responsive in this situation.

• When using Photometric lights with IES files, a modified color intensity value would not be kept when you reloaded a Bitmap in the Material Editor > Bitmap Parameters rollout dialog. The Photometric light now retains the correct value when reloading Bitmaps.

• When running the 64-bit version of ProOptimizer, the optimization results were not computed as well as with the 32-bit version. The 64-bit version now optimizes correctly.

• When using a material with the Camera Map Per Pixel feature on, a Diffuse or Color map material RTT would produce an error when outputting. This is now supported.

• The Render Region Outline tool was not definable on a white image and it was not possible to view its location. This is now possible.

• When using Bitmaps in scenes, render times could increase; this degradation was more noticeable as the number of machine cores increased. This degradation in performance has been corrected.

• When opening the UVW Editor window, the window occasionally open minimized. This is now fixed.

• When viewports used Hardware Shading mode, if an object was mirrored along an axis it would turn solid black. This situation no longer occurs.