As I am preparing to teach another session on Revit Railings I noticed another small quirk. Again in this example I am using railing supports to act as balusters, a great option when dealing with glass panel.
In this image I have a support to look like gasketing material as well as glass supports, these are associated to the U track handrail. This allows for the glass seam to be unpinned and moved to any desired location.
The quirk arises when the handrail has a value for a fillet radius, even though the Default Join is set to Miter. If the support is unpinned and moved it will move along the radius as if the value were set to Fillet no Miter.
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.
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.
Tagged with: Bug?
One of the minor new features for Revit 2017 was the nuance of how pinning a tag works. In previous releases if a tag had been pinned it kept an individual from moving the tag but it moved along with the element it tagged. In 2017 when a tag is pinned it still keeps an individual from moving it, however it will stay in it’s given location as the element being tagged moves. Note: The leader only moves with the tagged component if the Leader is set to Attached End and not Free End.
This is a very welcomed new feature, I have been an advocate of detailing using tags in lieu of text but was always frustrated that if a detail item changed the tagged would move and have to be realigned. No more wasting time with this menial task
The new features that we received as part of Revit 2017 for View Range were actually part of 2016 R2, with one exception. In 2017 the factory gave us a 2 key shortcut (VR) to activate it. This is, maybe I should say was, one of my favorite new little features for this release. However I found a bug when using the shortcut instead of accessing it through the properties dialog. If you use VR to access the dialog you Must use apply dialog for it to work clicking OK wont accept changes. Aaron Maller and I also discovered that you can access the view range via VR even when there is a view template assigned. Simply applying the view template to the view wont correct the problem you must make a change in the view template and it will then overwrite the settings. These quirks forced me to no longer say this is one of my favorite small enhancements.
During my last Revit Radio session I was had made the comment that Material Assests can’t be purged out of a family. The discussion arose as I had found a bug in Revit 2017 that if you attempt to delete all the materials out of a family then Revit was just crashing. It didn’t do this on all families but specifically on View Title families, both OOTB and custom versions. Aaron Maller wrote in explaining me a work around to remove the material assest. This mornign I was gong to blog about his work around but wanted to first attempt to figure out why the family was crashing in the first place. My first troubleshooting thought was to purge the family and to my surprise we can now Purge material assests (This is huge for us content generating geeks). Not only that but it will allow us to purge all materials out of a family, it doesn’t leave default.
FYI purging the family of materials didn’t make it crash but deleting the material did. I stopped looking since this is a better option anyway.