December 27, 2011

ACA - Multiple Cut Planes in One Sheet

You may have a situation where you would like to show the same plan area more than one time on the same sheet, with the same Display Configuration, but with two different cut planes. For example, you might have a door with sidelights and transom, and you might want to show a plan view cut at the usual cut plane height, through the door, along with a plan view cut through the transom.
This can be done, but you need to remember that the cut plane height is set in the Display Configuration. Recent releases of ACA have had a control on the Drawing Window Status bar that lets you change the value of the cut plane without having to edit the current Display Configuration through the Display Manager.
Someone unfamiliar with the way the cut plane is set in the Display Configuration might think that you could set up two viewports of the same plan area
and make model space active in one and simply change the cut plane for that viewport. Because both viewports use the same Display Configuration (High Detail in the example shown), using the Cut Plane Control to change the cut plane height in one viewport
changes the cut plane in both viewports.

Changing the cut plane back to 3'-6" will, of course, change it back in both viewports. In order to have different global cut planes for the two plans, you will need to have two separate Display Configurations. This is easily done in the Display Manager:
  1. With model space in one of the plan viewports active, on the Manage ribbon tab, on the Style & Display panel, choose the Display Manager tool.
  2. In the left pane, select the Configurations node under the current drawing.
  3. In the right pane, right click on the current Display Configuration, which will appear in bold type, and choose Copy from the context menu.
  4. In the right pane, right click in the white area below the list of Configurations and choose Paste from the context menu.
  5. In the left pane, expand the Configurations node and select the copied Display Configuration - in the expample, High Detail (2).
  6. In the right pane, on the General tab, rename the Display Configuration with a more meaningful name, if desired.
  7. On the Cut Plane tab, set the desired Cut Height for the cut plane of the new Display Configuration.
  8. Click OK in the Display Manager to accept the changes and return to the drawing.
  9. Set the new Display Configuration current in the plan viewport where you want the new cut plane applied.
Because the two viewports now use different Display Configurations, the global cut planes can be different.

December 12, 2011

Multi-Sheet Plans and Revisions in Revit

Many projects have floor plans that end up being too large to fit on one Sheet. Revit makes splitting a single Level onto two or more Sheets fairly easy by setting up a Dependent View for each sector of the overall floor plan. Revit even includes a Matchline tool to make it easy to designate the extents that each Dependent View documents. Each Dependent View is then placed on its own Sheet.

When choosing where to break up your plan, and how far beyond the matchline each Dependent View should depict (model and annotation), keep in mind that Revit will automagically add a revision to the Sheet if a View on that Sheet contains the full extents of a revision cloud in that View. If you only place revision clouds on the Sheet itself, you have no worries. But for plan revisions, I prefer to place the revision clouds in the View, so there is no need to worry that the View will move on the Sheet without the revision cloud also moving.

If you show large areas of the model beyond the matchline or if the annotation crop extends well beyond the matchline, you are increasing the odds that a small cloud drawn on the View of one Sheet, but near the shared matchline, will also fall completely within the adjacent View's annotation area. If you are issuing both Sheets, that is not a big deal. But if you are only issuing the Sheet that actually has the revision, you would not want the revision to show up on the adjacent Sheet. Keeping things as tight to the matchline as possible will minimize the chance that this will occur.

Sometimes the way the project is laid out makes it difficult to establish a clean matchline to which you can closely crop the Dependent Views. Other times, a revision is relatively small and right next to the matchline. Here are a couple of ways to avoid having the revision show up on the adjacent Sheet.

  1. If you have additional revisions in the same View, you can combine the cloud of the revision near the matchline with one that is farther away, and beyond the annotation area of the adjacent Sheet's View.A revision cloud does not have to consist of a single, closed loop of revision arcs. It can be open, and can also have multiple, unconnected runs of arcs. If any part of the graphics of a revision cloud is beyond the annotation area of a View, it will not show in that View, and will not result in a revision line on the Sheet on which that View is placed.
  2. If you do not have additional revisions, you can edit the revision cloud to include a very small arc that does not fall in the annotation area of the adjacent View, in a discreet location in the View with the revision. If the graphics this generates disturbs you just as much as having a revision line on a Sheet that was not issued, and you turn off the display of revision clouds from previous revisions when making the next revision, you can wait until after you have printed the drawings to be issued, and then go back and add the small segment just before marking the revision as issued and turning off the display of the revision clouds for that revision.

November 25, 2011

Rounding and Column Totals

