"detail view" vs "floor plan" in callouts

[shane.249457]

hi everyone. im working on a project where we have created a number of callouts under the "detail view" type.

in these detail views we cannot see a linked file, even though it is tuned on, and all the visablity settings are correct.

if we recreate the same callout as a "floor plan" instead of a "detail view" we see the link no problem

can someone explan what is happening here? is there a way to get my links to show up in "detail views" if not.. what is the purpose of this type of view?

(note, in the past i have used "floor plans" due to problems, but now we have created many detail callouts for a project and recreating them would be alot of work)

thanks

[wmullett]

Seems to work fine for me if it is either a detail or a plan. Both types show the link. Are you sure nobody hid the link in the parent view? If the did, then it is hidden in the call-out as well and will show in reveal hidden elements.

[brethomp]

Detail callouts and Floor Plan callouts have different options for the depth of the view. You may be able to see your linked file by changing the far clip distance of your detail callouts.

[shane.249457]

the detail views work fine for me when they are taken from sections or elevations. when i take a detail view from the plan i loose the link.

nothing is hidden in the view or the parent view

[wmullett]

Something is wrong on your system then because we have not had any problems in 8,9,10 or now 11. You are talking about a linked Revit file - not a linked CAD file - correct?

[Scott Womack]

Something is wrong on your system then because we have not had any problems in 8,9,10 or now 11. You are talking about a linked Revit file - not a linked CAD file - correct?

We have this problem as well. A Detail callout off of a floor plan will not let a structural column that is in the linked Revit Structural Model Appear. If I do the callout as a plan, it is fine.

Even odder is that the Linked Revit MEP file is visible in a detail callout.

[brethomp]

We have this problem as well. A Detail callout off of a floor plan will not let a structural column that is in the linked Revit Structural Model Appear. If I do the callout as a plan, it is fine.
The columns in the structural file probably have the "Show precut in plan" check-box checked in the family categories and parameters dialog.

[cliff collins]

Yes--and then the Arch. has to get the Struct. eng. to go into all the column families and change the settings, reload, Synch to Central and post to FTP ( or save across WAN )
a bit tedious just to get a column to show up in a callout!

cheers

[Scott Womack]

The columns in the structural file probably have the "Show precut in plan" check-box checked in the family categories and parameters dialog.

Bingo! Thanks for the info. Now I need to tell my structural engineers about this.

Thanks!

[Scott Womack]

Yes--and then the Arch. has to get the Struct. eng. to go into all the column families and change the settings, reload, Synch to Central and post to FTP ( or save across WAN )
a bit tedious just to get a column to show up in a callout!

OK, question for Cliff and Factory!

If the families are set to be by my project, if I load the column families into my project with the Pre-cut check box over, why is'nt it working then to correct this issue? Logic might say that correcting them in my project should cause the correct column behavior from in the linked model. It does not appear to carry that far through.

Scott

[cj_follmer]

we recently asked our structural eng to turn off precut but they were not able to as it messed up their graphic settings. I don't know how/why - I'm taking him at his word. So we are opening up the copy we get of their model and making the change ourselves. This works as we don't have in-house struct.

BTW The braces have the same precut option that when unchecked allows the braces to be cut correctly per view range.

CJ

[thand]

This post is a classic reason why AUGI needed to have all of it's earlier post in a searchable format... Just had a co-worker that has been having the exact same problem that this post identified and prevented me from having to re-post the same question again...

Thanks everyone for all the hard work and discussion that helps us all become better with Revit..