RevitTricks

K eep section and detail callouts relatively tight to what is being annotated.   Basically – If the current view’s range ‘touches’ the extents of a tag’s Crop Region that callout/section/detail will show in the view. If MORE space is needed for annotations- turn the annotation crop on and stretch the limits to include the necessary annotations.   There are many places where annotations can be turned off but all views should be kept closely cropped to the elements (i.e. curtain wall elevations) referenced.   Several comments regarding “CW showing in plan” were due to the section-elevations of the curtain walls extending too far to the plan views below.

If you don't have the luxury of a 100% Revit-BIM Based project you will need to import/export to CAD and subsequently DGN for most DOD / USACE projects. The   Revit View naming conventions established in the DOD outline correspond with slightly adapted NCS Version 4.0 File naming conventions. There are a few basic reasons for the format and rigidity 1. The view names need to be organized in something other than "DETAIL 1", "CALLOUT OF FLOOR PLAN 1" "ELEVATION 1", etc. from Revit's generic naming conventions. 2. Because the views are exported to PDF and DWG reference especially in Hybrid projects- the best convention we have to follow is based on the current NCS (National Cad Standard currently version 4.0).  Every major player in the US either loosely or strictly follows or will be following this standard; Including U.S.A/C/E, VA, GSA, and DOD.  Building Smart Alliance  currently oversees the NCS  and the NBIMS i...

Added... " Browse to the export folder. " below Cad Export Process (After bare-bones & Materials are assigned) Revit Icon> Export> CAD Formats > DWG Select set to export (Or Insession) Select sheets/views to filter in the list. Sort by name to itemize everything by drawing type and its name Set up CAD Layer naming (If not already set) This may require selecting one of the read-only layer exports and resaving it under a different Name. Revit ADDS ALL LAYER NAMES from linked drawing files- to prevent this list from becoming too large we made it read only. Browse to the export folder. Strip everything off the ‘tail’ of the file name so the project number (and building identifier if necessary) are the only   elements left to use as a prefix. Revit will add a “-“ after this prefix. For standard CAD export - Make sure the [ ] Xref views on sheets is unchecked. This places all elements with the sheet in one file. For “STRIP REFERENCING”   Make...

Finish extents tag-   to show extents of finish along wall in plan.  This 'tag' is actually a  DETAIL COMPONENT that you can use to tag walls/extents of finishes to show the extent of finishes in plan (Interiors old-school). It can be taken one step further- By incorporating this detail component into a generic wall hosted family- it can force to snap to walls and will show wherever the instance is cut. These families would actually map the extent of the wall finish as a wall-hosted object which then would show the tags when cut. This can be done but would take some reconstruction of the family to keep it under control (Like the ADA graphics- it would likely need to be a generic subcategory and/or locked down to a specific workset) MARK and DESCRIPTION are the parameters for the text/graphics. These are designated by type. FINISH_EXTENTS.rfa

  To show the ceiling plans correctly, the RCPs will be cut at a height of 7’6”   All the drop soffit areas lower than this will need to have plan regions added to them to drop the RCP cut plane in these regions to 6’9” to display and register correctly.       A SINGLE SKETCH in the PRIMARY VIEWS with all the plan regions indicated can be used to lower the view across all drop soffit areas that are below the 7’6” mark similar to below. Try to keep relatively tight to the   Without a ceiling to tag, no height information or graphics stippling/representations will show (The elevation targets will disappear).        

Autodesk likely destined for the clouds... So' Private and Public' (MS ' Dedicated VS Standard' ) versions are already being run in the clouds... HUGE application implications for work-sharing applications like REVIT! http://labs.autodesk.com/technologies/trials/   OVERVIEW Welcome to Project Twitch! This project is testing remote delivery of our applications over the Internet. The goal of project Twitch is to enable you to test and try the latest versions of AutoCAD, Revit, Inventor, and Maya without having to install or download the applications. These applications run remotely on our servers and are delivered to you over the Internet.          

View references  – there are two types of VIEW REFERENCES  – opposite and adjacent .   View References ONLY show in PRIMARY<>Dependant view relationships. They are not visible in standard views. It is best to find the extents of the dependent views from the primary view and place the view reference tags there- use the dependant view extents (Dashed in view/annotation crop regions in the primary view) to place the tags.   BOTH Opposite and Adjacent tags should be used as they ‘grow’ from opposite sides of the match line- The invisible aligning line (Below in purple) should align with the match line. Each must point to the corresponding dependant views- adjustable from the options bar or element properties.   NOTE: ·          In the primary view reference ALL view reference tags show. ·          In the dependant vie...

This document outlines the processes of cross-platform collaboration between Revit and AutoCAD. Version 2010-06-03-1.0 Basically the steps involved in Exporting from Revit to CAD (and back) are as follows: Creating reference in Revit (Discipline and type-specific, plan, section, elevation, Callout or detail) Naming the callout view name correctly. Creating sheets in Revit (Setting up the details on the sheets in Revit) Exporting Revit to CAD Matching Revit output in CAD Detailing in CAD STRIP REFERENCING (For re-importing to Revit) Re-Importing the enhanced information back into Revit. NOTE:   Elements shown in RED are behaviors that need to be verified with each upgrade/update to Revit or CAD editing program. Each update can cause its own unique set of issues and should be tested on a case-by-case basis. This should probably be done with a single detail/sheet export/import from Revit to CAD before full export to CAD is assumed to be working correctly. There ...