In the past, some users have automated Revit to NWC export to happen overnight using customized journal files. Kyle Morin has now created an addin that monitors model changes and automatically keeps your NWC up to date, essentially in “real time”.
You can download it for Revit 2014 here, and view / contribute on the open source page here.
Check out his post at:
Revit to Navisworks: Auto NWC View Exporter – kylemorin.co Blog
Quick fix for Revit 2012:
- Close Revit
- Go here, download and extract ZIP
- Go to Revit 2012 Program folder and rename AdWindows.dll to AdWindows.dll_OLD
- Copy AdWindows.dll from the extracted folder to the Revit 2012 Program folder
- Open Revit Architecture 2012 – your ribbon problems should be fixed
For Revit 2013 links, see below:
Ribbon behavior problems occur in Revit 2012 and 2013 after the installation of Microsoft .NET 4.5, which is one of the pre-requisite for Revit 2014. This is why this problem is typically encountered after Revit 2014 is installed side-by-side with a previous version of Revit. For those using Revit 2012, the Autodesk Revit 2012 – Ribbon behavior due to .Net 4.5 installation hotfix will resolve this problem. And for Revit 2013 users, the fix is included in the latest update releases, which are available from the following links: Revit Architecture, Revit MEP, Revit Structure, andRevit.
Autodesk Revit QA
Related forum thread:
Have you ever used the 2014 feature Temporary View Properties? If you have, you might have noticed that it automatically creates a list of the (temporary) View Templates that have been used recently.
What Revit Wants is for us to stop clogging up our models with 100s of working views, and instead just use 2 or 3 “Working View Templates” along with the Temporary View Properties feature.
This way, you don’t have to keep switching between Working and Printing views all the time…
Also, apply some keyboard shortcuts to these (the “Restore” one will be particularly useful):
Let’s say you want to quickly schedule a particular Model Group’s instances in your project, and also be able to quickly “find” them in the project:
- Make a new Generic Model that can have everything “hidden”
- Make sure it has a Shared Parameter that is set to “Varies by Group Instance” in the Project
- Make a Schedule that shows only this family (using a Filter). In essence, this schedule will now be scheduling the actual group.
- If you want to, enter some identifying information into the “varying” Shared Parameter that you made in step 2
- Use the Highlight in Model option in the Schedule to locate each instance
This process is only made possible in 2014, due to the ability for parameters to vary by Group Instance.
I adapted and expanded on this method over at:
Auditing and Comparing Model Groups in Revit 2014
Most of you know that in Revit 2014, you can stack Project Browser, Properties Palette and other “panes” on top of each other, resulting in a tabbed dialog.
But did you know you can also drop them beside each other, resulting in a Split Pane view? Like this:
Note: you can also do this with panes stacked on top of each other. And, it is not limited to two panes vertically or horizontal, you can do a mixture, like this:
Some up-to-date info on data exchange between Tekla and Revit, including IFC and SDNF workflows (from revit structure blog):
The main purpose of the IFC import into Tekla is to allow the fabricator to accurately build a model from the consultants Revit model. However, you can convert certain objects from the IFC file to native Tekla objects such as beams, columns, footings etc. This is clearly useful rather than building a model from scratch. I tried this on a few beams and columns and again found no discrepancies with the original Revit Structure 2014 model, however, as you would expect the stairs translated to a bounding box. See the below image including the report.
I also imported an IFC model from Tekla to Revit with some fairly good results that are fine for coordination purposes. I would imagine that this may be better in a product such as Navisworks…
The best way to incorporate the analytical model from Tekla to Revit is to transfer the model as CIMsteel (Note that you will need to install the SDNF Import/Export for Autodesk Revit 2014). This gives you the option of transferring the analytical model
Revit Structure 2014 and Tekla Structures 19.1 | Autodesk Revit Structure
This is basically what will happen:
So, basically you can choose to re-index to RCP, or leave them as-is and continue to use the PCG.
While there is much to love about the smooth performance RCP point clouds, I have to admit that PCG point clouds seemed to allow:
- greater point density, perhaps due to different default indexing settings,
- more consistent display (ie. once the view had regenerated, that’s how it would stay – while RCP seems to slowly and continuously re-gen until you get a very realistic view)
- and didn’t have cropping problems – I’ve noticed that a 3D Section Box with an RCP point cloud will require a greater “buffer” than with PCG. If you crop it too close, the RCP points won’t show (even if they physically exist in that section box space).
Swap it for another parameter and then back again…
This is easy on 2014 – after selecting the column or column header, you have an option in the ribbon to swap for another parameter. When you swap it back again to the original, the name will match the Field / Parameter name, until you override it 🙂
Download it at:
SuperFilter | Autodesk Revit | Autodesk Exchange Apps
It has a dockable interface, shows number of objects and can list ID of elements, as per the translation from this Russian site:
- Now Super Filter works with all types of objects, including the objects selected in the manager of the project.
- Now the window is presented in the form of a constantly open window similar to the properties window and the project manager. You can place it on the analogy of these windows, even doing extra tab.
- The updated interface is both visually and in functionality. Now show the number of objects in each node. It is also available a list of ID elements.