Walk and Fly are available only in perspective views.

Walk and Fly are available only in perspective views.

All of a sudden, this dialog box started popping up again while performing a 3DOrbit inside AutoCAD Architecture.

Walk-n-Fly
Walk-n-Fly

After checking this thread for a solution and finding none, I offered the following:

Add the following to your section in your FixedProfile.aws

 <HideableDialog id=”VMToolsUI.WalkFlyToPerspectiveView” title=”Walk and Fly – Change to Perspective View” category=”Navigation” application=”” result=”1001″><Preview><TaskDialog Source=”/AcTaskDialogs;component/TaskDialogs.xaml” Id=”VMToolsUI.WalkFlyToPerspectiveView” xmlns=”clr-namespace:Autodesk.Windows;assembly=AdWindows”></TaskDialog></Preview></HideableDialog>

Make sure you do this while AutoCAD is not running, or the fixedprofile.aws file will get overwritten when you do close AutoCAD.

New versions of IFC Exporter and UI available

Are you running the IFC Exporter for Revit 2014 or Revit 2015?  Did you know new versions were released yesterday?  If not, consider yourself “in the know” now.  To really get up to speed, continue reading.

Download links:

IFC Exporter for Revit 2014 (v3.13):

IFC Export Alternate UI for Revit 2014 (v2.13.0.1)

IFC for Revit 2015 (v15.3.0.1):

Learn more – read below


 

What’s new for IFC for Revit 2015 v15.3.0.1:
New Export Functionality:

  • Allow IfcLongName to override the “LongName” attribute for levels.
  • Rooms can now be exported from 3D views even when exporting only elements visible in view.  If the option is chosen to export rooms, then all rooms inside or bordering the bounding box of the section box will be exported.  If the section box isn’t active, all rooms will be exported.
  • Work in progress: users can now opt to export files according to the IFC4 Reference View MVD.  This will result in IFC4 files that use IfcTriangulatedFaceSet instead of IfcFacetedBRep, resulting in significantly smaller IFC files.  There are still some cases where IfcFacetedBReps show up in these files, and there are some cases where the tessellation isn’t optimized for the reference view; this will be improved in upcoming releases.

Export Bug Fixes:

  • Fix export of files with a project north value different than true north that would cause a slight shift in elevation.
  • Fix export of some IfcCurveBoundedPlanes with more outer loops than inner loops.
  • Fix the location of some assemblies on export.
  • Fix the base quantities export for walls and columns when they are split by level.
  • Improve splitting of walls in some cases when they are split by level on export.
  • Improved the export of some entities with extruded surface geometry with clippings and openings where some clippings and openings were not being exported.
  • Properly scale the volume of columns when base quantities are exported for non-imperial projects.
  • Update the French resources file that prevented IFC export from working on computers with a French OS.

New Import Functionality:

  • Add ElevationWithFlooring and InteriorOrExteriorSpace/PredefinedType for IfcSpaces.
  • Add IfcContainedInHost parameter for doors and windows to contain the name of the hosting wall.
  • Add IfcElevation parameter for Levels.
  • Add IfcElementAssembly parameter for elements inside assemblies.
  • Add IfcSystem parameter for elements inside systems.
  • Add material thickness to the IfcMaterial parameter for elements who have an associated IfcMaterialLayerSetUsage.
  • Better handing of nameless grid lines.
  • Heal some curves with short curve segments, small gaps between segments, and vertices that are too close and better log file error reporting of the above problems.
  • IFC4: Import IfcTriangulatedFaceSets, generally created for the IFC4 Reference View MVD.
  • Import Box (i.e., the bounding box) representation for elements that have it, but only if they have no Body representation or it contains no visible geometry.
  • Import IfcAssemblies.
  • Import Construction Type and Operation Type for IfcDoorStyles.
  • Import IfcPorts.
  • Import IfcSystems.
  • Import IfcZones.

Import Bug Fixes:

  • Accept “Profile” as an alternate name for “FootPrint” when reading in entity representations.
  • Force some entities to have a default name if Revit requires them to, even if there is no name in the IFC file.
  • Improve processing of faceted BReps with gaps and short edges.
  • Improve processing of walls and slabs whose geometry is defined by IfcMaterialLayerSetUsage.
  • Properly scale IfcCompositeCurveSegment trim parameter for non-imperial files.
  • Use gray, not black, as the default material color for materials with no color assigned.

 