If you have a Schedule Table column that displays real-number values that are rounded by the applied Property Data Format and you also display a total for the column, you may find that the total displayed does not equal the sum of the individual numbers displayed. This can happen because ACA uses the real-number values before the format is applied when calculating the total, and then applies the Property Data Format to the result. So if there is not a balance between round up amounts and round down amounts, the total can differ from the sum of the displayed, rounded numbers.

If this bothers you (it bothers me), you can make use of the same techniques discussed in this blog article, where the task was to get rows with apparently similar values to collapse into one row in a Schedule Table with a Quantity column. The rows were not collapsing because even though the displayed, rounded numbers were the same, ACA was using the actual values, before applying the Property Data Format, to determine whether or not the values were the same.

In response to an inquiry in the Autodesk ACA Discussion Group, I posted a sample file (AutoCAD 2010 format) demonstrating several ways a Formula property can be used to make the source value the same as the rounded value, so that the total for the column will be the sum of the displayed values (and, if you have a Quantity column, that rows with identical displayed values will collapse). The image below shows the test Schedule Table I set up to show how the various properties in the SpaceObjectAreas Property Set display. The file was created using the Aec Model (Metric Stb).dwt template and the AutoCAD Architecture (US Metric) profile.

The columns in that Schedule Table display two properties from the out-of-the-box SpaceObjects Property Set Definition: Name and Number. The remaining columns display properties from a custom Property Set Definition called SpaceObjectAreas. Here is a description of these properties, and the effect that the way they are set up and formatted has on the values displayed and the column total.
  • BaseAreaUnformatted: This property, displayed in the column titled "UNFORMATTED", uses the Automatic Base Area property of Spaces to display the area of the space. A custom Property Data Format called Standard-8 has been applied to this property and to the column in the Schedule Table. This is a copy of the out-of-the-box Standard Property Data Format, with the real-number precision changed to eight decimal places and trailing zero supression turned off. There is also no prefix or suffix applied to the value, so when referenced by formula properties, the value will be treated as a numeric value. The areas of the test spaces do not generate any rounding issues when totalled, as they do not require more than the eight digits displayed.
  • BaseArea: This property, displayed in the column titled "AREA FORMAT", also uses the Automatic Base Area property of Spaces. It has the out-of-the-box Area Property Data Format applied to it, which in its metric version displays real numbers using an Area unit type, units of square meters, decimal unit format with two-decimal-place precision and a suffix of " M2". Other than Space 101, the area of each space is rounded up when displaying the value to two decimal places. The total is rounded based on the total of the raw values (see the Unformatted column total), and results in a column total that is 0.04 M2 less than the total of the displayed numbers.
  • BaseAreaPassThrough: This property, displayed in the column titled "PASS THROUGH", is a Formula property. It takes the BaseArea property and uses the feature added in ACA 2007 that allows you to assign a different Property Data Format for the purposes of the Formula property. In the example file, a custom Property Data Format called Standard-2 is assigned, which is a copy of the out-of-the-box Standard Property Data Format, with the real-number precision changed to two decimal places and trailing zero suppression turned off. The Formula takes the value of BaseArea (rounded to two decimal places by the Standard-2 Property Data Format), makes it a string, converts that to a double-precision real number and passes it through as the final value. Since we want to have a total value for the column, using the default Area Property Data Format would not work, since this includes a suffix of " M2", which would cause the value to be interpreted as a string and therefore not provide a numeric value that can be totaled. Because the Property Data Format has trailing zero suppression turned off, the CDbl conversion is not required, but because I know this value should always be a number, I put it in, should the Property Set ever get copied to a file that already has a Property Data Format called Standard-2 that has trailing zero supression turned on. In that case, if the BaseArea value was a whole number, the result would be interpreted as an integer in ACA and the real-number formatting would not be applied.
    Because the Formula property is generating the "raw" values with the area values rounded to two decimal places, the column total reflects the total of the actual values displayed, rather than the rounded sum of the source areas of the actual Spaces.
  • BaseAreaRounded_01: This Formula propery is displayed in the column titled "FORMULA ROUNDING 0.01". It accomplishes the exact same effect as the pass-through Formula, but uses the VBScript Round function to do so. CDbl( Round( [BaseArea], 2 ) ) It also assigns a different Property Data Format to the BaseArea property (Standard-8, in this case). In the example file, I could have simply referenced the BaseAreaUnformatted property without reassigning the Property Data Format in the Formula property, but I used the BaseArea property with the reassigned Property Data Format to demonstrate that you do not need to set up a separate, unformatted version of an automatic property if you are using the 2007 or later version. I included the unformatted property here so that I could display the area values to eight decimal places in the Schedule Table, so you could see the effects that the various formatting/rounding options had on the raw numbers. As with the previous formula, the column total matches the sum of the displayed values, because the raw value of the Formula property is the same as the displayed value. If you can achieve the precision and rounding you want with a Property Data Format, then you can use either the pass-through or the Round function method. As you will see in the final example, the Round function (combined with other mathematical operations) can do things that the Property Data Format cannot do, in which case the Round function would be the only choice.
  • BaseAreaRounded_05: As seen in the column titled "FORMULA ROUNDING 0.05", this Formula property rounds the area value to the nearest 0.05, and since the raw values are the actual rounded values, the column total is correct for the displayed values. CDbl( Round( ( [BaseArea] / 0.05 ), 0 ) * 0.05 ) The formula achieves the desired rounding by starting with the BaseArea property value, with the Standard-8 Property Data Format applied. It divides that value by 0.05, rounds the result to the nearest whole number and finally multiplies that result by 0.05 to achieve the desired result. I am not certain how often something like that might be used in a metric file (you could use the same technique to round to the nearest half-square meter, just change the "0.05" to "0.5"), but there are occasions, when using imperial units, that rounding room areas to the nearest 25 or 50 square feet is used as a means of not implying too much precision in early test fits.
