Revit MEP

Revit MEP
Showing posts with label Support. Show all posts
Showing posts with label Support. Show all posts

Monday, November 21, 2011

Using Revit as a Team. Use Same Builds.

When using Revit on a project, make sure everyone on the team is using not only the same version, (2011, 2012, etc), but the same build number as well.  The build number can be found by clicking on the question mark pull down in the upper right corner, and click the About button….

From there, you’ll see the splash screen of the version, and the build.  The first 4 numbers in the year the build was released, (2010) The next 2 are the month of the release, (09-September), the next 2 are the day of the release, (03-third).  The last four are the actual build number 2115, and the service pack number is new to the newer versions.  Might not be shown for earlier versions.

 


I’ve seen fatal errors in Revit when teams are using the same version, but different build numbers, and users are syncing their builds local file to the central file, and the central file is receiving updates from multiple builds, when there have been some changes to the software code, and there is a discrepancy  between two items, one new version, one old version, and Revit doesn’t know what to do. 

In order to make sure everyone is using the same build, everyone should be using the latest build.  For 2011, its build 20100903_2115 Web Update 2 Service Pack.  For 2012, it’s build 20110916_2132 Update Release 2.

Monday, October 03, 2011

Revit MEP 2012 Update 2 – September 2011

In case you are too lazy to search to the Autodesk site... I've posted it here

Update 2 is not a full install; rather it is using service pack technology similar to AutoCAD®- based products. Update 1 is built into Update 2, so you don't need to worry about installing the first one before installing the second one.
Improvements made in Update 2 build (20110916_2132):

Autodesk® Revit® MEP 2012 Enhancements
  • Improves stability when routing ducts which utilize an elbow or takeoff to complete the run.
  • Improves stability when dragging a Panel Schedule into a sheet.
  • Corrects the classification of embedded windows within a curtain wall contained within a linked file which is used as the boundary to create spaces.
  • Improves the regeneration time of Ducts after applying a Visibility/Graphics Override.
  • Improves stability when creating a new zone in the zone editor and specifying an already existing name in the properties palette.
  • Improves performance when adding an air terminal to a system.
  • Retains System Type when coping elements from one project to another.
  • Retains pipe and fitting connections when moving piping layout to another level.
  • Improves the display of duct with insulation and lining for hidden line views when contained within a linked file.
  • Improves display of insulation on segments when viewed in ceiling plans.
  • Maintains the type parameter values for panel schedules viewed on a sheet.
  • Maintains circuits when upgrading Revit MEP 2011 projects in Revit MEP 2012.

Autodesk Revit® Platform 2012 Enhancements

  • Improves stability when switching the visibility setting of linked file from By Linked View to By Host View.
  • Corrects Ambient Shadow on objects which are contained within a mirrored linked file.
  • Improves the import of IFC files which contain overlapping walls.
  • Improves stability when exporting a project to DXF which contains a dimension style that is referenced more than 255 times within the project.
  • Corrects the resolution of the background image when calculating offset and scale.
  • Corrects duplicate column creation when using Create columns by Grid when some columns are already created on the grid.
  • Improves stability when setting a view to Realistic display mode.
  • Improves stability when navigating in 3D view after canceling a Print operation.
  • Corrects silhouette display for perspective views in projects with linked files.
  • Corrects the angle of Photometric Web based light sources when exported to FBX.
  • Retains the original IES files when exporting to FBX.
  • Reduces the scenarios where element IDs may become remapped or removed when Synchronizing to Central.
  • Improves stability when removing layers from floors, roofs and walls.
  • Corrects gbXML export of curtain walls where window openings were classified as air opening when using simple complexity mode.
  • Improves stability when accessing HELP
  • Help
  • Corrects mapping of Cable Tray, Cable Tray Fittings, Conduit and Conduit Fittings when exported to IFC.
  • Improves the consistency of beams being unique objects when exported to IFC.
  • Improves the placement of slabs when exported to IFC.
  • Improves the creation of beams, such as length, when imported from IFC.
  • Disables switching to 3D view if current view only is set when exporting to IFC.
  • Enables the export of filled regions to IFC.
  • Enables mass based curtain panels and mullions to be individual elements when exported to IFC.
  • Enables Structural Columns to be exported to IFC.
  • Allows elements hidden by category to be ignored when project is exported to IFC.
  • Enables Unicode support for both Import and Export of families.
  • Changes setting for "Export views on sheets and links as external references" to be enabled when exporting to DGN.
  • Allows exporting to DWFx if the view is blank.
  • Improves stability when exporting to DWG.
  • Improves the export of custom wall hatch patterns to DWG.
  • Improves stability after displaying a warning message.
  • Enables the use of Family Parameter when using the Material Browser Paint tool.
  • Improves stability when modifying part assemblies.
  • Improves stability when working within the Phases dialog.
  • Improves placement of linked point clouds based upon their origin.
  • Improves stability when printing to PDF in batch mode.
  • Improves stability when saving a family into the same folder as the type catalog.
  • Improves stability when upgrading projects.
  • Improves stability when setting a workset from Editable to non-Editable.  

