August 27, 2015

Revit 2016: Worksharing Monitor

The Worksharing Monitor extension for Revit® 2016 can now be downloaded by Subscribers from the Autodesk® Exchange.

Previously released extensions are listed here and here.

August 25, 2015

Autodesk Answer Days - Revit

Got a question about Revit® or Revit LT™ that you wish you could ask directly of the Autodesk team behind Revit? Mark Wednesday, October 7, 2015 on your calendar; from 6:00 am to 6:00 pm U.S. Pacific Time, you can ask your question as part of the second event in the Autodesk® Answer Days series.
Find out more about this event here.

August 14, 2015

Revit 2016: More Extensions Released

In addition to the four extensions noted here, Revit® subscribers can now access three additional extensions for the 2016 release, from the Autodesk Exchange:
  • Roombook Areabook Buildingbook 2016
  • Space Naming Utility
  • Autodesk Site Designer Extension for Revit

July 30, 2015

Windows 10 Support

Autodesk has posted this Autodesk® Knowledge Network article regarding Microsoft® Windows® 10 support. As of now, no products are officially supported. Versions from 2012 and earlier are no longer officially supported at all, so the article does not apply to them. They indicate that the article will be updated with additional information on Windows 10 compatibility as it is available, so check that article periodically.

Revit 2016: Extensions Released

Revit® Subscribers may now download the following extensions for the 2016 release from the Autodesk® Exchange:
  • Revit DB Link 2016
  • Batch Print 2016
  • Model Review 2016
  • eTransmit 2016

Version 16.2.0.0 of the IFC 2016 extension was also released today.

July 28, 2015

Dynamo Primer

If you have been interested in learning to use Dynamo, but were hoping for more documentation on using it, beyond the video tutorials available on the Dynamo Learn page, take a look at Dynamo Primer.

Version 1.0 features the first four of twelve planned chapters, including an introduction to visual programming and Dynamo, how to install Dynamo and a tour of the interface, the parts of a visual program and how to keep things organized and the building blocks of a program.

July 20, 2015

ACA/AMEP: Adding a Properties Ribbon Panel

The ACA.cuix and MEP.cuix that ship with AutoCAD® Architecture and AutoCAD® MEP do not contain a Properties ribbon panel. This was done intentionally, to encourage you to control the display of AEC objects via the Display System. (This is also why AEC objects do not have many of the basic object properties exponsed on the Design tab of the Properties palette.) I understand the thinking here, and agree that the Display System should be the first place you go to control how AEC objects look. But there are times when you just want to apply a linetype to an AEC object and really do not want to set an object-level or style-level display override for just that - particularly as that makes all of the other display settings an override, and will not be affected by changes made at the drawing default level (or style level, for object overrides). Do not get me started on "other" people who accidentally set the default object properties to something other than ByLayer; having to clean up that mess without being able to quickly see what properties are set on an object is frustrating. And while you can select one or more AEC objects, right click and choose Edit object display from the context menu and then use the General Properties tab of the Object Display dialog, some prefer the immediacy of a ribbon panel tool, especially those who have been users long enough to have used the control tools on the old properties toolbars.