In all of the Formula properties, the Area Property Data Format is applied to the property (and the column in the Schedule Table) to get the " M2" suffix applied to the value calcuated by the formula. Also remember that when specifying a property reference in a Formula property, you have to select the referenced property from the Insert Property Definitions box in the lower left corner of the Formula Property Definition dialog; you can not simply type in the name of the property, enclosed in square brackets. If you are interested in reading more about rounding in Formula properties or some of the other techniques discussed above, you may want to check out some of these earlier blog articles:
07/09/2005 - Unformatted Properties and Numeric Precision
08/31/2005 - Rounding Up Property Data Values
08/31/2005 - Rounding Revisited
09/03/2005 - Rounding Redux
09/15/2005 - Rounding to Death
05/01/2006 - Using Property Data Formats to Force Real Number Interpretation
04/15/2007 - ACA 2008/ADT 2007: Setting a Different Property Data Format in a Formula Property
06/16/2007 - Rounded Values and the Quantity Column

October 19, 2011

Revit Key Plans - More Detail

It has come to my attention that my Revit Key Plans article can be hard to follow, particularly if you are not familiar with some of the concepts or procedures used. It was not intended to be a step-by-step tutorial, so I am providing this post to fill in some of the gaps and make it easier to follow along. This tutorial was prepared using Revit Architecture 2011; interface elements in other versions or releases may vary.
  1. Start a new Generic Annotation Family. From the Application Menu - Big "R" in the upper left corner - choose New > Family. In the New Family - Select Template File dialog, navigate to the folder where you or your firm have placed the Annotation Family Templates, and choose Generic Annotation.rft.
  2. Determine how your Key Plan needs to function. I do not want to have to place the Key Plan family separately on each Sheet; I want it to be part of the title block family so that it need only be placed once, and will always be in the exact same position on each Sheet. I also do not want to set up a title block family type for each Key Plan option. I do not want to show a Key Plan on every sheet in the set, so I will need a Key Plan type that shows nothing at all. There will be plans that show the overall building, as well as larger scale plans showing only one of the two wings. I want a solid fill to show in the Key Plan indicating the area that is being shown on that drawing. I also want to be able to show the Key Plan outline graphics with no fill.
  3. Create the graphics for your Key Plan. You are going to have to figure this one out on your own. There does not appear to be a way to make use of any sort of graphics in a project file and transfer them to a family file. You can scale graphics inside the family, so you could draw the building outline in the family to scale and then scale it down to fit the area available in your title block for your Key Plan. As shown below, I created scaled-down outlines of the two wings of my building and then added text to identify the wings, filled regions with solid black fill for each wing, and the north arrow graphics. Keep in mind that the intersection of the two reference planes will be the initial insertion point for your Key Plan family and position your graphics accordingly.
  4. In order to be able to control the display of the various graphic components, I created three type-based Yes/No parameters in the Family Types dialog. The first is for the outline, text and north arrow graphics that will be on whenever a Key Plan is to be displayed, but off when no Key Plan is to be shown. I called this parameter Outline.
    1. On the Modify ribbon tab, on the Properties panel, select the Family Types tool.
    2. In the Family Types dialog, click on the Add button in the Parameters area at the lower right side.
    3. In the Parameter Properties dialog, in the Parameter Data area, enter the name for the parameter, change the Type of Parameter to Yes/No, select a parameter category under which to group the parameter - I used Graphics and select the Type toggle. Click OK to add the parameter and dismiss the Parameter Properties dialog.
    4. In the Family Types dialog, I cleared the check mark in the value column, so that the current condition will be to not display the graphics.
      Repeat the previous sub-steps to add the remaining two parameters, SectorA and SectorB, for the filled regions associated with each building section. Other than the Name, the parameter attributes are the same as those for the Outline parameter. Uncheck the toggle in the value column for these as well.
  5. With the Family Types dialog still open, create a family type for each display condition you want for your Key Plan, and turn on the appropriate visibility parameters for each type. In the example, I created five: No Key Plan (all parameters unchecked), Outline Only (only Outline parameter checked), Sector A (only Outline and SectorA checked), Sector B (only Outline and SectorB checked) and Sectors A-B (all three checked).
    1. In the Family Types dialog, select the New button in the Family Types area at the upper right.
    2. In the Name dialog, enter the name for the Family Type in the Name edit box and click OK to register the entry and dismiss the dialog.
    3. In the Family Types dialog, set the appropriate value (checked or unchecked) for the visibility parameters for this type. (For the No Key Plan type, leaving all unchecked is correct.)
    4. Repeat the preceding sub-steps to add the remaining Family Types needed for your Key Plan, setting the appropriate values for each type.
  6. Select all of the graphic elements in your Key Plan that are to be associated with one of the parameters (in my example, I started with the Outline parameter, to which everything but the filled regions will be assigned). On the Properties palette, look for the Visible parameter, under the Graphics parameter group. If you do not see it, you likely selected an object, such as a Reference Plane or a Group, which does not have this parameter. Deselect these items. Select the button at the right side of the Visible parameter line. (In versions prior to 2011, do this from the Instance Properties dialog for the selected items.)
  7. In the Associate Family Parameter dialog, choose the appropriate Yes/No parameter (Outline, for the graphics selected on the first pass) and then click OK.
  8. Notice on the Properties palette, the Visible parameter and its value are now grayed out and the button at the right side displays an equals sign ("="). This indicates that the Visible parameter has been linked to another parameter, and cannot be edited directly. You can click on the button to verify (or edit) the chosen parameter.
  9. Repeat the previous three steps to assign the SectorA and SectorB Yes/No parameters to the visibility of the associated graphics (in my example, the filled regions). Note: If you have any Detail Groups within your Key Plan Graphics, as I did to collect the various parts of the north arrow graphics, you will need to edit the group to be able to assign the appropriate visibility parameters to the nested graphics within the Detail Group.
  10. At this point, your Key Plan family is complete. Save the family.
  11. Open the Title Block family into which you will place the Key Plan. Load your Key Plan family into the title block family. (One way, with the Key Plan family open and current, on any of the standard ribbon tabs, on the Family Editor panel, choose the Load into Project tool. If you have multiple potential target files, choose only your Title Block family in the dialog presented.)
  12. Your Title Block family should be set current and you should be prompted to insert an instance of the Key Plan family. If you are not seeing any "ghost" graphics of your Key Plan family near your cursor, check the Properties palette to see what the default family type is. Mine was set to No Key Plan, which has no visible graphics, so I got no ghost graphics to aid in initial placement. I changed it to Sectors A-B so that I could see all of the graphics.
  13. Adjust the location of your Key Plan family in your title block, if necessary.
  14. Select the placed instance of the Key Plan.
  15. On the Options Bar, click on the down arrow at the right of the Label drop-down and choose <Add parameter...> from the list.
  16. In the Parameter Properties dialog, in the Parameter Data area, give the new parameter a name; I used Key Plan. Choose a Group for the parameter; I used Graphics once again. Make this parameter an Instance type. This is crucial, as doing so will allow each instance of your title block to have a different family type displayed, which is what you want.
  17. On the Home ribbon tab, on the Properties panel, click the Family Types tool.
  18. You should see the Key Plan (or whatever your called yours) Label listed as a parameter under the Graphics group (or whatever group you chose). Set the value for the Label to your desired default Key Plan family type. This is the value that newly created (or newly updated) title block instances will use. I chose to set mine to No Key Plan. (If your Title Block family has several family types, you will want to do this for each Family Type. This only sets the default value; each instance can be changed to show a different Key Plan type because we made the Label an instance parameter. This avoids the need to create a separate Title Block family type for each Key Plan type.)
  19. Save your Title Block family file.
  20. Load or reload your Title Block family into a project. On a Sheet that has an instance of this Title Block family, select the instance.
  21. On the Properties palette, notice that, under the Graphics parameter group (or whatever parameter group you assigned to the Label applied to the Key Plan instance in your Title Block family), there is now a parameter called Key Plan, the value of which is a drop-down list of the family types you created in your Key Plan family. Choose the type you want to see for that particular Sheet.