Monday, March 21, 2011

Book Review: Mastering Autodesk Revit MEP 2011




Revit MEP has been out since August 2006, or almost 5 years now.  And new versions are usually released in mid-April.  This coming version will be the 7th release.  While the software has been around for a while, there hasn't been any good advanced documentation or books on the software.  In 2008, while attending AU, I was approached by a book publisher to write a Revit MEP book because so many people were asking for one, and none existed.  While I was excited about the opportunity, I couldn't find time in my schedule with a two year old and a newborn.

Over the last year, I've started to see some new books come out on Revit MEP.  But the one that is above the others is this one by Don Bokmiller, Marvin Titlow and Simon Whitbread.  I've done Revit MEP training with the AOTC courseware since the software was first released in 2006, and I wish that I had a resource like this book to train from.  While there is a learning curve of the basics, this book takes users to the next level and shows how Revit MEP is used in real world projects from start to finish, and not just showing you how to do a couple simple tasks that are part of a smoke-and-mirrors dataset.

I always say there are two types of people looking for knowledge on Revit MEP, and you must adjust your training accordingly.  There is the end user, who wants to know how do connect equipment, duct, pipe, lights, etc and read the engineering data that is generated from those connections.  Then there is the BIM manager, who wants to know how to get the equipment and connections to display correct for construction documents, and the engineering data to calculate correctly, and get projects to run quickly and efficiently.  But sometimes knowledge of how Revit works in the background is helpful for both types of end users of the software. And this book accomplished that.

While some books only apply to one type of Revit user, I really recommend this book for all users of Revit MEP.  It's in depth, and applies to all types of Revit users.  Even when a new Revit software version is released, this book will still be relevant.

This paperback book can be purchased directly from the publisher here:

or an Adobe E-Book can be purchased and downloaded from the publisher here:

or a paperback book from Amazon here:

AutoCAD Revit MEP Suite
  • VER      BUILD                NAME     
  • 1.0       2006 04 01    (Revit Systems 1) (1)
  • 2.0       2006 09 01    (Revit Systems 2) (2)
  • 2008    2007 04 12    (Revit MEP 2008, AutoCAD MEP 2008) (3)
  • 2009    2008 04 15    (Revit MEP 2009, AutoCAD MEP 2008) (4)
  • 2010    2009 04 16    (Revit MEP 2010, AutoCAD MEP 2010) (5)
  • 2011    2010 04 16    (Revit MEP 2011, AutoCAD MEP 2011) (6)  

Friday, October 01, 2010

The New “Revit Server”

