The following defects have been fixed in AutoCAD MEP 2009 Update 2
- Duct Sizing should more accurately produce the correct size in metric units.
- The Load property on Devices will now schedule the loads of each phase instead of only phase 1.
- Object Snaps on scaled Devices will now behave more consistently.
- Devices which contain annotation will produce an image in the Property Palette which matches the image in the Select a Style dialog
- Using grips to modify a Pipe layout during a Reference Edit session no longer causes disconnections in the pipe layout.
- AutoLayout should not produce overlapping pipe segments when connection two existing pipes to each other.
- Multi-view Part tools will respect Part Size Name when executed.
- Invalid Enum Map String message is no longer encountered when using the MvPartModify command on a multi-view part which does not exist in the active catalog.
The following defects were fixed with AutoCAD MEP 2009 Update 1 and are also fixed in AutoCAD MEP 2009 Update 2:
- Unable to Write Check Permissions error occurs when copy and paste parts into the same catalog.
- Duct sizing does not always provide the expected size when using Metric units
- Power Totals tool does not always state the correct load.
- Pipe segments will be offset from each other when using justification which is not Center/Center.
- Insulation will not be applied to pipe fittings when using the match properties.
- In some instances pipe object are not visible until a regenerate is performed.
- Invalid Enum Map String error when using MvPartModify on a multi-view part created via MvPartConvert command.
- AutoCAD warning message when saving an External Reference.
General Updates to AutoCAD Architecture
The following defects have been fixed in AutoCAD Architecture 2009 Update 2
- Multi-view blocks inserted from user created tools did not scale properly when used in subsequent drawings or sessions.
- Projects created from project templates did not inherit the correct sheet storage location property.
- Projects created from project templates did not inherit sheet subset storage location information.
- The application would occasionally crash when creating project details.
- Surfaces belonging to different walls would export with the same CadObjectId.
- Spaces, railings, footings, and column objects might be exported with an incorrect object type identifier in some localized releases.
- Half spaces would be imported as large modifiers.
- Slab fascias and soffits would not properly export in some localized releases.
- Level and elevation info would be created in reverse order when an IFC file was imported into a project.
- Material sets applied to walls of type "Shared" would not export correctly.
- The schedule quantity column evaluated property values without first applying the property data format.
Wall objects and opening endcaps
- Certain endcap configurations might cause walls to disappear in 3d isometric views.
- Some walls might not draw completely at a locked z elevation.
- Using "Add selected" for anchored doors, openings, and windows could cause an application crash in some circumstances.
- Walls might fail to clean up properly across xrefs if the host drawing used different drawing units than the xref.
- Tooltips would appear for AutoCAD entities even when ROLLOVERTIPS was set to zero.
- Saving a drawing to the 2004 file format would take an exccessive amount of time.
- Export to AutoCAD might cause an application crash in some circumstances.
The following defects were fixed with AutoCAD Architecture 2009 Update 2:
- The application might crash when cutting or refreshing sections or elevations containing certain structural members.
- For localized versions of AutoCAD Architecture, callouts and labels would occasionally fail to resolve when dropping views.
- The application might crash when viewing the external references of a project drawing that was resaved as a different project drawing type.
- It was not possible to drag a project entity from one file to another when hardware acceleration was enabled, if the host drawing did not use the 2d wireframe visual style.
- The application might crash when plotting immediately after cancelling a previous plot job.
- Fillet radii would not be imported reliably for certain parameteric profiles.
- Parametric profiles without voids would not be imported reliably.
- Spaces with clipping and holes would not import reliably.
- Wall styles would not be reliably converted and mapped on import.
- Curtain walls might not be import properly on localized versions of AutoCAD Architecture.
- gbXMLspan would export a value 1000 times too large for AirChangesPerHour in metric drawings.
- The application would occasionally crash on shutdown.
- The face of a wall might not draw correctly in isometric view for certain endcap configurations.
- Autodesk Civil 3D users could end up with a style referencing a non-existent hatch.
- Memory would not be released to Windows when closing a drawing.
The following defects have also been fixed:
3D Navigation Tools
- When you use the ViewCube in some drawings, AutoCAD freezes.
- If you create a wipeout object through .NET API, a fatal error may occur.
- The scale of annotative text changes when you use LISP entmod() to change the properties of the annotative text.
- When a drawing contains xrefs, the -ATTEDIT command fails.
- In the File Navigation dialog box, when you use the Add a Buzzsaw location shortcut option, AutoCAD crashes.
- When you copy and paste a dynamic block, associative hatches do not work.
- After you redefine a block definition, associative hatches in dynamic blocks display incorrectly.
- When you open a drawing, a polyline in a block may have a very large width.
- After you open a drawing, some dynamic blocks lose their dynamic properties.
- Data Extraction cannot finish operations in some cases.
- The Data Extraction Combine Record Mode > Sum values option does not work correctly.
- When you import some DGN files, AutoCAD crashes.
- If alternate units is on and you edit dimension text, the alternate units text is duplicated.
Export a Layout to Model Space
- If .NET 3.5 Service Pack 1 is installed and you use the EXPORTLAYOUT command on some layouts, AutoCAD may stop responding.
External Reference ESW
- The FIND command performs slowly when you search for text.
- Rollover highlighting does not go away.
- When you bind a drawing with an xref that contains annotative hatches, AutoCAD crashes.
- When you use the HIDE command with a drawing that contains text, some objects may not be hidden.
- When you attach a corrupted raster image to a drawing, AutoCAD crashes.
- When you zoom to a locked viewport, the Layer palette updates
- When you attempt to switch layouts in drawings, an Out of Memory crash may occur.
- When you import a 3DS file with texture, AutoCAD may crash.
- Some menu macros do not work.
- Mleader custom arrowheads are not brought over to the drawing from the Tool palette.
Multiline Text (mtext)
- When you edit mtext in a viewport, it may be duplicated in other viewports.
- Osnaps on polylines and mesh objects do not work correctly.
- When you plot upside-down, an OLE object does not plot correctly.
- A drawing that contains hatches and gradients may plot slowly.
- When plot area is set to View, AutoCAD LT may crash.
- When you attempt to publish multiple sheets with PUBLISHCOLLATE=1, only the first sheet of the set is plotted.
- When you edit multiple mtext objects through the Quick Properties palette, AutoCAD crashes.
- When you render some drawings, AutoCAD runs out of memory.
- If the ribbon is displayed and you select portions of a mtext object that contains multiple formats, the mtext object becomes distorted.
- When you select objects in groups, AutoCAD may crash.
- When you edit text with space before or after the text within a table cell, AutoCAD crashes.
- When you move text to a new position within a drawing, it disappears.
- When you attempt to edit the properties of multiple Tool Palette tools, an Out of Memory crash may occur.
Known Issues with This Update
- After installing this update you may receive a "Error Code: 3010" message incorrectly claiming that the update failed. You can verify this by viewing installed updates through the Windows control panel.
- After you apply this update, you may experience the following ribbon customization-related problems:
An Incorrect or Missing Ribbon Tab
- Known Issue: When you display a ribbon tab from a partial or Enterprise CUI file, on the ribbon, the ribbon tab displays incorrectly or is missing.
- Workaround: To correctly display a ribbon tab, recreate the workspace used to display the ribbon tab from scratch. Do not duplicate or attempt to update the workspace. Once you create a new workspace, set the workspace current. The ribbon tab should display correctly.
- For a partial CUI file, before you add a ribbon tab to a workspace, use the Customize User Interface (CUI) Editor to change the customization group name of the file. The customization group name is represented by the uppermost node of the tree in the Customization In pane.
A Blank Image for a Command
- Known Issue: On a ribbon panel, the image associated with a command defined in the Command List pane displays as a blank icon.
- Workaround: To recreate a ribbon command item on a ribbon panel, delete it. Then, from the Command List pane, add the command to the ribbon panel.