Showing posts with label Tags. Show all posts
Showing posts with label Tags. Show all posts

Monday, July 15, 2013

Revit MEP - Free Size Parameter

If you use the Free Size parameter instead of Size you might notice a subtle anomaly.

In elevation views where we only see one dimension of a duct Free Size does not switch between WxH and HxW, the Size parameter does switch. In other views they both display width x height. In section or elevations that show the profile of a duct both dimensions are measurable and each parameter is consistent, they default to Width x Height.


It does seem like an oversight on their part, they ought to be consistent whether we use Size or Free Size.

Wednesday, May 29, 2013

Tag Slope of a Ramp

We can apply the Spot Slope annotation to a ramp but it isn't very useful because, while Revit does acknowledge the ramp element, when you attempt to tag it you see [no slope] (image using 2014).



Alfredo replied to my previous post with a tip in his comment:
    If you first place the spot slope tool on a floor and then move the slope annotation to a ramp, it works!

In this image I've dragged a slope annotation from a floor element over to a ramp element and it recognizes the ramp's slope!



Definitely quirky and subtle but at least it is possible after all. A word of caution, it will probably be necessary to check the slope value before printing, for example if Revit regenerates information because the ramp is altered. The tag could could start to report [no slope] again. Fwiw, in my casual testing so far it hasn't broken the slope value even after altering a ramp's parameters. Your mileage may vary...

Tuesday, February 12, 2013

Rotate with Component

This little setting is meant to force a tag to rotate with the tagged element, meaning to maintain the alignment.


The easiest example is beam or wall tags following their parent.


These categories respond to Rotate with Component:
Walls, Curtain Walls, Doors, Windows, Railings, Ramps, Stairs (Runs, Landings and Supports), Structural (Framing, Braces and Trusses), Property Boundary, Property Line Segments, Planting, and Parking.

These categories are immune to Rotate with Component:
Foundations, Floors, Ceilings, Roofs, Furniture, Furniture Systems, Casework, Generic Models, Structural Columns, Detail Components, Massing, Mass Floors, Curtain Panels, and Specialty Equipment.

Breaking loose from "Revity rules" the space, room and area tags are allowed to rotate more easily by choosing Vertical, Horizontal or Model, for each tag we use. The Model option allows us to use the Rotate tool to rotate them freely, which would be quite nice for any tag.

Architectural Columns, Shaft Openings remain immune to tagging by category at all.

That seems like a long list but that doesn't even factor in MEP components. Perhaps I'll tackle that another night.

Saturday, February 9, 2013

Leaders

I know people care a lot about where leaders start on blocks of text. Some want them to start at the first line, others at the bottom line and still others at the center of the text. Personally this has always felt like fussiness, focusing on trees and missing the forest. For eleven years I spent some of my time reading drawings to either bid on a project or to try to build something with them. I never got upset about such things. I WAS frustrated when the leader didn't point at the correct thing or fell short of "something" to point at. Where the leader started never confused me as long as it was clear which note it belonged to.

For my time and money, as long as they are consistent I'm satisfied. Unfortunately Revit isn't in this regard. Text has settings for leader positioning that keynote tags don't. That can lead to inconsistency and that's not good. Any annotation features that are available for text should be extended to other elements that display information that sure looks like text when looking at a printed sheet of paper. My 2.5 cents.

Friday, January 27, 2012

Occupancy Data Application

I've written about the workaround solution for documenting occupancy information in room tags in the past. I've even shared a sample project file based on the work I did for Scott Davis' past firm WLC Architects in 2005 (before he joined Autodesk). Until the API came along we were faced with a semi-inelegant solution that involved manual data entry and checking before plot day. Even after the API nobody really addressed this issue directly, till now...

Rahul Shah (blog: Revit Sticky Notes) works for Wood Bagot in the UK. He responded to a query at AUGI with a promise to write an application to push a calculated value to make Occupancy information taggable. He posted his solution today on his BLOG.

His written instructions on the blog post are:

    NOTE: In order to use this plugin you will have to add "Occupancy Load Factor (as area type)" and "Occupancy Load (as integer type)" shared parameters to your project file and assign them to Room object as Instance. Also, calculated occupany load value is not dynamically linked with other values so if you change room size or occupany load factor then you will have to rerun this tool to update occupancy load value. Please read the Readme.txt file contained in the zip file for more information.

You can DOWNLOAD IT NOW!

Tuesday, October 11, 2011

Elevation Tag Update Not Happening

Uh oh Spagetti O's... with the recent update I've noticed that the elevation annotation tags do not update when the their detail number values are changed. I don't recall this happening before the update but it's definitely going wrong now.


I find it necessary to change the annotation type to another or alter a setting in the family before Revit will "wake up" and change the tag to the new value. Boohoo...

Here's a quick VIDEO to demo the issue.