Link to AECbytes "Revit’s New Server Extension" Article (September 28, 2010) by Lachmi Khemlani.  Lachmi Khemlani is founder and editor of AECbytes. She has a Ph.D. in Architecture from UC Berkeley, specializing in intelligent building modeling, and consults and writes on AEC technology. She can be reached at lachmi@aecbytes.com.

The Autodesk® Revit® Server Extension helps geographically dispersed teams more easily collaborate on projects of varying size and complexity. Web-based services help keep teams coordinated as they work on a single project from separate locations.

The Autodesk Revit Server Extension helps you to:
  • Work more effectively as a single project team over a distributed wide area network (WAN) with higher performance and efficiency
  • Maintain a seamlessly integrated collection of Revit central models on a single server that team members can access from local servers
  • Easily manage products on Revit central server using the web-based Revit Server Administrator tools
  • Benefit from built-in redundancy in case of WAN connectivity loss
This Subscription Advantage Pack consists of two separate components: an application update, Revit 2011 SAP, and a server component, called Revit Server 2011. An installation of Revit Server may function as a local server or a central server. However this document does not draw any distinction between the two, as the installation and removal requirements are essentially the same for both.

Revit Server 2011
Systems hosting Revit Server 2011 must have:
    • Microsoft Windows Server® 2008, 64 bit (not 2008 R2)
    • Microsoft IIS 7.0
    • Microsoft .NET 3.5 SP1
Refer to the Revit Sever Installation Guide supplemental documentation for more detail on system prerequisites.

Revit’s New Server Extension 2011 Video


Wednesday, September 29, 2010

Revit MEP 2011 Update 2 – September 2010

Revit MEP Update 2 – September 2010

Important Note:
Update 2 is not a full install; rather it is using service pack technology similar to AutoCAD®- based products. Prior to installing the Update 2, please verify that you have already installed the First Customer Ship build of Autodesk Revit MEP 2011 which is available below.


Update Enhancement List
Improvements made in Update 2 build (20100903_2115):


Autodesk® Revit® MEP 2011 Enhancements
  • The list of supported video cards and drivers has been updated.
  • Improves stability when opening a recovery file.
  • Improves the selection of the proper fire damper size when inserted into an oval duct.
  • Remembers the last justification when adding duct from the draw duct option within the right click menu.
  • Corrects the creation of a small duct segment when a reducer is inserted due to a change in duct size.
  • Improves stability when dragging a duct end to the connection point of hosted equipment.
  • Improves the automatic joining of Cabletrays.
  • Corrects the value produced for a calculated value column within Panel Schedules and Demand Factors.
  • Allows the load value of a spare within a panel schedule to be editable.
  • Corrects the display of Wire Size and Type properties to be “—“ for spares in panel schedule.
  • Corrects the unit formatting of cells within the Load Summary of a Panel Schedule.
  • Corrects the display of circuit number on wire tag when using circuit naming By Phase.
  • Improves snapping an adapter to sprinklers when inserted from the project browser.
  • Corrects the Air Changes per Hour calculation when running a heating cooling load analysis.
  • Improves the connections produced by Routing Solution layouts of pipe or duct.
  • Improves consistency of adding pipe, duct, conduit and cabletray when snapping to non-MEP elements.
