Duct lineweight vs fitting lineweight

Duct lineweight vs fitting lineweight

pteague
Advocate Advocate
2,451 Views
10 Replies
Message 1 of 11

Duct lineweight vs fitting lineweight

pteague
Advocate
Advocate

I'm having an issue where the duct lineweights and fitting lineweights aren't matching.  I've checked everything I know to check (VG overrides, global object styles, system specific graphic overrides, view range settings, filters).

 

Any thoughts?

 

ducts.png

0 Likes
2,452 Views
10 Replies
Replies (10)
Message 2 of 11

Anonymous
Not applicable

You seem to have checked the obvious things.

 

Is this every duct fitting or all of them? Silly question, but are you using view templates? If so, is the view template locked to use the correct settings? That's the only thing I can think of if you've looked at filters, VG, Object Styles...

0 Likes
Message 3 of 11

tuuletin
Collaborator
Collaborator

1. Change line thickness of DUCT and DUCT FITTINGS on Object style dialog. This will be applied to all not overridden views.

Or

2. Override graphic settings of a view by changing the thickness of DUCT and DUCT FITTINGS in the current view. This is applied only for the current view.

Message 4 of 11

pteague
Advocate
Advocate
I may have found a major clue, and possibly a real problem with Revit's ability to do plan regions in ceiling plans.

We have a plan region set up in this area. The main view range settings are cut at 7.5', top at 11.5' and depth unlimited. The plan region is cut at 7.5', depth at 25.5', and depth at 25.5'. The plan region affects the lineweight of only the fittings and not the duct. The duct lineweight is only controlled by the main view range.

So the duct lineweight is being shown in the <BEYOND> line override because it is above the top elevation for the view range.

This seems to be a major inconsistency in Revit's handling of plan regions in ceiling plans.
0 Likes
Message 5 of 11

tuuletin
Collaborator
Collaborator

Sorry, my last post was useless, didn't read you carefully Cat Tongue

I had had this issue, and I solved it. Also, I tried to model your problem, and for me it seems, that everythong is fine (ceiling plan with plan regions with different view ranges).

Could you model this problem again in an empty rvt-file and upload it?

0 Likes
Message 6 of 11

pteague
Advocate
Advocate

Here's an exact replication of the issue from an empty project.

 

I have set the <BEYOND> linetype to be red to highlight the issue.  Duct shows as red (beyond), fittings show as black (normal).

0 Likes
Message 7 of 11

Anonymous
Not applicable

Nice detective work. Seems like you found an issue with plan regions then. I've had similar issues with pipework and plan regions (where they don't show drop / rise correctly). 

 

As a workaround you could make a filter for Ducts and apply the lineweight you require for ducts, as filters should take precendence. Silly workaround I know, and it may not work depending how you have your views set up.

0 Likes
Message 8 of 11

tuuletin
Collaborator
Collaborator

Hello, dear,

please, check your view ranges.

Your duct is placed on 9' 0''.

The upper view range is 8' 0''. If you set the upper view range higher, that the center-line of your duct-works (for example, 9' 00''), I guess, you will get correct linetypes. Please, try this and let us know, if this helps (I succeeded in your duct beyond.rvt ‏).

Cat Mad

0 Likes
Message 9 of 11

pteague
Advocate
Advocate
I know that my view range is lower than the duct, but the plan region should be overriding the view range settings, and it does for the duct fittings but not for the duct.
0 Likes
Message 10 of 11

Alaaeldin_Alsahli
Alumni
Alumni

Just wanted to let you know that it is one of the known major issue with MEP family system and plan regions from long time ago, it is still under investigation to find a fix but for now you need to use graphic override and filters as alternative solutions.

 

I will keep you posted in case i get any updates on that.

 

Some related issues such as Rise/Drop Symbol vs. Plan region is been fixed for the upcoming release (2017)



Alaaeldin Alsahli


Please mark Accept as Solution if your question is answered. Kudos gladly accepted. ⇘
0 Likes
Message 11 of 11

pteague
Advocate
Advocate
Thanks for the update.
0 Likes