October 11, 2011

ACA Openings with "Style"

The Opening object in ACA does not have styles. So, unlike Doors, Windows and many other ACA object types, you can not control the display of Openings with overrides at the style level, nor can you attach style-based Property Sets. Given the relatively limited display components associated with Openings,
not having styles may not be a problem for you. But if you have ever wanted to show different types of Openings in different ways, and wished that you could control these displays at the style level, rather than having to make the changes on each individual Opening, then you may be interested to know that it is possible use a Door to emulate an Opening, and thereby gain the benefits of having an Opening-like object that has styles. Another advantage of doing this is that you can assign a Profile to a Door Style acting as an "opening", allowing you to have non-rectangular "openings".

Before diving into the specifics, it is worth noting some of the limitations. If you make use of the Fill Types in the plan display of Openings, and you use a hatch pattern other than Solid Fill for the fill, you will likely be disappointed, as the use of a unit block to mimic the Fill Types will almost always result in a distortion of the hatch pattern since the Width and Depth dimensions will likely result in unequal scaling of the block. Another minor limitation is that, unlike when selecting the Triangle A or Triangle B Fill Types, the display of Cross Line B will not automatically be suppressed when turning on the display of the custom block for Triangle A or Triangle B. The four Fill Types are also not mutually exclusive - you could accidentally have more than one turned on at a time. If none of the above are deal breakers for you, then read on to see what is needed to set up a Door Style to enable "openings" with style.