Autodesk® Revit® Platform 2011 Enhancements

  • Improves stability when locking of constraints within families.
  • Improves stability when modifying the properties of an element.
  • Ensures „Select All Instances‟ when used on viewports within a sheet does select all the viewports.
  • Improves stability when using the “Create Form” tool when In-Place edit a mass.
  • Improves stability when using “Complex” complexity mode during gbXML Export.
  • Corrects glazing area when using “Simple” complexity mode during gbXML Export.
  • Improves stability when editing element Phase inside a group.
  • Improves consistency of the ifcflowsegment and ifcflowfitting properties during a re-export to IFC.
  • Improves stability when exporting to AutoCad 2000 DWG files.
  • Improves stability during export to DWG files when exporting a view with a linked DWG in "new layers for overrides" mode.
  • Improves stability after switching location within the InfoCenter settings
  • Improves stability of InfoCenter when logged into Revit with a double byte username.
  • Improves stability when selecting materials from within the materials dialog.
  • Improves stability when switching between views
  • Improves visibility of manually applied hidden lines during printing and exporting of Structural Hidden Lines views
  • Improves performance when using spinner control in the Decal Types dialog.
  • Improves stability when selecting array elements from within the Reveal Hidden Elements display mode.
  • Improves stability when finishing Sketch mode.
  • Improves stability when selecting a reference plane within the conceptual mass editor.
  • Improves stability when launching multiple sessions of Revit.
  • Corrects shadow casting of linked RVT files when in realistic display mode.
  • Improves stability when dragging sun.
  • Improves stability when upgrading Revit 2010 project file.
  • Corrects color of masked regions when rendered in Consistent Color display mode.
Autodesk® Revit® 2011 API Enhancements

  • Setting formula for Manufacturer/Type Comments as string no longer throws an exception.
  • Improves consistency between User Interface and API when using Family Type count
  • Improves the consistency of maintaining the preview image when Save/SaveAs.
  • Improves the consistency of creating the detail curve when the view’s detail sketch plane is not located where expected within the database.
  • Improves detail curve creation when the view does not have an implicit sketch plane.
  • MEP API: Cabletray Connector Angle property no longer throws an exception when rotating a cabletray.
  • MEP API: The following Electrical Parameter Types have been exposed to DB.ParameterType:
    • CABLETRAY_SIZE
    • LOADCLASSIFICATION
    • ELECTRICAL_TEMPERATURE
    • ELECTRICAL_DEMAND_FACTOR
    • CONDUIT_SIZE

Tuesday, July 13, 2010

Dependent Views, Matchlines, and View References in Revit: by Reid Addis

Dependent Views, Matchlines, and View References in Revit

Author: Reid Addis, Microsol Resources
Date Published: March 24, 2009

Autodesk University Article Link

Dependent Views were added to Revit in Release 2008. The concept behind Dependent Views is to allow you to maintain consistent annotation and View Scale among the main and dependent views while permitting independent crop regions for each view. A secondary result is that Dependent Views allow you to place different cropped portions of the overall View on different sheets while maintaining consistency of annotation and scale across sheets.

Normally when you simply Duplicate a view with Detailing, all of the annotation (text, dimensions, tags, etc.) become independent from the original view along with the View Scale. Thus if you change the value of the original object (adjust a dimension or edit text or delete a Room Tag) in one view, it has no effect on the duplicated object in the independent duplicated view.

This is not the case with Dependent Views. The annotation and view scale are identical across all the views. Change the view scale in ANY dependent or parent view, and it changes the view scale in ALL the dependent and parent views. In addition, the annotation is identical as well, so a change in ANY view again affects that same object in ALL views.

Using the “Getting Started” tutorial that comes with Revit Architecture 2009, I’ve created some Dependent Views of the Lower Level:

View 1


For clarity, I’ve turned on the Crop Region in the Parent View and added some Filled Regions to show the Dependent View Crop Regions. The “purple” area in the center indicates where these two regions overlap. This is where we will add a Matchline and View References in the Parent View to help coordinate locating these adjacent views when placed on different sheets.

Below are the two Dependent Views with the Matchline displayed that was added in the Parent view from the Drafting rollout of the Design Bar:



View 2

In the Parent View, from the Drafting rollout on the Design Bar, I will place a View Reference on each side of the Matchline.


View 3


Notice that as you place the View Reference, the Option Bar gives you the ability to specify which Dependent View is being referenced. Thus the View Reference placed in the West view will target the East view, and visa versa.

Equally critical is making sure that you actually have a Tag loaded from the View Reference Family. By default, this is set to and thus will fail to work.

View 4

The final step is to place these Dependent Views on Sheets, then watch how the View References update to include this information.



