I need some help with this. I have a feeling that it's possibly a corrupted family or file, but for some reason whenever I make interior elevations they always create the views to be the thickness of the floor slab plus an inch or so. This is makes interior elevations very difficult to make. Has anyone ever had this issue or found a way to fix this?
Solved! Go to Solution.
Solved by loboarch. Go to Solution.
Not understanding. Are you referring to the crop boundary?
Are you saying that you don't like the default crop and having to always adjust it?
@Anonymous wrote:
the crop boundary starts at what the image shows.
"Image"? What image are you referring to.
You do know that the crop boundary is adjustable after-the-fact; right? In other words, it ain't fixed.
Revit will automatically find the wall, floor, and ceiling to form the crop boundary. There might be some floor or ceiling above your current level.
So this is partially the issue. The finish floor type was not on in the views that we were creating the elevations on, but it still would create the view wrong. I removed all instances of 1 finish floor types and that fixed the issue, but once we redraw any finish floor again it brings back the issue. I even tested everything out to see what would fix it. I changed the finish floor type, I changed the level it is hosted from, and even created a new one from an existing. Any new finish floor that is drawn creates this issue so it looks like the model has some sort of bug in it.
Sounds like you are spending more time trying to "fix" than it would take to just manually drag the crop an inch. Maybe I'm not understanding the issue.
Well, the team already went the manual route. I attached the image I posted in my original post to this response. Literally all interior elevations started out at roughly 5" from top to bottom no matter what level they were drawn from. It was getting to be very tedious to resize the 70+ interior elevations they were placing. They ended up doing it manually, but I was trying to find out if something was being missed that I completely forgot about for the process.
@Anonymous wrote:
So this is partially the issue. The finish floor type was not on in the views that we were creating the elevations on, but it still would create the view wrong. I removed all instances of 1 finish floor types and that fixed the issue, but once we redraw any finish floor again it brings back the issue. I even tested everything out to see what would fix it. I changed the finish floor type, I changed the level it is hosted from, and even created a new one from an existing. Any new finish floor that is drawn creates this issue so it looks like the model has some sort of bug in it.
It is related to the position of the floors, and levels, etc... It is just the way Revit "reads" the geometry, there is nothing wrong or corrupt with the model. I spoke with one of the Revit "old timers" (I am actually one of those guys who is an old timer I think? ) about this some time ago and he described it was related to the way floors were positioned in relation to the levels. I can't remember exactly what the cause was. So basically what I am saying, is, it is Revit behavior, that is the way it works. If you are seeing it, it is probably just easier to manually fix it and move on.
Eventually you may see some kind of behavior change in Revit around it, but it is typically a pretty edge case in that it does not happen ALL the time.
@barthbradley wrote:
Old Timers Rule!
We know where all the bodies are buried.
I suppose I am about as "old timer" as they come with regard to Revit. I started using it ~2002, and started working for Autodesk in ~2005. So experience with Revit goes back to the old pre-acquisition days. There are probably only 10 or 15 of us at Autodesk (on the Revit team) that go back that far.
I'm not sure this is actually an edge case. I'm working on a project with 50+ interior elevations, and I'm experiencing the same behavior. Revit detects the room bounding edges at ceilings and walls, but the crop region defaults to the bottom of the floor instead of the room bounding edge at the top.
I replicated the same default behavior in a fresh project in Revit 2020 with four walls, a floor, and a ceiling.
We are talking about hours of repetitive work to re-align the bottoms of each crop boundary on a medium or larger project.
OK. I've been experimenting with this bug, this morning, and I've found a clunky workaround that is going to save me from manually adjusting 50+ crop regions. I consider this a fundamental bug in the software. It is certainly not an edge case.
Observations, in Revit 2020:
Solution / Workaround for clunky behavior:
I have also been experiencing this issue. We use thin floor assemblies and layer them on top of our slabs for things such as Tile or to create colored areas on the plan for graphic presentation purposes. So for instance we will have a 3/8" tile assembly setting on top of the Slab.
My clunky work around is to select all the "finishes" or assemblies and copy them over into model space outside of the Plan view crop. We set all of the the interior elevation views and then move all the finished floor assemblies back into place later in the production sequence. It has seemed to work and is faster to do than resetting all the interior views manually.
@Anonymous, we made an add-in that automatically updates the outline with one-click. Perhaps it works with your situation. The demo uses a filled region, but it can work with crop shape too. @loboarch @barthbradley
Can't find what you're looking for? Ask the community or share your knowledge.