Tag Archives: Bug?

Revit Railing Support Bug

Leave a reply

I have been teaching and using the hack to use railing supports in leiu of baluster or to use them for gates etc.  Yesterday a client told be about an issue with Railing Supports, they do not abide by phasing graphic overrides.  In cases where the supports are simple brackets (as shown below this probably isn’t that big of a deal.

Railing Support Phasing Issue 0

However when you are utilizing support for balusters or for gates (as shown in the two images below) this becomes a big issue.  This has been reported to Autodesk and I was able to reproduce the issue in both Revit 2017 & 2016, I didn’t test it in older versions of Revit.

Railing Support Phasing Issue 1

Railing Support Phasing Issue 2

Generic Annotation Bug

Leave a reply

While working with a family to resemble a Level head for detailing I noticed a quirk when dealing with Generic Annotations and justified text.  I had nested in a Generic Annotation family that only had a right justified label, this was nested into another generic annotation family.  What I discovered is right justified labels in a generic annotation family will end up moving the control point if there isn’t a line in the family.  This is odd because when the label is center or left justified the insertion point remains constant.  I traced this issue back to Revit 2012, can’t believe I hadn’t discovered this issue previously.

Generic_Annotaion_Quirk

To resolve this situation a line needs to be added to the family, I personally just added an invisible line on the vertical reference plane, such that it was easier to find if the label was blank.

 

 

New Exciting Release Slated for Late April

14 Replies

Dezi and I haven’t been blogging too much lately because we have been involved in this beta.  It has meant a lot of appointments with professionals, anticipation and excitement.

This release will come in a compact package but will continue to grow in the upcoming years.  Will probably become expensive in future years but we are hoping the product will be worth the costs.

This release does not use the ribbon interface however has an interactive touch interface which is user friendly and pleasant on the eyes and will make you want to keep playing with it.  The 3 dimensional representation seems lifelike.

Some of the features that will be available include super purge, hopefully the auto-sleep feature will work but has been known to be a bit glitchy.  It is said to have an artificial intelligence-like learning capability that is supposed to advance the more it is used.    Many other features will keep us up at night until we figure them out.    User customizable carrying cases can be added as well as  many accessories, but they must be purchased separately and can vary considerable in price.

The product is a direct result from nested family capabilities yet the final naming of the product is still yet to be decided and if you would like to weigh in feel free to add comments to this blog.  If you want to see a sneak peak of the box shot click the link below to see a preview.

BOX SHOT

 

2013 Stair and Handrail

2 Replies

While setting up a new template for one of my clients I noticed an interesting issue (I would call this a bug) with handrails and precast stairs.

In Revit 2013 one of the small changes to stairs was the “End With Riser” (as well as “Begin With Riser”) value was changed to an instance based value.  When creating precast stairs this value is unchecked by default.  The issue is not with the stair itself rather with the handrail that is created.  When this value is unchecked the handrail does not remain parallel with the run of the stair.

Once the “End with Riser” value is checked the rail becomes parallel again.

So how do we resolve this issue if we need the run to not end with a riser.  Edit the path of the rail and make the lines align with the top tread of the stair, then select the sketch line at the landing and make the value for it to be flat.

I have submitted this to Autodesk and hopefully we will get a good answer back.  Or at least have the issue resolved in a service pack.

Plan View Types Part 3

Leave a reply

I have posted a few times now about the Revit 2013 new Plan View Types.  I really like this feature, however I found another nuance that everyone should be aware of and hopefully will change with future service packs or releases. 

At first I loved the fact that when levels were created it allowed the Plan Views to all have the same name if they were under different view types.  I still like this, however it seems to be causing issues.

Notice in the image below I have Level 1 and Level 2 views in each plan view type. This is great now if you rename a level or view the capability to rename all of them still exist.

 

Now simply move a view from one category to another. 

 

If that view name already exists then it doesn’t add another number at the end, it simply add up to the next available number. Which seems totally non_Revit like in my opinion why not a (2) at the end?

 I wanted to make everyone aware of this issue. I have already been discussing this with clients to see how they want to impliment and deal with this issue.

Small nuance that could be frustrating however not devastating to a project.  If you want to apply a view template via another view and all of the plan views have the same name how do you choose?  As you can see there are numerous Level 1 views.