Custom Blocks
In order to duplicate the components available in an Opening object, you will need to create eight "unit" blocks, one for each component. A description of unit blocks can be found in this blog post. The graphics of each unit block fit within a one-unit by one-unit area; the eight unit blocks can be seen in the image below. The insertion point is in the lower left corner of each block. The linework or hatch in each block is drawn on Layer 0, with Color, Linetype, Plot style (if you use named plot styles) and Lineweight set to ByBlock, so that the Display System will be able to contol all of these properties.
The four blocks on the left side provide the graphics for the equivalent of the Length Lines, Width Lines, Cross Line A and Cross Line B components of an Opening. The four blocks on the right side provide the equivalent of the four Fill (Hatch) Types: Cross A, Cross B, Triangle A and Triangle B, provided that you set the Hatch component to use a Solid hatch.

Door Style as Opening
With the custom blocks defined, you can now create the Door Style that will be used as a style-based "opening". The following steps will show how to do that, matching the out-of-the-box Display settings for Openings; if your office has customized those settings, you will likely want to use those instead. On the Manage ribbon tab, on the Style & Display panel, click the Style Manager tool to open the Style Manager. Expand the Architectural Objects node (under the drawing in which the unit blocks are defined) and select the Door Styles node. In the right pane, right click on the Standard Door Style and choose Copy from the context menu, and then right click over a blank area on the right pane and choose Paste to create a copy. In the left pane, select the new copy (mine was called Standard (2)) and choose the General tab. Rename the style in accordance with your firm's naming convention. (I used Door as Opening for my example style, and provided a description for the style.)
On the Dimensions tab, in the Frame area in the upper right, set the width to 0" and make certain that the Auto-Adjust to Width of Wall toggle is checked. Simply turning off the Frame component is not enough - you need to set the Width of the Frame component to 0 here so that the Width set on the Door (as Opening) will also be the width of the actual opening created in the Wall.
On the Design Rules tab, change the Door Type to Pass Through. If you are looking to create a non-rectangular opening, you would assign the profile on this tab.
You can set up standard sizes on the Standard Sizes tab, if you like. On the Display Properties tab, click on the toggle in the Style Override column for the Plan Display Representation to set and edit a style-level override.
The Display Properties dialog will open. On the Layer/Color/Linetype tab, turn off the display of all components by clicking on all yellow lightbulbs in the Visible column to turn them off.
This will suppress the display of the standard Door components in a plan view. The custom blocks will now be added to provide the equivalent of the components for Openings. On the Other tab of the Display Properties dialog, click on the Add button.
In the Custom Block dialog, do the following:
  1. Click the Select Block button and choose a block definition to add as a custom display block in the Select a Block dialog. In the example, the Dr as Opng - Length Lines block is selected. This is the Length Lines block illustrated above. Click OK to register your change - the block name will be displayed to the right of the Select Block button.
  2. Choose the conditions under which the custom block will display (Always, When Intersectiong Cut Plane, When Above Cut Plane, When Below Cut Plane). In a brief experiment, I found that Opening object components, when "on", appear to display regardless of whether the Opening is cut by the cut plane, above the cut plane or below the cut plane, so I left all of my custom blocks set to Always display. You may choose to do differently, if it meets your needs.
  3. In the Scale to Fit area, enable the scaling toggles for Width and Depth. This will cause our unit block to be scaled to match the user specified Width for the Door object and the width of the partition (because we enabled the Auto-Adjust to Width of Wall toggle on the Dimensions tab of the style). Since the block only contains 2D (plan) graphics, we do not need to scale it for Height. Choosing both Width and Depth scaling will disable the Lock XY Ratio toggle, which we would not want to use here.
  4. Clear all of the Mirror In toggles (none should be selected when first adding a block; verify that none are selected).
  5. Set the Insertion Point to X: Left, Y: Front and Z: Bottom, if it is not already set that way. This coordinates with the insertion point of the unit block being in the lower left corner of the block's extents.
  6. No Insertion Offset is required; verify all values are set to 0.
  7. The only choice of Component for a Door is Frame Component. Verify it is set to Outside, which should be the default value.
