I replied to a thread at AUGI regarding the Eccentricity parameter of a Wall Footing. They observed that Revit seemed to ignore their input and didn't understand what it was meant to do. In this case the width of the footing was less than the value they entered.
The parameter is intended to shift the footing over, from interior to the exterior face of the wall. The footing starts out centered on the wall above.
The maximum eccentricity is equal to (Footing Width/2)-(Wall Thickness/2).
The interior wall surface can be aligned (flush) with the interior face of the footing but not further, creating any overhang of the wall, which seems logical to me. A picture might help?
It is a common practice to add a name to the reference planes we create. If it isn't common where you work then it ought to be. The name helps give a hint to anyone that works in the model that this reference plane is more important than those without a name. It can also help understand what it is for, why it was made.
There are some who make the effort to clear out reference planes that are not named periodically, just another of any number of model/housekeeping chores. I've even seen Dynamo scripts intended for this task.
If you're using Ideate's Explorer you'll find it easy to see a summary of all the reference planes in the model. In the following image I've created two reference planes, one with a name and another without a name.
Notice that there are five (5) reference planes listed though. As it happens, when the Edit Profile concept is used on a wall four reference planes are created and internally applied against the sketch of the wall. They are only visible to us while editing the wall's profile sketch. We can't see these reference planes in the regular user interface, it only becomes very apparent with their Explorer tool.
It is also possible for us to create reference planes while creating any sketch based element, like a floor or stair for example. These reference planes are only visible to us while editing their related sketch.
The reference planes associated with a wall's edited profile can't be deleted via IDEATE Explorer. It can delete them when we've created our own within a wall's profile and other sketch based elements.
Attempting to clean up these unnamed reference planes might also be an issue if you're writing your own code or Dynamo script to delete them. We can/could add names to these internal reference planes (wall profile) but I don't think that's a task that worth the effort. Something to keep in mind.
Yesterday while trading messages with a friend we discussed my previous post about columns disappearing. He suspected it might explain the issue he was observing. After looking more closely it turned out that it doesn't. In his situation the structural columns were modeled the full height of the building and Join Geometry was used on walls, that passed through (overlapped) the columns, at each floor (level). The result: at some levels no column appeared while at others they do.
It was necessary to pull the walls back so they stop at the surface of the columns. Join Geometry allowed for the desired appearance and the columns reappeared at the other levels where they were missing earlier.
Dialog stretchiness has been an ongoing long standing user wish for all dialogs. Daniel wrote to me hoping that I'd echo his complaint about the Filter dialog. Yes you can stretch it but the frames remain less so. The Filter name frame does add a scroll bar at the bottom when a filter name exceeds the width of the frame, which does not increase in size when the overall host dialog stretches out. Ideally we'd be able to stretch/adjust individual sections of such dialog boxes. If memory serves that is dependent upon which GUI tools are being used to generate the dialog. If that tool set doesn't do it then...we don't get it...without a custom entity.
Daniel was writing about Revit 2019. Even when you scroll over to the right completely a filter with a long name gets truncated and you can't read all of the name.
I note that in Revit 2020 a tooltip will appear that displays the full name while the frame does the same truncating even when it has been scrolled completely to the right.
Naturally, we can avoid it if we can use Filter names that are not very long, an easy fix...there's that word again - easy. Easier said than done...it seems.
When we create a Callout within a plan view we can choose between Floor plan and Detail. A structural column that uses a negative offset won't show up when a wall exists in the same location when a Detail view type is used. It works fine in a Floor plan view type.
Here are some example images. The first one is showing the negative offset used. If the offset is zero then there is no graphical issue, the column shows up.
This images shows both callouts in the overall floor plan, Detail on the left and Floor on the right.
This is the Floor Plan Callout, column shows up as expected.
This is the Detail Callout, no column is visible.
This is the same Detail Callout but my cursor is hovering over the column and Revit sees it, highlights it despite not being visible. The wall is masking the column.
This is the same Detail Callout but the view is changed to use Wireframe and the column appears.
It boils down to the negative offset applied to the column. The graphics hierarchy does not respect the full height of the column and the wall element is drawn over the structural column. We can also get around the issue if we remove the option: Show family pre-cut in plan views.
This is an update to a much earlier post after getting a couple comments on that thread. These are three companies I'm familiar with that are providing solutions that contend with sharing details between projects and multiple model projects.
It’s been about a week now where some of us can’t post/reply at the forum. I guess I’ll give up trying at this point. I can only spend so much time replying only to have the forum crash. Hopefully they’ll figure it out eventually. Maybe someone can tell me if/when that happens? Good luck!
In Revit 2018.3.2.7 I am seeing and getting reports that keynote legends are not updating to show the current state of keynote tags visible in views. The existing workaround to force a refresh by turning on/off the Annotation Crop Boundary works but is entirely impractical to expect a team to open every sheet and do that task for each and every view on a sheet.
This past Knowledge Network post seems relevant. A portion of the text at that article suggests...
Workaround: There are a few ways you could work around this behavior, and the best method will vary depending on the model geometry and number of affected tags. Here are a few options:
Temporary fixes (these will restore the display keynote tags, but future view changes will clear them again): Temporarily adjust the location of the Cut Plane so that is above the affected elements (this will restore the value to the tags) and then restore the original cut plane location. Note: Some customers have noted that for views with dependent views, this process is required:
Open the parent view and adjust the cut plane upward.
open all sheets containing dependent views belonging to this parent view to refresh the keynote tags.
move the cut plane back to its original position in the parent view.
(Note: this may not work for some elements such as Duct; in that case, see the Non-temporary fix below.) Recreate the affected tags manually.
Non-temporary fix (This will prevent future changes to the view from clearing the keynote tag): Adjust view or elements so that the cut plane is above the affected elements. (This could be done with a Plan Region.)
I have been trying to carve out a little time here and there to fix the paths to downloads I've shared in the past. As of now the most requested stuff is fixed, the egress family and railing files. If you try to download something and hit a page not found warning, drop a comment in the post to bring it to my attention and I'll make it a priority. Thanks for being patient - The mGmT...