View 5

Notice that the View References now show which View and Sheet number the Matchline adjacent view is on.



View 6


I hope this clears up any confusion you may have had about Dependent Views, Matchlines, and View References.

Saturday, May 15, 2010

Troubleshooting Revit MEP

A 20 minute video from Autodesk's Harlan Brumm and Jerry Lee Smith covering:

Overview of the Revit MEP Workflow
  • Create new project using MEP template
  • Save Arch model as central file on server
  • Link in models using origin-to-origin
  • setting links to be room bounding
  • copy/monitor levels
  • Setting up views and apply view templates to views
  • create levels to account for plenum spaces
Troubleshooting Spaces and Zones
  • space not visible in view
  • rooms are "unoccupied"

Troubleshooting Revit MEP Performance
  • Not following workflow
  • not creating logical systems
  • large connected duct networks
  • complicated families
  • poorly connected elements
  • Limit color schemes
  • place endcaps on open ducts
  • ensure flow direction on connectors is correct


Monday, April 19, 2010

Upgrading Your Custom Revit MEP Library from 2010 to 2011 Format

Because some architects might be early adopters to 2011, and some architects might wait until the first service pack is released before upgrading their projects to 2011, engineers will find themselves working with architects using different versions of Revit.  Because Revit is not backwards compatible, engineers will have to run multiple versions of Revit MEP to match each architect that they are working with.

The history of this issue is that everybody working on a Revit project must be using the same version of Revit.  Architecture, Structural and MEP must all be the same.  If one team is using an newer version, the other teams who are using an older format won't be able to read the newer format.  The new format has new tools, new objects, and new settings that older versions don't understand, and weren't written to automatically know what new objects would be coming out in the future.  Now if one team is using an older version, the other teams will be able to open an older version, and upgrade that project to the newest version, but the team using the older version won't be able to open the new format version of the other team members.

So now that we understand why we have to install multiple versions of Revit MEP on our workstations, we will also need to have multiple versions of Revit Libraries on our server.  The 2011 directory, obviously will have the newest contect, and that content can only be used for 2011 projects.  That content cannot be used for 2010 projects.  So any 2010 project must use content from a 2010 content directory.  Any custom 2010 content can be copied, and the copies can then be upgraded and added to the 2011 directory.


To Use the Content Batch Upgrade Utility:


  1. Copy Upgrade_RFA.txt and Upgrade_RFA.bat into the root directory of the library that you want to upgrade.
  2. Run the Upgrade_RFA.bat to create the file list to upgrade, famlist_rfa.txt.
  3. To launch the utility, from the library directory, drag Upgrade_RFA.txt onto the Revit icon on your desktop.
  4. After upgrading, delete all backup files from the library.


Make sure all of your .rfa files are not read-only and delete all backup files from the library. If a particular family fails to upgrade properly, the utility will stop.  If this occurs, open famlist_rfa.txt in Microsoft Notepad, and remove all previously upgraded families and the failed family from the list. Save famlist_rfa.txt, and re-run the utility.

Thursday, March 18, 2010

Autodesk Publishes Framework to Help AEC Professionals Implement BIM Process

The Autodesk BIM Deployment Plan is a Free, Web-accessible Resource Offering Tools and Guidance Based on Real-World Practices for building industry professionals interested in implementing Building Information Modeling (BIM). Tools offered in this resource provide a practical framework for AEC stakeholders, and can be used by individual organizations on specific projects. The BIM Deployment Plan includes:

  • BIM support materials for owners, architects, engineers, and contractors
  • Templates to streamline multi-discipline communications
  • Recommendations for roles and responsibilities
  • Best business process examples
  • Software suggestions for an effective BIM environment
DOWNLOAD the BIM Deployment Plan Here