Click OK in the Custom Block dialog to register your changes. TIP: The preview display on the right side of the Custom Block dialog does not always display the block properly when first added. If you want to use the preview to be certain that your settings are correct, click OK, and then, back on the Other tab of the Display Properties dialog, select the block you added in the list and click the Edit button. It should now be correctly displayed for the settings you have chosen.
Repeat the process above to add the blocks for the Width Lines, Cross Line A, Cross Line B, Cross A, Cross B, Triangle A and Triangle B custom display blocks. I used the same settings for each block.
Return to the Layer/Color/Linetype tab. In addition to the out-of-the-box components previously shown here, you will find that each of your custom blocks is now listed as a display component.
This is where you will control the visibility and display parameters of the custom blocks. You will not have a Fill type tab, as an Opening object does; instead, you will need to control the display of each fill option individually, here. You also will not have a Hatching tab, so, as noted at the beginning of this post, you will not be able to select a hatching type - solid fill is "hard coded" into the custom display block of each fill type. In order to match the out-of-the-box display for Openings, you will need to turn off all of the custom display blocks except for the Length Lines block, and set the display parameters as shown in the image below.
You are, of course, free to use your own settings. Click OK in the Display Properties dialog to register the changes made to the Door as Opening Door Style. In the Style Manager, click OK to save the changes to the drawing file (and then save the drawing file), or click Apply if you want to continue editing styles in the Style Manager. To test your new style, you can either make duplicates the style and then modify the style-level override display settings in each to turn on different sets of components, to verify that each works as expected, or you can place multiple instances of your Door as Opening "with style" and then apply object-level overrides to test each component's display. Ultimately, you will want to create multiple styles, since the whole point of creating this Door Style was to be able to control the display of "openings" at the style level. To complete the emulation of an Opening object, you will need to create a Tool palette tool for each Door as Opening Door Style and that uses the OPENING Layer Key as an override, so that the Door object created get placed on the same layer as an Opening object (by default).

If you use the Schedule Feature to create a Door Schedule for your "real" Doors and do not want these "opening Doors" showing up in the Schedule Table, you can apply a Layer Filter to your Door Schedule or you can set up and apply a Classification Definition to exclude the opening Door Styles from your Schedule Table. Refer to this blog article for more information on filtering the objects in a Schedule Table.

You can find a sample file that contains the style used to generate the screen captures shown here, along with some copied styles with different custom blocks turned on, in this thread in the AutoCAD Architecture Content Discussion Group.

October 08, 2011

ACA 2012 Service Pack 1 Released

Apparently Autodesk has decided to go back to calling them Service Packs, rather than Updates. Service Pack 1 for AutoCAD Architecture 2012 is now available - download it from here.

Be certain to read the README for installation instructions. According to the README, Service Pack 1 restores the former ARRAY command functionality, in a new command called ARRAYCLASSIC. There is also a new System Variable, SNAPGRIDLEGACY: set this to 1 to have the cursor always snap to the grid (legacy snap behavior); set it to 0 to have it snap to the grid only when AutoCAD has prompted for point input.

