Narrow view range in plan region doesn't work

PDSF
Collaborator
Collaborator

Narrow view range in plan region doesn't work

PDSF
Collaborator
Collaborator

Hi all. I'm trying to create a crawl space plan for a single family residence, including a deck area framed with about 10" clear to gravel below. But I can't get a plan region that shows the area correctly. There are posts that support this deck and they do not appear, although the footing for the post does. I have noticed previously that very narrow view ranges in plan regions don't work. For example, we have a clerestory plan in this same model and the windows are not cut through correctly. Is there a trick I'm missing or is this just how it is? TIA.

0 Likes
Reply
Accepted solutions (1)
767 Views
14 Replies
Replies (14)

barthbradley
Consultant
Consultant

I think you are experiencing "low wall" behavior. It's curable. Not fatal.

 

Do not use "Unconnected" for Top Constraint.  

 

Cut Behavior of Low Walls - The Revit Clinic (typepad.com)

0 Likes

PDSF
Collaborator
Collaborator

The post (not wall) is not set to Unconnected, bottom or top.

post properties.JPG

0 Likes

ToanDN
Consultant
Consultant

Share the file here.

0 Likes

PDSF
Collaborator
Collaborator

I can't do that. I can't the detailed drawings for a private residence (including the address) on the internet. How does anyone do this with any kind of project?

0 Likes

barthbradley
Consultant
Consultant

Have you looked through this list? Betcha one of these 33 applies. 

 

Missing Something in a Revit View? 33 Steps to Find Stuff | Ideate Inc

0 Likes

PDSF
Collaborator
Collaborator

@barthbradley wrote:

Have you looked through this list? Betcha one of these 33 applies. 

 

Missing Something in a Revit View? 33 Steps to Find Stuff | Ideate Inc


I know what you mean--there are a lot of reasons why objects don't show up. But that wouldn't seem to apply in this case. The objects were literally copied from another subgrade area where they show up correctly. It has to be related to the plan region view range, since that is the only thing that is different.

 

another post.JPG

0 Likes

barthbradley
Consultant
Consultant

@PDSF wrote:

The objects were literally copied from another subgrade area where they show up correctly. 

 

 


 

Copied and Pasted to the View?  They look like Detail Items.  Are they? Detail Items are drawn at the Detail Plane of the View. View Range settings have no effect on Detail Items. Are you sure the element's Category/Subcategory is turned on?  

 

...also, FWIW: Detail Items are Annotative elements. 

0 Likes

PDSF
Collaborator
Collaborator

They are not detail items. They are modeled elements, copied from another location in the plan. Not copied and pasted. Again, here is a section where they show up correctly. The problem is with the narrow view range of the plan region. As I say, I have noticed this erratic behavior before. I just can't figure out how to fix it. I have played with the view range a dozen times but nothing works.

section.JPG

0 Likes

barthbradley
Consultant
Consultant
Accepted solution

Are those Columns?  Edit and uncheck "Show Family Precut in Plan View".  

0 Likes

PDSF
Collaborator
Collaborator

That worked! Thanks! What does that setting do? Why would anyone leave the setting checked? Is there a situation where it would be preferred?

0 Likes

barthbradley
Consultant
Consultant
0 Likes

PDSF
Collaborator
Collaborator

@barthbradley Is there a similar setting for windows? Here is the clerestory plan I referred to earlier. Note that windows M, N and O are cut through correctly but window L is not.

 

clerestory.JPG

0 Likes

barthbradley
Consultant
Consultant

I'd have to look at the file to figure it out, but it could have something to do with how Windows (and Doors) display in Project Plan View. They are not displayed based on the Project View's Cut Plane.  

 

Read more here: 

 

https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/Revit-Windows-and-...

0 Likes

PDSF
Collaborator
Collaborator

I'll do that. Thanks @barthbradley 

0 Likes