Monday, March 29, 2010

Video's up and running

For those who are subscribed, etc. The videos are up and running again via YouTube.

Sunday, March 28, 2010

Screencast Bandwidth Limitations

Hey all,

Just as a warning, apparently I have a limit on bandwidth transfer for my Screencast account, and given the length, size and (apparent popularity) I'm at risk of maxing out (which means you won't get to watch my videos).

So dealing with YouTube was not so bad. One more video uploading, but the rest are there and "live".

YouTube was out, as they won't take SWF files, same with Vimeo. I'm investigating options, but if anyone has suggestions throw up a comment. If anyone has some spare server space and bandwidth, I'll take that too.

Thanks to Kyle's tip on a conversion program, we're back in business. Videos uploaded to YouTube. I may have to give up on Jing do to what seems to be slightly poor conversion quality from SWF to FLV to YouTube. But, it should be good enough that you get the idea.

Cheers!

Revit 2011: Custom Elevation Tags

So, this feature was not on my personal list of requests, but obviously it is/was on someone's given its persistent presence on AUGI wishlists (along with site tools*). I have to say, it will be nice to be able to create Elevation tags that are smaller, and will fit better into small interior spaces.

These new tags are pretty straight forward. You have to create a "body" which can hold as many pointers as you like. The pointers allow for the creation of elevation views. There are some limitations as you will see in the video, but overall the implementation is really good (and I wish it would come to section heads too). There is a new property for text and labels that controls the relative rotation of the text to the symbolic geometry. Lastly, the same problem that has plagued section heads, plagues elevation tags too, where masking regions will mask symbolic lines. Thus you either must create many separate masking regions to get all your required edges, or skip the masking regions, which can be a problem in complicated spaces or when floor patterns/finishes are visible in views. See the video for a fairly quick demonstration of the new feature(s).



* A brief note on Side tools, a bug in 2010 when a sloped pad was adjacent to a level pad resulted in a teeny tiny sliver of "site" extending up past both pads has reportedly been fixed in 2011.

Friday, March 26, 2010

Revit 2011: Reporting Parameters

2011 is here! As I post, I'm participating in Autodesk AEC's blogger day event. Much like David Light, I've had to sit on most of this information for 9 months+ now (and its been soooo hard!), I can also say that I expect to see more! Maybe not tomorrow, not even next month, but soon!

There are a growing number of posts in general about the new features in 2011, so I decided to focus on something near and dear to my heart (supposedly my case-study provided good reasons to move forward with this feature) Reporting Parameters.

Reporting Parameters are a hugely powerful feature (as mentioned by other posters). So I thought that I would do some movies to demo how they work, and what they do. I've got four movies lined up, each builds on the next in complication.

First, the basics. Creating a reporting parameter, and showing what it can do. Note, a reporting parameter does not have to be shared, but combining reporting parameters with shared parameters, means you can get that information into a schedule (or tag).



Next up, a little bit of what you can and can't do with a reporting parameter in a family. For instance you can use dimensions from "Host Geometry" to drive elements in families. However, reporting parameters driven by non-host geometry can only report the information, you can't use the value in a formula. Note, you also cannot directly drive geometry with a reporting parameter, you should set another parameter equal to the Reporting parameter in the formula column.



Third a creative application of the reporting parameter in Curtain Panel. Note that when a curtain panel is loaded into a project you can already schedule Width & Height, so if you create reporting parameters to do the same thing you should probably name them differently (particularly if they're shared).



Are the idea juices cooking yet? Here is one more example, also making use of the new "Adaptive Component". Note that these components can only be placed in a Conceptual Mass family (think of the mass family as a "wrapper" but you can change the category of the Adaptive Component, as well as linking parameters and geometry, to give the user in project full control of the Adaptive component (within reason, there are still some limitations).