The following ACA defects have been addressed:

Drawing Manager
  • Selecting a sheet with a long name may cause unexpected behavior in AutoCAD Architecture.
  • Opening a project with a large number of files in a 64-bit machine may cause AutoCAD Architecture to crash.
  • Space containment does not work on a 64-bit operating system.
Multi-View Block
  • Exporting multi-view blocks to AutoCAD may result in an incorrect size.
  • Some AEC ARX files are loaded when running AutoCAD Architecture with an AutoCAD profile.
  • Renovation function fails when you add a door or window object during renovation mode.
  • Sometimes the renovation toggle remains enabled even after exiting the renovation mode.
  • Building geometry may change after you activate and then disable the live section.
  • Roof or roof cap solid hatch might be displayed in section incompletely.
  • Some merged space area are calculated incorrectly.
  • When the unit area is inconsistent with its unit length, the calculated space area might be inaccurate.
Structural Member
  • Adjusting column grid can cause beams to lose connection with the columns.
  • Adding tags for doors on multiple reference copies may cause unexpected behavior in AutoCAD Architecture.
  • REPOSITIONALONG command does not work for doors and windows.
  • Running the JOIN command on two connected walls may cause unexpected behavior in AutoCAD Architecture.
  • When you offset a wall using another wall with the same direction as the reference, the offset wall may be created in the opposite direction.
  • The Below Cut Plan display component of doors or window may not display.

The following AutoCAD defects have been addressed:

3D Navigation Tools
  • 3DConnexion settings are not being remembered after changes are made.
  • 3Dconnexion device will not cancel the current command.
3D Surface Modeling
  • With dynamic input off dragging the height handle of an extruded line will not always stretch by the value and direction of the drag.
  • AutoCAD may become unstable when rebuilding a helix to a spline where the selection was not dropped.
Annotation Scaling
  • AutoCAD may become unstable while attempting to load a DCL file with errors from a long file name.
  • Tooltip does not appear when Additional tool tip string is set in “AcEdInputPointMonitor::monitorInput”.
  • API fix: This fix will respect the custom color, line pattern and line weight when selecting the entities including external reference.
  • Autoloader fails when SeriesMax parameter set to linked.
  • Autoloader loads partial CUI but may not display it when the bundle is removed and reinstalled.
  • When platform="AutoCAD*", bundles will be load on ACAD and Vertical.
  • Using Autoloader to add custom CUI files that contain WPF Custom Controls will not work as it needs a registry entry.
  • AutoCAD may become unstable while snapping to blocks containing OLE objects.
  • Editing attribute text in EATTEDIT dialog sometimes results in a fatal error.
  • When a drawing is saved from within the Block Editor, the entire content of the drawing is sometimes lost and replaced with the content of the block being edited.
  • Sometimes there is a delay while trying to modify blocks containing a Block Table Parameter.
  • AutoCAD becomes unstable when entering the block editor, attempting to edit a dynamic block which has geometry on a locked layer.
  • Sometimes the BEDIT toolbar does not get hidden after exiting block editor.
  • You may receive an error at the command line after enabling a WinTab driver and the tablet will not function.
Display Drivers
  • Integrated chipsets are unable to return available video memory correctly.
  • Arcs and circles viewed on edge appear as a single line. This changes 2D DWF/DWFx drivers to plot them as a single line, rather than a polyline.
  • AutoCAD may become unstable when using the "UNDO" command on drawings that are 2 gigabyte or larger.
  • Ordinate dimensions in paper space are not correctly reflecting the distance from paper space UCS.
  • AutoCAD may become unstable while closing a drawing after etransmitting it using the COM API.
  • Autodesk Exchange may display a non-subscription link after updating to a subscription serial number.
  • User login IDs that contained special characters like “@” could not log in to online services.
Express Tools
  • AutoCAD may become unstable when using the NCOPY command.
  • Overkill may delete polylines incorrectly when working with reversed polylines.
  • Overkill may not work well when there is an arc segment in between 2 line segments.
  • AutoCAD may become unstable when using the “separate hatch” option.
  • Multi frame QuickBird Tiff image files may not display expected colors.
  • When trying to insert an Adobe Photoshop PSD file it was not visible in the file filter list.
  • AutoCAD may become unstable when inserting an AdobePhotoshop PSD file.
  • Changing layer colors of layers beginning with non-alphanumeric characters may result in other layers changing colors.
  • The layer state Ribbon control does not honor the apply properties viewport overrides.
  • AutoCAD may become unstable when drawings with multileaders are saved to older versions.
  • AutoCAD may become unstable when editing polylines.
  • NCOPY may fail to copy objects contained in blocks that were inserted into paper space.
  • Mtext Paragraph spacing value cannot be edited once a value is set.
  • True Type (TTF) font text or mtext is blurry, bold, and distorted when the viewport is non-orthogonal because XY values are not exactly zero.