SAN RAFAEL, Calif - Autodesk, Inc has announced the availability of its Autodesk BIM (Building Information Modeling) Deployment Plan: A Practical Framework for Implementing BIM, a new web-accessible resource for building industry professionals. Aimed at all AEC stake-holders, including owners, architects, engineers and contractors, the free guide includes support materials and a framework based on real-world applications of BIM. Tools offered include templates to help manage multi-discipline communications within a BIM project, as well as suggestions for the roles and responsibilities of each party in a BIM process-based project, best business process examples and suggested software to support an effective BIM environment.



“The BIM Deployment Plan is helping us develop a BIM implementation process best suited for the technology needs of the project and tailored to the abilities of the players involved. It is also helpful in defining clear roles and responsibilities for the execution of workflows on our jobs.”



As the building industry continues to evolve, technologies such as visualization, simulation and analysis are fundamentally changing how projects get delivered. Now more than ever, collaboration and transparency are essential and effective for anticipating and reducing problems related to cost overruns, schedule, scope and quality. Autodesk has been at the forefront of BIM technology adoption including the creation of a portfolio of software products that facilitate a BIM solution.



“New technology is creating enormous opportunities for the building industry to improve processes and outcomes, and many organizations still need guidance on how to share information as well as streamline project communications,” said Phil Bernstein, FAIA, Autodesk vice president of building industry strategy & relations. “The Autodesk BIM Deployment Plan was designed to help companies navigate the entire process via one collaborative framework and subsequently deliver projects faster, more economically and with reduced environmental impact.”



“As strong advocates of BIM, we can develop building design strategies that are extremely well integrated and coordinated, substantially increasing our efficiency and lessening the building time – all of which allow us more time to create inspiring designs for our clients,” said Dick Thomas, vice president at SHP and executive director of 2enCompass. “Now taking this a step farther, The Autodesk BIM Deployment Plan has helped us further advance BIM project implementation by better documenting stakeholder roles and responsibilities and most importantly, helping us deliver the right information from the project model to the right people at the right time to drive our project forward.”



“Communication and collaboration amongst strategic team players is vital to the success of our projects,” said Mark Konchar vice president at Balfour Beatty Construction, Washington division. “The BIM Deployment Plan is helping us develop a BIM implementation process best suited for the technology needs of the project and tailored to the abilities of the players involved. It is also helpful in defining clear roles and responsibilities for the execution of workflows on our jobs.”

Friday, December 18, 2009

Implementing Autodesk® Revit® MEP: A to Z

Implementing Autodesk® Revit® MEP: A to Z


Event Year: Autodesk University 2009
Class ID: MP322-1

Primary Speaker: Todd Shackelford

Class Information
Class Type: 90-Minute Class
Expertise: Intermediate
Industry: Building
Primary Track: MEP Design and Engineering
Primary Software: Revit MEP

Class Audience
CAD managers, IT managers, and engineering professionals

Class Description
This class will outline a framework for transitioning to Revit MEP. From setting expectations and defining goals for Revit, building information modeling (BIM) and integrated project delivery (IPD) to plotting the construction documents, we will walk through the checklist of elements required to help Revit really work in your office. Along the way, this class will demonstrate how to defuse the landmines of a Revit implementation, and some clever Revit tricks will be exposed to smooth the transition.

Key Learning

  • Understanding the role of Revit MEP in BIM and IPD
  • Creating a Revit MEP template for success
  • Creating MEP Families that work for you
  • Revit MEP transition tips
  • What not to do

Tuesday, September 15, 2009

Autodesk Navisworks 2010 Service Pack 1 Now Available

Download Here
http://usa.autodesk.com/adsk/servlet/ps/dl/item?siteID=123112&id=13861499&linkID=10382102

General Updates