The good news is that the ribbon controls are still defined in the ACA.cuix and MEP.cuix and that it is relatively easy to add whichever ones you like to a ribbon panel and add that panel to the ribbon tab of your choice. I made a Screencast to show just how easy it is. I do not have a good setup for adding narration to the Screencast (and I am not particularly skilled at talking and doing at the same time, either), so I will include some notes here on the process, in case it is difficult to see on the Screencast. You can click on the double diagonal arrow icon in the lower right corner of the embedded Screencast to go to full-screen mode, or you can hover over the Screencast and click on the title in the upper left corner to view the Screencast on the Screencast website. You will be able to see the command timeline on the Screencast website.
Notes:
  1. The examples shown in the video are just that, examples to demonstrate the techniques. Want a different arrangement, or want to add and/or remove commands and controls? Go for it - it is, after all, your customization.
  2. Creating a new ribbon panel requires using the Customize User Interface dialog. You can type CUI at the command prompt, or use the Workspace Switching tool on the Application Status Bar, and selecting Customize on the pop-up menu. The Screencast shows the latter method.
  3. I prefer, and recommend, that customizations be created in a separate customization file other than aca.cuix or mep.cuix, even if you eventually intend to add the customizations to those files. This makes it easier to back up your customizations and to move to later releases without having to drag the old main CUIX file along with you, possibly missing out on new features added to the new aca.cuix or mep.cuix. To do so, I use the Transfer tab to create a new customization file, which I then load as a partial customization file on the Customize tab, in the upper left pane.
  4. After loading the new partial customization file, the upper left pane will show just that file, and you will note that there are no commands shown in the lower left pane, because this CUIX is currently "empty".
  5. To get a list of commands and controls to add to our new file, change the setting of the upper left pane to show All Customization Files, using the drop-down list. Scroll down in the upper left pane, if necessary, and expand the following nodes: Partial Customization Files, your customization file name and Ribbon.
  6. Select the Panels node, right click and choose New Panel from the context menu. Give the panel a name, such as Properties.
  7. Right click on Row 1, and choose New Sub-Panel. Repeat this a second time, to add a second sub-panel. You could just add rows, and stack things up that way, but creating two sub-panels to handle two columns of controls builds in some flexibility, as you will see later in the Screencast.
  8. Right click on Sub-Panel 1 and select New Row to add a second row to the Sub-Panel. (Commands and Controls are always added to rows, so each panel and sub-panel will always start with one row when created.) Add a third row to this panel, and then add two additional rows to Sub-Panel 2.
  9. The framework is now in place for the first ribbon panel, and we need to add the Commands and/or Controls we want. In this example, all of the items are Controls, so the first thing to do is, in the lower left pane, change the selection in the drop-down list from All Commands Only to All Commands and Controls.
  10. Using the search feature in the lower left pane, search for the Command or Control you want to add. (You can scroll the list, but it will be easier and faster if you type in a key word or two to narrow the list.)
  11. When you find the item you want, such as the Object Color Gallery, left click, hold, and drag it to the upper left pane. I find that if I take the direct route, straight up, that the upper left pane will usually scroll away from the place I want to put the item, so I usually swing over to the right side and then up and back over to the upper left pane, entering it from its right side. There will occasionally still be some scrolling, but generally not enough to move the destination beyond the visible part.
  12. Hovering over the destination row in the upper left pane, release the left mouse button to add the control to that row. To see a preview of the results so far, select the panel name, or any part of its "structure," such as a row or sub-panel. The preview will show in the upper right pane.
  13. Repeat the previous three notes for each additional Command or Control you want to add to your panel. I added the Layer List Combo Box, Ribbon Combo Box - Linetypes, Ribbon Combo Box - Lineweight, Transparency Method Drop-down (changing the button style from Small Without Text to Small With Text and Transparency ribbon controls in the example). See below for additional observations on the Transparency Method Drop-down.
  14. Now that the panel is completed, it needs to be added to a ribbon tab, so that it can be displayed in the workspace. I chose to create a Test 01 panel in the newly created partial customization file. You may want to add it to an existing tab in another CUIX file that you have loaded. If you do so, note that this will copy the panel into that CUIX file, so any future changes would need to be made in both places. Right click on the Tabs node (under the Ribbon node) and choose New Tab from the context menu and then give the new tab a name.
  15. Left click and hold the Properties panel node under the Panels node, and drag it up to the destination tab. In this example case, there are no other panels on the Test 01 tab, but if there are panels on the tab where you are trying to place a panel, you can drag the mouse (with the left button still held down) to the desired position (indicated by a blue horizontal line) relative to the other panels where you want the new panel placed. When you have the right position, release the left mouse button to add the panel to the tab.
  16. If you created a new ribbon tab, select the tab to see its properties. If the Default Display property is set to Add to workspaces, when you load the partial customization file, this tab should be automatically added to all Workspaces in the main CUIX. This will not occur now, because we added the ribbon tab after we loaded the partial customization file.
  17. Select the OK button to close the Customize User Interface dialog. Note that the new ribbon tab did not appear in the interface. (If you added your panel to an existing tab that was already in the current Workspace, you can skip the next few steps.)
  18. Re-open the Customize User Interface dialog. Under the main customization file (ACA in this example, as I did the Screencast using AutoCAD Architecture 2016), in the upper left pane, expand the Workspaces node, if necessary, and select the current Workspace. In the upper right pane, expand the Ribbon Tabs node and note that the Test 01 tab is not on the list.
  19. Select the Customize Workspace button at the top of the upper right pane. Note that all the items in the upper right pane turn blue. This indicates that you are in the Workspace editing mode.
  20. In the upper left pane, find and expand the customization file that has the ribbon tab with your new panel. Expand the Ribbon node and then expand the Tabs node. Note the toggles in front of the items that can be added to a Workspace while you are in Workspace editing mode. In the Screencast, I clicked on the toggle in front of the Tabs node to add all of the tabs to the current Workspace, since there was only one tab in that customization file. If you have multiple tabs, and you do not want to add all of them to the current Workspace, use the toggles in front of each individual tab to control which ones are in the current Workspace.
  21. Back in the upper right panel, notice that the Ribbon Tabs node expanded itself and the newly added tab is shown, in black type. You can drag the tab to a different position in the listing if you do not want the new tab at the end; I chose to leave it at the end.
  22. Select the Done button in the upper left pane to ratify the changes made to the Workspace, and to exit the editing mode. Select the OK button to close the Customize User Interface dialog and to confirm the changes made. Give the program a few moments to process the change and display the new tab in the interface.
  23. Those who added the new panel to an existing ribbon tab can jump back in at this point. Select the tab with the new panel to make it current, and check out the Commands and Controls you added, to verify that they work as expected. You have successfully created a new panel, with properties-related controls, and had it displayed in your Workspace.
  24. The balance of the Screencast shows the creation of a second panel, this time with just one "column" of controls, placing those beyond the third row in the "Slideout". These can be seen by selecting the panel title (which will feature a downward pointing arrow icon to let you know there are more tools). It also shows the benefit of having used sub-panels in the first example, as we can copy those to the new panel to get that panel started.
  25. Reopen the Customize User Interface dialog, and, in the upper left pane, find and expand the node for the new partial customization file created for the Properties panel. Expand the Ribbon and Panels nodes.
  26. Expand the Properties panel node, and the Row 1 node beneath it.
  27. Create a new panel by right clicking on the Panels node and choosing New Panel. Provide a name for the panel; in the Screencast, I used Properties 2.
  28. Rather than start this version of a Properties panel from scratch, I chose to copy the sub-panels from the previously created one. Select Sub-Panel 1 under Properties (under Row 1), right click and select Copy from the context menu.
  29. Select Row 1 under the Properties 2 panel, right click and select Paste from the context menu. A copy of the panel will appear.
  30. Select the Properties 2 panel and add a new row. Notice that since Row 1's sub-panel fills all three rows that are always visbile, Row 2 appears under the SLIDEOUT item.
  31. Copy Sub-Panel 2 from the Properties panel, and paste it to Row 2 under the Properties 2 panel.
  32. I chose to add two additional rows to the sub-panel under Row 2, and add the Locked layer fading and Xref fading Controls to them.
  33. In order to test the new panel, I added it to the Test 01 ribbon tab, and then selected the OK button to ratify the changes and return to the drawing.
  34. The Properties 2 panel now appears on the Test 01 ribbon tab. The three Controls from the original Sub-Panel 1 appear on the panel, and the Properties 2 title bar has a downward-pointing arrow icon adjacent to the panel name.
  35. Selecting the panel title expands the panel and displays the balance of the Controls. Selecting the pin icon at the left side of the expanded panel title pins the panel in the expanded position. (Press again to un-pin the panel.)

I did not look at the vanilla AutoCAD Properties panel (ACAD.cuix) prior to creating this video. This version stacks all of the controls in one "column", but includes a large button for the Match Properties command, which could easily be added to the Properties 2 panel I created, by placing it on Row 1, before the Sub-Panel on that Row. I also failed to include the Plot Style Gallery Control. This could easily be added to Properties 2 by adding another row to the Row 2 Sub-Panel. A third Sub-Panel would be required to add another Control to the Properties panel, provided that you want all the controls to be visible all the time for that version. The vanilla AutoCAD version also includes a dialog launcher (indicated by the open arrow icon at the far right side of a panel title bar) for the Properties palette. This can be added to either of the panels created in the Screencast by dragging the Properties command (from the ACA or MEP customization files; choose the one with the Element ID of ID_Modify) up to and drop it on the Panel Dialog Box Launcher item. The image below shows the Properties and Properties 2 panels, with the Properties 2 panel pinned open. The Plot Style Gallery Control and the Properties dialog launcher have been added to the Properties 2 panel in the image below. The Match Properties tool was not added, as that is available on the ACA and AMEP Home ribbon tab, Modify panel.

You may have noticed that there were two Transparency Method Drop-down ribbon controls, and that I selected the one further down on the list, rather than the first one. I tried using both, and found that the "upper" tool would not allow me to set the drawing default transparency (with no object selected) and would not change the displayed value when the drawing default setting was changed, whereas the "lower" tool did both. I cannot promise that these two controls will always maintain that repsective relationship, but if you make certain that the current drawing default value is set to ByLayer before you open the Customize User Interface dialog to begin creating your panel, the "right" control will display the ByLayer icon (three stacked parallelograms, top one blue, other two white). The "wrong" control will show the "Use Current" icon (thin blue square around what looks like closely packed blue dots) and text, if you change the button type to Small With Text.

July 15, 2015

Revit: MEP Copy-Monitor with System Tab Off

We made an interesting discovery today in Revit 2014 ("one box"), and confirmed that it works the same way in Revit 2015 as well. We had set up our architectural deployments to have all of the MEP System Tab tools turned off. The idea was to simplify the interface, and since we were not expecting architects to place any of the objects on that tab, it seemed like a good idea to turn it off.

