Monday, September 29, 2008

Revit MEP 2009 64-bit Now Available!

YYYYEEEEESSSSS!!!! Looks like the native 64-bit versions of Revit are now rolling out the door at Autodesk. I just logged on my Autodesk Subscription site and and there it was listed under the new Product Downloads section on the homepage of the redesigned site (which I love by the way). Below is a direct link to the Subscription download page (you'll need to be logged in) for Revit MEP 2009 64-bit which looks to be the only one available at the moment but I'm sure the other flavors will follow shortly.

Looking for more details, read on...

Release Date: 2008-09-29
This version of Revit® MEP 2009 is a native 64-bit application to be used with 64-bit Operating Systems, such as Microsoft® Windows® XP Professional 64-bit or Microsoft® Windows Vista® 64-bit (Business, Home Premium, Ultimate editions). The 64-bit version of Revit MEP 2009 removes the 4 gig memory limitation found in 32-bit applications which enhances the software’s capability to handle large projects. It contains the functionality found in the 32-bit release of Revit MEP 2009, with the noted limitations found in the Known Issues document.

Known Issues
Revit MEP 2009 (64-bit only)

  • Revit® 64-bit products can access additional RAM in computers containing more than 4GB of memory. Due to the inherent application memory access limits of Revit 32-bit products, it will be possible for 64-bit Revit products to create models that 32-bit Revit products will be unable to open. If this situation is encountered, the problematic model must be divided into two or more models small enough to be opened in the more limited memory available to Revit 32-bit applications.
  • ODBC export is limited to those formats for which Microsoft has provided 64-bit drivers. At the time of this release, drivers to export to Microsoft Excel and Microsoft Access are unavailable for Microsoft Windows 64-bit operating systems.
  • The Autodesk DWF Printer is unavailable for the Revit platform products in 64-bit. DWF files may still be created with Revit’s DWF Publish option.

Revit MEP 2009 (32-bit and 64-bit)

Default Pipe Size Information

  • The first time you open a project that was created in a previous release, Revit MEP attempts to import pipe size information from the PipeSize.xml file used with the prior release. The imported information overwrites the integrated default pipe size information. If you want to preserve custom size information from a prior release, you must restore the PipeSize.xml file used with the project to its original path. There is no warning message if the PipeSize.xml cannot be found. If you save the project in this release of Revit MEP, without having imported the size information used with the prior release, the project will use the default size settings. For more information please refer to Revit MEP Help.

Control-Point Location on Homerun Arrows

  • The location of the control point that is used to grip and drag the arrow location of a homerun wire has moved from the tip of the arrow to the base of the arrow. This point location is also used to determine graphics for "automatic cleanup" that occurs when the homerun for one circuit is connected to, for example, a receptacle on a separate circuit. The end result is that the base of the arrow will be automatically located at the graphical boundary of the receptacle symbol, with the tip of the arrow extending into the receptacle (or whatever other device/equipment the homerun points to). To fix this problem, you can grip-edit and drag the control point on the arrow to the desired location.

Export to ODBC

  • When exporting to ODBC, family instances within the project that have more than one connector will only export information associated with one of the connectors. The other connectors will be ignored.

Heating and Cooling Loads Report

  • Results that are displayed in Heating and Cooling Loads reports may appear to be non-precise. For example, a cubic room that is 20ft x 20ft x20ft may display a volume of 8,000.01CF instead of 8000.00CF. This is due to rounding differences that are introduced during the conversion to metric units so that the calculations can be performed, and then back to imperial units for display in the report.
  • Space areas that are calculated and displayed in the Heating and Cooling Loads reports could be based on either the internal faces or external faces of the wall. There is no way for the user to control this. By default, the first attempt is to use the inner faces of the walls. However, due to current technical limitations, there are cases where it may not be possible to use the inner surfaces of the walls, in which case the area calculations will be based on the location of the outer wall surfaces.
  • On Vista 64-bit operating system, IES version VE585 cannot be launched from within Revit MEP 64-bit.

Design Phases in the MEP Workflow

  • Using design phases in the Revit MEP workflow may result in unexpected behavior. For example, if 3 air terminals with a flow of 500 CFM each are created in one duct run, then the flow reported on an upstream pipe would be 1500CFM (as expected). However, if one of those terminals is demolished in a different phase, then that same upstream duct will still report 1500CFM – regardless of which phase you are currently viewing. This is because it is not possible for a single duct run to be able to store multiple flow values simultaneously. Therefore, the systems values will always be representative of the all equipment/devices attached to the system. This similar type problem applies to all mechanical and electrical systems. Any system that is created has no way to keep track of information for multiple phases. This problem with phasing may also be manifested in ways other than what is specifically described above.
  • When running Heating and Cooling Loads calculations, only the spaces that are on the current energy analysis phase will be included in the calculations. All spaces must be on the same phase in order to be included in the calculations.


  • Revit MEP 2009 software contains a new rendering engine that makes major changes to the previous workflow. See the Revit MEP 2009 Feature Summary, What’s New in This Release, and Help documentation for information and instructions.
  • Currently, Decal bump image maps fail to import at the correct scale for cut-outs.
  • The Plant Height parameter may not scale the nested component correctly (RPC Content).
  • When rendering an uncropped 3D view, geometry may appear shifted. Workaround: turn on crop region for the view.
  • For lights, the "Emit from Line Length" parameter may not work properly unless the user has Soft Shadows enabled.
  • Non-English builds of Revit currently display RPC ID’s instead of names for downloaded RPC content.
  • Currently, using more that 5 or so decals in a view can seriously increase render time. Also, using 18 or more in a view can crash Revit.

The Front orientation in ViewCube in a published DWF

  • Currently, if the Front orientation in ViewCube™software is changed from its default setting in Revit MEP, the change will not be reflected on the ViewCube in a published DWF™.

Fill Patterns

  • Fill Patterns can now be applied to most surfaces (including warped planes), however:
    - Only patterns on planar surfaces can currently be moved or rotated.
    - Some complex surfaces may exhibit undesirable anomalies (such as areas of missing pattern).
  • Currently, detail components do not support aligning fill patterns to the element.

Dimension Text Overrides

  • For a multi-segment dimension string in which one of the dimensions had a dimension text override, adding a new segment to the string causes the override to disappear.

Dimension Type Text Sizes

  • Dimension Types lose their previous Text Size changes when a Duplicate Type is created.

Mass Floors in Groups

  • Currently, when binding a link containing Mass Floors, they will disappear because they cannot be placed into groups.

Far Clip Parameter and Linked Files

  • While Linked files can now be displayed By Linked View in Sections, Elevations, and 3D views, the Far Clipping Parameter in Section and Elevation views will always display per the Host view’s settings and NOT by the Linked View’s settings – even when the Link is set to display By Linked View.

Slab Shape Edit

  • After clicking Pick Supports for a sloped slab, changing the Curved Edge Condition to "Project to Side" causes the shape edit to fail for some curved edges. A temporary workaround is to delete the offending curve.

Room Bounding Instance Parameters

  • Currently, not all room bounding elements (e.g. in-place ceilings and in-place floors) have an on/off Room Bounding parameter.

Foundation Extensions

  • Openings do not participate in the Foundation Extensions feature, only Inserts.

Large DWG Imports

  • DWG™imports with entities further than two miles apart (after scaling) may cause accuracy issues. Very large DWG imports should be subdivided into smaller files.
  • DWG imports with coordinates (before scaling) longer than ten digits may be truncated to zero and become corrupted.

Concrete End Joins

  • New behavior is limited to Concrete Beams with the following properties:
    - Rectangular Sections with Cross Sectional Rotation that equal 0, 90, 180, and 270 degrees.
    - Trapezoidal, T-shaped, and L-Shaped Sections with Cross Sectional Rotation that equal 0 degrees.
  • Sections that do not qualify within these properties will exhibit old behavior.
  • Shape Handles are not available for elements participating with new behavior.
  • Type parameter changes will not automatically update concrete join geometry.

Automatic Join Geometry

  • Hierarchal joining rules between element categories cannot be changed, e.g. Slabs always cut Columns when using Join Geometry.
  • Automatic Join Geometry does not occur between Wall and Slab categories.
  • It is not possible to disable automatic Join Geometry, but joins can be manually un-joined.
  • Joined geometry may impact performance.

Hidden Lines

  • On-screen display of hidden lines may not match vector output (e.g. Print, Export) in some cases.
  • Some edges of Wall ends will not show as hidden.
  • All Edges of slab edge will show as hidden in a Plan view if obstructed by the Slab.

Beam Extension and Mitering at end Join

  • Mitering non-Concrete Beams is limited to 2 Beams of the same type within the same plane.
  • Lines within the Beam family (e.g. hidden lines) will not Trim/Extend to the miter plane.
  • Beam shape handles do not participate in extensions.
  • Edit Beam Join editor is not available when a concrete beam is participating in the end join.
  • Beams that have been mitered at any time during their life will be cut by the Cut Plane in Plan Views using Medium/Fine Detail Level.

Worksharing Monitor

  • The Worksharing Monitor tool may behave incorrectly if the Local (or Central) File names contain dots other than the dot before the .rvt extension.

DWF Markups

  • Markups made in Design Review with the Freehand Markup tool do not import into Revit with properties.


  • Microsoft Office 2007 dictionaries for English, German and Spanish are currently incompatible with Revit. You can still use the provided Autodesk dictionaries or install an earlier version of Microsoft Office to use the older Microsoft dictionaries.

Release Notes
Welcome to the 64‐bit edition of Revit® 2009 platform products. This release takes advantage of the additional memory available to applications in a 64‐bit operating system environment. 32‐bit Microsoft® Windows® operating systems, when properly configured, are limited to providing between 3GB and 4GB of memory to applications. From a software standpoint, there is no practical technical limit to the amount of memory available to compatible applications under 64‐bit Microsoft Windows operating systems, although the hardware platform may impose some technical restrictions on the amount of RAM that may be installed in a given workstation.

Hardware Requirements and Recommendations for the Revit Platform

System Requirements

Operating System: Microsoft® Windows® XP Professional x64 Edition or Microsoft Windows Vista® 64 bit (Business, Home Premium, Ultimate)

Browser: Microsoft® Internet Explorer® 6.0 SP1 (or later)

CPU type: Intel® Pentium® 4 1.4 GHz or equivalent AMD processor

Memory: 3 GB RAM

Video Display: 1280 x 1024 monitor and display adapter capable of 24-bit color

Hard Disk: 3 GB free disk space

Pointing Device: Microsoft-mouse compliant

Media: Download

Connectivity: Internet connection for license registration

System Recommendations

Operating system: Microsoft Windows XP Professional x64 Edition

Browser: Microsoft Internet Explorer 6.0 SP1 (or later)

CPU type: Intel Core® 2 Duo 2.40GHz or equivalent AMD processor

Memory: 8 GB RAM (or more)

Video Display: Dedicated video card with hardware support for OpenGL specification 1.3 or later, and support for Microsoft® DirectX® 9 or later.

Hard Disk: 5 GB free disk space

Pointing Device: Two-button mouse with scroll wheel

Revit 2009 platform 64‐bit product performance is expected to be similar to an identical Revit model edited with Revit 2009 platform 32‐bit products. However, due to the potential for the Revit platform to access greater quantities of memory made available by the Windows operating system running with more installed RAM, the Revit platform may exhibit increased stability.

Model Size
With hardware configured in the manner listed in the System Recommendations section, it may be possible to edit Revit models of greater size than is practical within the 32‐bit version of the Revit 2009 platform. It should be noted that Revit models whose memory requirements exceed the RAM available in a 32‐bit operating environment may not open in the 32‐bit version of Revit 2009 platform.

Non‐Autodesk external commands and applications designed to access the Revit platform may not be compatible with Revit 2009 64‐bit platform.

As of this Revit release, Microsoft has not made available ODBC (Open Database Connectivity) drivers for its 64‐bit operating systems. Consequently, the Revit 64‐bit platform cannot export a Microsoft® Excel®‐ or Microsoft Access®‐compatible ODBC file.

No comments: