I don't recall when this first showed up but I noticed it first in Revit 2012. Here's what it looks like with a right-click in Revit 2013.
My first reaction was cool! Then I wondered, "When or why would I use it?". Pondered it for a bit and decided that it might be cool if I have a sheet full of details that needed some cleanup. Create a view template and then apply it right quick. Then again I could just select multiple views in the project browser and apply them. With Revit 2013 my view templates will adjust all those details as soon as I change the template, or at least they can if I set it up that way. I suppose this feature might be handy if I forgot to do it and they were all on sheets at this point.
A subtle refinement to process that probably just goes unnoticed? I wonder how many of my readers use it, know about it, care?
Revit OpEd
Welcome to Steve Stafford's Blog ~ Revit OpEd = OPinion EDitorial ~ My view of things Revit, both real and imagined.
Wednesday, May 16, 2012
Tuesday, May 15, 2012
Revit 2013 - View Types
It is now possible to create new view types for all views except for area plans and sheet. This means you can create your own versions of floor plans according to discipline or perhaps design phase. We've been able to do this with sections, elevations and detail views for some time. As Revit's features have been merged into the new Building Design Suite "Revit" it became apparent that putting all the tools in one box created some curious view, view template and discipline control issues that had to be sorted out, thus being able to create view types for more views was born.
Further, views can be tied to view templates and have changes to a view template take effect immediately in a view or many views. We can apply a view template like before, just to make a change or we can assign a view template to the view so that it will alter the view without the past extra step of applying the view template. This is the typical assumed behavior that most people where surprised to learn did not happen in the past.
One curious thing that is documented at the WikiHelp site regarding these new view types, changing a view from one type to another does not actually apply the view template change that is assigned (if any) to the view. It is an instance parameter so it's an extra step you've got to take to make sure the view has the correct template assigned.
If you use the Apply View template option on a view assigned to view template already you'll get this message.
It's confirming that you really want to apply a different template's settings to the view. It also says that the only properties that will be altered are those that aren't in conflict with the other template. Hopefully the swapping of view types won't occur much after creating them initially and getting this sorted out. If you do find yourself needing to swap them around, just remember to check the view template assignment.
Tip: They've added View Template to the available fields in View Lists (schedule) so it can be managed there too.
Further, views can be tied to view templates and have changes to a view template take effect immediately in a view or many views. We can apply a view template like before, just to make a change or we can assign a view template to the view so that it will alter the view without the past extra step of applying the view template. This is the typical assumed behavior that most people where surprised to learn did not happen in the past.
One curious thing that is documented at the WikiHelp site regarding these new view types, changing a view from one type to another does not actually apply the view template change that is assigned (if any) to the view. It is an instance parameter so it's an extra step you've got to take to make sure the view has the correct template assigned.
If you use the Apply View template option on a view assigned to view template already you'll get this message.
It's confirming that you really want to apply a different template's settings to the view. It also says that the only properties that will be altered are those that aren't in conflict with the other template. Hopefully the swapping of view types won't occur much after creating them initially and getting this sorted out. If you do find yourself needing to swap them around, just remember to check the view template assignment.
Tip: They've added View Template to the available fields in View Lists (schedule) so it can be managed there too.
Labels:
Revit 2013,
View Templates,
Views
Monday, May 14, 2012
Dept. of Echo - Don't use the Basic Ceiling
Originally posted here August 2009 and still true with Revit 2013
When an architect uses the Basic Ceiling-Generic type they are creating a situation for the Revit MEP user they may not be aware of. Face based content does not orient themselves to the correct side or face of this ceiling. For air terminals and others this means they are usually upside-down. I created a short video to demonstrate what I'm writing about.
You can listen and watch below:
Here's an image to convey the issue without watching the video. The left side is a Basic Ceiling and the air terminals are upside down. The right side is the Compound Ceiling and the air terminals are okay.
When an architect uses the Basic Ceiling-Generic type they are creating a situation for the Revit MEP user they may not be aware of. Face based content does not orient themselves to the correct side or face of this ceiling. For air terminals and others this means they are usually upside-down. I created a short video to demonstrate what I'm writing about.
You can listen and watch below:
Here's an image to convey the issue without watching the video. The left side is a Basic Ceiling and the air terminals are upside down. The right side is the Compound Ceiling and the air terminals are okay.
Labels:
Ceilings,
Revit MEP,
Tips,
Troubleshooting
Friday, May 11, 2012
Hide Those Connectors
A recent question at Revitforum.org asked about hiding the connectors in family content for the sake of cleaner previews.
To accomplish this:
To accomplish this:
- In the view you want to use as the preview
- Select the connectors
- Click Temporary Hide/Isolate
- Choose Hide Element
- Save the file
- Close the file
Labels:
Connectors,
Preview,
Tips
Thursday, May 10, 2012
BIM Coordinator for Civil 3D and Revit
Autodesk Labs posted an application that was developed by Autodesk Consulting. You can read more information HERE.
It functions as a plug-in that is installed in both applications, Civil 3D and Revit. It allows a Civil 3D user to define the shared coordinate system to be passed on to a Revit project. Running the tool in Civil 3D is based on selecting two points on a reference building footprint file (don't forget paying attention to elevation) and saving the information to a separate file.
Note that it uses a file formatted as ACCSXML (Autodesk Consulting Coordinate System eXtensible Markup Language).
The file is then used in combination with a plug-in tool inside Revit that asks you to pick the same points in Revit and then select the source file. As the project progresses, you can pass model data back and forth easily as long as you export by specifying the correct project units and Shared Coordinates each time.
You can watch a video at You Tube that explains how it works (9:53)
The process described assumes that the person deciding where the building goes is using Civil 3D which in my experience is not necessarily accurate. They'll ultimately be responsible or define it precisely eventually but the building location is often affected by a lot of things and roughed in by designers using an underlay of a survey and civil data.
It is also very important that the person using Civil 3D passes along the two key points on the building. If they get this wrong or we misunderstand them we’ll end up with a discrepancy when we potentially pick slightly different points. Of course this assumes that the civil engineer is not sitting right next to “us”, the architect or structural engineer. Connecting the information between all parties still boils down to someone deciding what building location is "spot on".
Check it out, might help your next project?
It functions as a plug-in that is installed in both applications, Civil 3D and Revit. It allows a Civil 3D user to define the shared coordinate system to be passed on to a Revit project. Running the tool in Civil 3D is based on selecting two points on a reference building footprint file (don't forget paying attention to elevation) and saving the information to a separate file.
Note that it uses a file formatted as ACCSXML (Autodesk Consulting Coordinate System eXtensible Markup Language).
The file is then used in combination with a plug-in tool inside Revit that asks you to pick the same points in Revit and then select the source file. As the project progresses, you can pass model data back and forth easily as long as you export by specifying the correct project units and Shared Coordinates each time.
You can watch a video at You Tube that explains how it works (9:53)
The process described assumes that the person deciding where the building goes is using Civil 3D which in my experience is not necessarily accurate. They'll ultimately be responsible or define it precisely eventually but the building location is often affected by a lot of things and roughed in by designers using an underlay of a survey and civil data.
It is also very important that the person using Civil 3D passes along the two key points on the building. If they get this wrong or we misunderstand them we’ll end up with a discrepancy when we potentially pick slightly different points. Of course this assumes that the civil engineer is not sitting right next to “us”, the architect or structural engineer. Connecting the information between all parties still boils down to someone deciding what building location is "spot on".
Check it out, might help your next project?
Subscribe to:
Posts (Atom)