What’s new for IFC Exporter for Revit 2014 v3.13:
New Export Functionality:

  • Allow IfcLongName to override the “LongName” attribute for levels.
  • Rooms can now be exported from 3D views even when exporting only elements visible in view.  If the option is chosen to export rooms, then all rooms inside or bordering the bounding box of the section box will be exported.  If the section box isn’t active, all rooms will be exported.
  • Work in progress: users can now opt to export files according to the IFC4 Reference View MVD.  This will result in IFC4 files that use IfcTriangulatedFaceSet instead of IfcFacetedBRep, resulting in significantly smaller IFC files.  There are still some cases where IfcFacetedBReps show up in these files, and there are some cases where the tessellation isn’t optimized for the reference view; this will be improved in upcoming releases,

Export Bug Fixes:

  • Fix export of files with a project north value different than true north that would cause a slight shift in elevation.
  • Fix export of some IfcCurveBoundedPlanes with more outer loops than inner loops.
  • Fix the location of some assemblies on export.
  • Fix the base quantities export for walls and columns when they are split by level.
  • Improve splitting of walls in some cases when they are split by level on export.
  • Improved the export of some entities with extruded surface geometry with clippings and openings where some clippings and openings were not being exported.
  • Properly scale the volume of columns when base quantities are exported for non-imperial projects.

 

What’s new for IFC Export Alternate UI for Revit 2014 v2.13.0.1:
New Export Functionality:

  • Rooms can now be exported from 3D views even when exporting only elements visible in view.  If the option is chosen to export rooms, then all rooms inside or bordering the bounding box of the section box will be exported.  If the section box isn’t active, all rooms will be exported.
  • Work in progress: users can now opt to export files according to the IFC4 Reference View MVD.  This will result in IFC4 files that use IfcTriangulatedFaceSet instead of IfcFacetedBRep, resulting in significantly smaller IFC files.  There are still some cases where IfcFacetedBReps show up in these files, and there are some cases where the tessellation isn’t optimized for the reference view; this will be improved in upcoming releases.

Export Bug Fixes:

  • Update the French resources file that prevented IFC export from working on computers with a French OS.

Download links (repeat):

IFC Exporter for Revit 2014 (v3.13):

IFC Export Alternate UI for Revit 2014 (v2.13.0.1)

IFC for Revit 2015 (v15.3.0.1):

 

 

Update to Chainlink Fence (Railing)

Update to Chainlink Fence (Railing)

I’ve updated the Chainlink as Railing example to utilize the latest railing styles and modified the construction to allow for displaying in a site view with x’s as the post.  I’ve also added a material that renders as chain link.  So now you get the easy creation method of the rail object, with surface patterns, render material, and you can control visibility in your site view to show as a traditional linework.  Since its a railing, it will also allow curves.Here is a site view of the “fence” in action:

Here is an elevation view in realistic mode:

Here is an elevation “hidden line” view showing the surface pattern:

Here is a rendered view:

Here is how it is constructed.

Continuous Chain Link Fence_2014

 

Revit Buildchecker Version 9 for 2015 Products

I updated this tool last year, but didn’t upload it to the blog.
 RBCv9
Sorry folks, here is a copy that works with products 2008 through 2015.
ACA: Automating workstation counts per squarefoot

ACA: Automating workstation counts per squarefoot

We have been successfully using ACA rooms to meet program needs for one of our primary clients. Their requirements are based on a specific square footage formula for determining how many workstations should exist within certain room types.  Recently they added additional room types beyond “Office” that also require workstation counts.  In addition to the increase in room types, they also increased the workstation counts per square foot.  On top of the those requirements, there is always a need in this business to override an automated value based on room geometry or other constraints, so the automation had to be flexible.  The current workflow for overriding the count involved deleting the default room tag and replacing it with an alternate tag containing an attribute. Because I had to revisit the formulas, I took an opportunity to streamline the workflow while adjusting the formulas.  I reduced the workflow for overrides from 12 clicks to 5 and eliminated the alternate room tag in the process.The original room tag had values being constructed via a formula, in a custom property set definition (psd) field called WS_Count.  It was set up to always display the rooms square foot value by reading the gross area field from the RoomObjects psd.  A relatively simple formula was used to check the space name and when “office” was in the name, the WS_Count value was concatenated to include a workstation count.  The tag looks like this in operation:

As you can see from the image above using the same tag for both spaces results in a workstation count being displayed in office types and just the square footage for other type of rooms.  This is accomplished with some simple statements inside the object based psd.  Note the Space name is standardized and controlled by pulling from a list and is style based.  To create something similar, you could introduce the following function in a psd field.

The logic within the above sequence first checks to see if the list based style name contains the word “office” if it does not, it will skip all the down to the Else statement and simply return a string containing the “GrossArea” automatic property of the room object which is concatenated with a space and the letters “SF”.  If the space type contains the word “office”, then the value of the “GrossArea” automatic property is checked from smallest to largest using a “less than” comparison.
This tag was working well for this clients projects, but based on the previous mentioned changes, I introduced two new fields into the psd (WS_Override & WS_Detect) to eliminate the non coordinated overrides and to reduce the multi-view block count by 1. Because I wanted the value of the workstation count to always get calculated, I added a simple “less-than” function to calculate the count in the new property field titled: WS_Detect as shown below.

This function checks the string value from the property WS_Count to see if “WS” is found, meaning that the room type required a workstation count, and checks the new property WS_Override to see if its value is defaulted to 0 representing no override.  If both prove true, then the square footage is calculated based on the square footage program requirements set by the client using a similar “less-than” approach.  If either value is false then the manual integer based property value of WS_Override is used.

With the two new properties in place, anytime an override is needed because of space geometry, pilasters, or other obstructions that might require a deviation from the program, the designer simply places a positive value in the WS_Override property of the space. With the calculated value being tracked in a separate property, the original WS_Count property formula was modified as follows:

The original space type check was modified using the boolean “Or” to check for “Office” as well as the new space types that also get workstation counts.  If no workstation count is required, then the formula skips to the Else statement and simply presents the Square footage value as before.  If a workstation count is required, then the logic begins to check for a positive value in the WS_Override property.  When a positive value is found, the formula concatenates the square foot value with the workstation count from the WS_Override property.  If no override is in place, the original program based workstation count is used by concatenating the square foot value with the WS_Detect property.

The room tag multiview block was created using the following psd properties within an attributed block as shown below.  This block is used as a display block within the multi view block.

Client_SPACESTYLES:Client_DESIGN_TYPE
Client_SPACESTYLES:LENGTH x Client_SPACESTYLES:WIDTH
Client_ROOMOBJECTS:WS_COUNT

Note: in the above attributed block definition the middle line contains a simple text object with the letter “x” to allow the length and width size to be displayed.  I set the Length as right justified and the width to be left justified.  The first and third lines are middle center justified.

To give visual feedback to the designer as they are placing the spaces, I added a display theme to color the spaces based on workstation count.  I also added a room based schedule to display the workstation counts and provide a running total.  This schedule is set to automatically add new spaces and to search within blocks so that it is always up to date.  This setup is estimated to save approximately 10 – 15 minutes per project every time the plan is created or changed.  This is projected to save the company more than 80 man hours per year. It also eliminates counting errors and inaccuracies which may be introduced through human error.  The image below shows the original space layout on the left with the new display theme based layout and legend displayed on the right.

An image of the schedule that maintains tracking of Workstation Count is shown below.

The image below shows the settings used for the display theme.

Finally, the formula used in the Workstation Count Schedule is provided for reference.

The above formula checks the psd property WS_Count for the string “WS” indicating a workstation count is being calculated based on the space type.  If the formula doesn’t find the string then the workstation count is set to a value of zero. If it finds the string “WS”, then the value of the property WS_Override is checked. If it is greater than zero, its value is used directly, if not, then the value of WS_Count property is parsed using the split function.  The split is based on a space value and the third element of the resulting array is returned, which is the workstation count.

Let me know if this helps in your work. Here is a tip, you can cut and paste formulas like these shown in this blog post into the editor in ACA, but you’ll need to highlight any values found within square brackets and double click to replace the property set data using the interface. I frequently do this when working with a long formula.  I’ll copy it out of a working example into notepad, add the necessary logic, and then paste back into the formula editor. When you paste it back in, look for any bracketed properties that do not display the dark background.  You’ll need to replace those by highlighting them and then double clicking on the property from the object list below the code area. Use the sample results area as a check.

When the sample results area displays a proper sample value you are ready to use it.  Below you’ll see an example of the property formula editor in both working and non-working order.  Remember if you see the formula in the sample results area, you still have some replacements to make.

Flush your Undo – AutoCAD

Flush your Undo – AutoCAD

As I roll out the 2014 versions of Building Design Premium, a designer sent me the following warning message from AutoCAD:

Warning! The undo file length is 1569321556 bytes.  Undo will be automatically disabled at 1750000000 bytes to prevent overflow…

Although I’m not sure what an UNDO Overflow would look like, rather than soil the carpets with all those abandoned and rolled back activities, I decided to investigate further.  I recommended that the designer saveas to ensure no data was lost and then began an investigation.

The solution:

  1. Use Saveas to write the file back to the harddrive or network location in case of a potential fatal error.
  2. Clear out the temp folder – Use %temp% in the file dialog and delete files found.
  3. Flush the Undo register – Type Undo – C – All

For more info refer to this Autodesk technical reference.