We had an architectural user who was attempting to copy-monitor lighting fixtures from a linked electrical model report that while the link could be selected, once selected, the lighting fixtures in that link could not be copied. When two of us in the Design Technology support group opened the exact same model, we were able to copy-monitor the lighting fixtures without any problem. We did notice that the architectural user was missing the Coordination Settings tool on the Coordinate panel of the Collaborate ribbon tab and both the Coordination Settings and Batch Copy tools were missing from the Tools tab of the Copy/Monitor contextual ribbon tab, and thought perhaps there was a problem with the installation. We tried repairing the installation and deleting the local profile from the registry, forcing Revit to recreate it. Neither worked. Eventually my co-worker realized that one thing that was different on our machines was that we had all of the MEP System Tab tools turned on (since we have to support all disciplines), and that if we turned off all of the MEP System Tab tools, then we also lost those tools and could not copy-monitor lighting fixtures, either.

Ribbon tabs, with Systems tab enabled:

Ribbon tabs, with Systems tab disabled:

Something to keep in mind if you have the "one box" version of Revit and want architects to be able to copy-monitor MEP objects. Note that so long as at least one of the MEP Systems Tab tool sets was enabled, then the light fixtures could be copied; it did not have to be the electrical tools.

June 29, 2015

ACA: Classification Definitions, Applies To and Tagging

Classification Definitions have been around since Autodesk® Architectural Desktop 2004. One use for them is to act as an additional filter for the AEC objects that can be included in a Schedule Table; unlike layer filters, Classification Definition filters can be built right into the Schedule Table Style, on the Applies To tab. You can also use them on Property Set Definitions to limit the objects to which you can attach a Property Set.

I have been using them to control what objects are seen in Schedule Tables for quite some time now. A recent thread in the AutoCAD® Architecture General Discussion Group had me wondering if they could be used to prevent a Schedule Tag from being placed on an item, theorizing that if a Classification Definition was set up such that the Property Sets referenced by the Schedule Tag did not apply to a particular object, perhaps I would be unable to tag that object.

To test my hypothesis, in the 2016 release, I created a Classification Definition called Schedule that applies to all objects, with two Classifications: Schedule and No Schedule.

I then applied this Classification Definition to the Property Set Definitions referenced by the out-of-the-box US Imperial Door Tag (non-project), classifying each as Schedule.

Finally, I applied the Classification Definition to the Door Styles, on the Classifications tab of each style. In my test file, the Hinged - Single, Hinged - Double and Sliding - Double - Full Lite Door Styles were set to Schedule, and the Cased Opening Door Style was set to No Schedule.

I placed a few instances of the Doors (two of the Cased Opening style, one each of the others). On the Extended Data tab of the Properties palette, I observed that the Add Property Sets button was grayed out for the Cased Opening Doors, as it should be, since the DoorObjects Property Set does not apply due to the classification being set to No Schedule for those Doors. I edited the Cased Opening Door Style, and, on the General Tab, selected the Property Sets button and manually removed the FrameStyles, DoorStyles and ManufacturerStyles Property Sets (which were attached in the source file). Once I did so, the Add Property Sets remained grayed out, due to the classification.

At this point, I used the out-of-the-box US Imperial Door Tag tool (Document tool palette group, Tags palette) and attempted to tag each of the doors. As you can see in the image below, I was not prevented from tagging the Cased Opening Doors, even though none of the referenced Property Sets could be applied to those Doors. I did get a Command line message stating: Note: Not all properties apply to selected object. The DoorObjects Property Set was not applied to these Doors, and the Schedule Tag displayed the default value assigned to the attribute definition in the tag's view block. Surprisingly, the style-based Property Sets were attached to the Cased Opening Door Style, even though those did not apply, either.
In the image above, I turned on the display of the Anchor Extended Tag to Entity component, and set its color to green. The green arcs extending from the Schedule Tag insertion point to the Door origin point are these anchor components, verifying that the Tags on the Cased Opening Doors are in fact anchored. I also repeated this experiment, with a custom Schedule Tag that only referenced one object-based Property Set, but the Cased Opening Doors still received the tag, even though the referenced Property Set was not attached. Similar results were obtained in the 2015 release as well.

So, using a Classification filter to limit the objects to which Property Set Definitions apply will not prevent a Schedule Tag that references properties in such a Property Set Definition from being anchored, and will even add any style-based Property Sets referenced by the Schedule Tag. Object-based Property Sets will not be attached, and attributes that are set up to display the value of object-based properties will only show the default attribute value.

May 28, 2015

Revit: 2015 R2 UR8 Available (Subscription Customers)

Update Release 8 for Autodesk® Revit® 2015 R2 was released yesterday. Subscription customers who have installed the Revit 2015 R2 mid-year update can apply this update if they currently have Update Release 7 for R2 installed, or R2 without any updates. See the full details in the Read Me. A list of the improvements can be found here.

It appears that the same download also works for the "Non-R2" Revit 2015.