This service pack fixes the following defects.
  • Clash Detective. Camera now transitions more smoothly between clash results.
  • Object Animation. When adding a keyframe to the end of an animation the object movement now remains consistent.
  • Comments window. TheID column in the Comments window is now labeled Comment ID.
  • Hyperlinks and Smart Tags. Autodesk Navisworks now remembers Hyperlinks and SmartTags visibility settings between sessions. New Show Hyperlinks and Show SmartTags options have been added to the Options Editor (Interface node).
  • Sectioning. The section bar slider now maintains correct settings when user switches between viewpoints.
  • Collaboration. When using the collaborate function all window states now remain consistent.
  • AutoCAD Interoperability. AutoCAD elements are now correctly displayed on the Properties tab of the Selection Tree window.
    Installing Autodesk Navisworks 2010 no longer causes issues with AutoCAD VBA customizations.
  • Inventor Interoperability. You can now view Inventor 'surface models' in Autodesk Navisworks.
  • IFC Interoperability. Improved support for IFC 2X2 files. Missing components and misplaced Geometry issues are now resolved.
  • Revit Interoperability.
    Structural usage text designated in Revit is now displayed in Autodesk Navisworks.
    Window and door openings are now supported when exporting NWC files from Revit.
    Revit models modelled in mm now appear the correct size in Autodesk Navisworks.
  • AutoCAD Visual LISP. Visual LISP feature of AutoCAD 2008 and 2009 now functions correctly after Autodesk Navisworks 2010 is installed.

Tuesday, August 18, 2009

Revit MEP Calculations. How'd They Do That?

Ever wonder what's inside the black box of Revit? What standards and methods are being used in their calculations? Can I trust them. Well, in the past I would just compare my calculations to Revit's calculations to see if they were close.

Pipe Sizing
You use the Pipe Sizing dialog to automatically specify the sizing for sections of pipe using friction and/or velocity sizing methods.

Fixture Units to Flow (GPM) Conversion
Revit MEP provides a general conversion from fixture units to flow, using the values found in the 2006 International Plumbing Code (IPC), Table E103.3 (3). The flow conversion method selected in the Instance Properties dialog for the selected system determines the section of the IPC table used for the conversion. The resulting flow is used to calculate pipe sizing.

The value calculated for flow can be helpful in sizing the branch piping for subsystems. However, when specifying sizes for the main piping, you should consider a variety of other factors, including the type of system, the type of building, peak demand, available supply pressure, the pressure required at the highest fixture, and limitations imposed by local authorities, selected fixtures, and supply source. The 2006 International Plumbing Code, Appendix E provides detailed information that must be considered when planning a plumbing system

Autodesk is working on releasing more documentation on how the data is calculated.

The PDF documenation is in beta. You can download the file at:

Revit MEP electrical wire sizing calculations
Revit MEP Duct Sizing calculations

Revit MEP_Hydronic_Piping calculations

Thursday, April 03, 2008

Revit MEP Coordination Views

When you are using either a Mechanical or Electrical view disipline, the view will display those objects darker than the architectural objects or other MEP objects. You can see from this Mechanical 3D view below, the walls are light, and you can see the piping going through it.


If you change the view properties so it is displaying using a coordination disipline instead, the walls will become darker, and the piping will be hidden behind the wall objects. But it will not display the piping with hidden lines.


If you create plan views using Coordination disipline, you can see the pipe that goes through the wall or under a light fixture or another pipe as disappearing.


When in plan mode, and the view set to a mechanical disipline, you can see those pipes passing below other MEP objects as hidden lines, but not shown hidden through the wall objects as shown below.


To do this, you'd probably need to use a basic line tool for this. Perhaps there will be more control provided for this feature in the future. For now the above workaround may help.

Thursday, December 20, 2007

Problem Creating Deployment image with Last Revit Build

When you tried to create a Revit product deployment image with a build number of 20071109_2345, you received the following error message:

user cancelled installation

This error is caused by outdated DLL files on the system.

To correct this issue, you need to download and install the Microsoft Visual C++ 2005 SP1 Redistributable Package. During the installation of this package, updated DLL files will be copied to the system. After the installation, you will be able to create the deployment.