This gave me the clue that the architectural model was a detached central model. This means that the model has been detached during an eTransmit process.
It is hard to find technical information regarding the state of these models. From what I’ve figured out, the model is in a state where it is technically “read only”. So if the linking process requires accessing or revising anything in the linked model, you will get an error. In this case it was an issue with permissions to edit shared coordinates.
Let’s talk a little about Plan Regions in Revit. In a nutshell, this tool helps to show areas of a View that may need to deviate from your view’s View Range. Aside from the common uses for this in architecture, mechanical designers can actually get their risers to display properly when using a vertical elbows.
Mechanical and plumbing Revit Designers have undoubtedly run into issues with their ducts that turn vertically if the elbow is outside of the view’s View Range. Revit does not cut through the elbow properly, if it cuts through it at all. Note the image below is missing the “X” within the riser to graphically designate which system the duct is on.
The issue is caused by the View Range settings for your view. Don’t fuss with the View Range settings for the entire View because tweaking View Range for one riser can be catastrophic for your the rest of the elements on your View.
The Solution: Use a Plan Region
The steps below outline a simple workflow to fix this issue. The goal is to create a Plan Region that encompasses the shaft’s view range requirements. Note that this technique also works with pipe elbows that do not graphically show the proper up or down symbol.
First, take note of the elevations that you need where you need to adjust your view range for the Plan Region.
Next, go to View > Plan Region and draw a shape around the area you would like the View Range to effect.
Important: Your plan region needs to encompass the entire riser for this to work. If the outline of your Plan Region overlaps the duct, it will not be effected.
You may want to extend your Plan Region a little further out than the duct itself. Note that the Plan Region outlines do not print.
Now we must adjust the View Range for the Plan Region. With the outline of the Plan Region selected, go to the View Range setting in the Properties window.
Adjust your View Range accordingly based on your measurements from step one.
The riser should now display the appropriate symbology within the duct that is turning up or down.
I have been working on a Dynamo Workflow that will purge out all views and sheets from a Revit model. Yes, there are several add-ins that currently accomplish this task, however I eventually want to create a “Super Purge” Workflow that will purge a model of all views, sheets, and elements for me. More on that to come.
The SetDifference node is grabbing all views in the current document from the Document.Views node and removes the user-specified view to keep in the model from the Views node. Note that Revit maintains the requirement to have at least one view within a project.
Then, the Springs.Doc.DeleteElements node deletes all views (except for the one chosen in step one).
Today I was challenged with figuring out why a revision schedule from a titleblock family was not showing the revisions on the sheet that the titleblock was placed on.
I found a subtle setting in which I’ve never used before – it is to set a fixed Height of the revision schedule. I suppose this could be useful if you would like to limit the number of rows in a schedule. Apparently, this can restrict your revision schedule to the point where it won’t display any revisions whatsoever.
The fix was to change the Height setting to “Variable” rather than “User defined”.
I remember my early days of Revit and working with architecture that had several angles in plan view. Cutting a section without knowing the exact angle is difficult in Revit and the Align tool currently does not work on section lines.
Here is a workaround to rotate your sections to align with any angle within Revit.
1) Draw a straight section
Make sure it is perfectly straight or this method will not work.
2) Use the rotate tool
Select the section from plan view and click Modify > Rotate.
3) “Place” your center of rotation
This step is where the magic happens. Once you choose the Rotate tool, there is a checkbox on the Options Bar that says “Center of rotation”. Click the “Place” button.
4) Pick a point
Choose a point that snaps to an element that has the angle you would like to reference. In this example, we will use the midpoint of the elevator wall.
5) Create a rotation reference
After you’ve picked your center of rotation, you need to create a starting angle for the rotation. This reference line should be parallel to your section line. In this example, it is horizontal.
6) Snap to the proper angle
To complete the rotation, snap to the line that you are using as a reference.
7) Done and done
You have successfully aligned and rotated a section to match an angled element in Revit!
This morning, I ran into an interesting bug in Revit 2016. I opened up my Macro Manager per the norm, but when attempting to create a new module Revit wouldn’t save the new module. It successfully opened the dialog box to let me choose a name, language, and description, however once I clicked “OK” nothing happened. Sharp Develop did not open nor did the new module appear in the Macro Manager window.
Navigate to your Macros folder on your C drive:
You may see multiple years in this folder, one per Revit version installed on your computer (e.g., 2014, 2015, 2016, 2017). Move the year of Revit that you are working in to a temporary folder like your desktop.
Go to your Macro Manager and create a new module.
By creating a new module, Revit recreates this directory and is able to successfully create a new module for your use.
A great tutorial. What you are essentially doing is creating a family which you can stretch and contract using parameters. You will also array a label so that you can have your text repeating over the linetype.
BIM Track™ is a web-based collaboration platform that empowers your team with better coordination workflows. BIM Track™ provides a central hub for all coordination information from design to construction. With information at your fingertips, you can get access to your data anytime, anywhere, either from a desktop or mobile device. Charts and graphics help understand data and your management performance through precise metrics. We promote openBIM workflow solutions by supporting IFC (Industry Foundation Classes) and BCF (BIM Collaboration Format).
I chose to try out BIM Track because it has a web-based comment and issue tracking interface. This type of interface is ideal because it will let less technically-savvy team members access the comments without opening any models.
It is really a toss up between using A360 or BIM Track for this project, but since BIM Track is free (up to 50 comments) and A360 requires paying for and configuring licenses and contracts, BIM Track seemed like an easier way to test the waters with minimal time and money invested.
My initial “handshake” with this software was a firm one. The add-in prompted me to register online which was a simple form on a website. Immediately after, I was prompted to create a hub to host my projects. I created a project easily. I was able to figure this out without training.
At first glance, the functionality of BIM Track seems extremely similar to A360. The main difference that I noticed is that BIM Track is actually installed as an add-in to Revit and Naviworks which allows you to easily view a coordination item directly in your working model. This seems like an excellent feature that A360 currently does not support (they probably will roll this feature out at some point).
Playing Nice with Revit and Navisworks
From the BIM Track window within Navisworks or Revit, the user has the ability to view issues, edit issues, and create new issues. There are even some filtering options for models that have several issues to track.
Clicking on the “View in model” button works well. BIM Track seems to essentially save the location of the camera at the time the issue was created. This gives the user the ability to zoom to a spot in Navisworks or Revit which should make the workflow of fixing issues much simpler than our current processes.
Clicking on the “Edit” button takes the user to the web interface in which one can contribute to a comment thread or make the task complete.
Room for Improvement
Being as robust as the software is, there is no surprise that I ran into a few items that could use improvement when using BIM Track in a live environment.
Navisworks completely froze when creating an issue in BIM Track. I am unable to replicate this issue.
When an issue is created in Navisworks, you cannot zoom to the location of the issue in Revit by clicking the “View in model” option. Ideally, it should open the Navisworks model and zoom to the location the issue was originally created rather than do nothing.
Commenting within the Revit or Navisworks add-in would be a “nice to have”.
During my initial testing of this product, it seems as though this is a worthy application for use in smaller firms and smaller projects. I think there is a lot of potential for this add-in to take off, however I would need to conduct more testing before rolling out to a 50-person team of Revit designers and engineers.
As I continue testing, I will post updates with my experiences using BIM Track.
Have you used BIM Track?
What do you think of the software? Post a comment and let us know what you think!