OLE (Object Linking & Embedding)
  • AutoCAD may become unstable when copying from an Excel file back to AutoCAD.
  • Cannot open drawing files from file Explorer if the drawing contains a "'%'" in the file name.
  • AutoCAD may stop responding when saving and or opening drawings with Symantec Norton 360 Version 5 installed on your system.
  • You will be unable to open drawings created using a non-Autodesk product when using the Open() API.
  • AutoCAD may become unstable when selecting the grid in some drawings.
  • AutoCAD may become unstable after editing MTEXT in a viewport and when exiting the program.
Parametric Drawing
  • Area is wrong when coincident constraints are applied to entities.
PDF Export
  • AutoCAD may become unstable when using PDF Export on files that contain MS Mincho font.
PDF Underlay
  • AutoCAD may become unstable when unloading a PDF underlay.
  • AutoCAD may become unstable when an undefined PDF underlay is unloaded.
  • AutoCAD may become unstable when plotting drawings that include “MS Mincho” to PDF.
  • Drawings containing many layers may become slower with each pan and zoom operation when the ribbon is active. Performance improvement in 64bit COM APIs.
  • You may experience data loss when sending multiple plots to Xerox printers.
  • AutoCAD may become unstable when selecting plot preview.
  • AutoCAD may become unstable when using the purge command.
  • The linetype preview may be missing from the linetype dropdown in Ribbon Properties panel when opening drawings from the Application Menu.
  • Ribbon Combo Box text eight may be empty when using "TEXTEDIT" on multiple dimensions.
  • With Snap enabled, the cursor does not move to snap intervals.
  • Turning SNAPGRIDLEGACY ON will restore the old Snap behavior of the cursor when no command is active.
  • Restores legacy SNAP behavior during certain LISP-based selection commands.
Sheet Set Manager
  • Sheet List Table Context menu in Sheet Set Manager (SSM) is missing some menu items.
  • Cell style is grayed out when picking inside any cell.
  • The data link menu is grayed out after inserting a data link in a table.
UI Enhancements
  • AutoCAD may become unstable attempting to edit a polyline vertices Pedit tangent.
  • AutoCAD may become unstable in group selection where the group contains a box.
  • When objects are on locked layers you are able to nudge them.
  • AutoCAD may become unstable when interacting with the ViewCube while grip editing.
  • When right click menus are disabled, selection or crossing right click actions are incorrect.
Visual Basic for Application
  • AcFocusCtrl cannot be inserted in a VBA form.
Visual Lisp
  • Attribute dialog will be displayed when inserting a block with attributes based on the setvar ATTDIA value.
Visual Styles
  • AutoCAD may become unstable when using osnap in a 2d hide view.
External Reference
  • AutoCAD may become unstable when interacting between the open dialog and the XREF manager.
  • AutoCAD may become unstable when zooming over the XY indicator in Layout.

September 02, 2011

Unit Blocks

A unit block is an AutoCAD block definition in which all of the graphics are drawn within the confines of a one-unit by one-unit area (or, for 3D blocks, a one-unit by one-unit by one-unit volume). The block can then be inserted with X- and Y-scale factors (or X-, Y- and Z- scale factors in the case of a 3D block) equal to the actual size of that instance. For example, HVAC supply diffusers are often represented by a rectangle with opposite corners connected by diagonal lines

You could set up a number of blocks for all of the different sizes you would need (or, in more recent versions, master the creation of dynamic blocks). Or, you can create a single, unit block and then set the X- and Y- scale values to get the size needed for a particular instance.

The unit block concept remains useful, even with the advent of dynamic blocks, as ACA objects that use blocks (such as for the view blocks of Multi-View Blocks or for custom display blocks added to many object types) often can take advantage of the unit block concept, and dynamic blocks will not remain dynamic when nested within an ACA object.

August 30, 2011

Early AU Registration for AU Members

"Early" registration for AU 2011 is now open for AU members. Regular registration starts September 7. Register at the AU website.