Draw Order of Objects

[meVAWU8]

I just have learned that there is some kind of Draw order in Revit for 3D Objects. I usually use Volumes above some 3D objects to define areas in 3D Space.  

Here you can see the Greenish Area is a Volume. It was modelled after the Green and Pink Walls. But the Orange Wall was modelled after that. What this causes is that when looking on the screen everything is fine. but when printing out this happens:

I am perfectly fine with that draw oder, that things that you model first are drawn first and so on but I would love to be able to control that beyond the order of modelling. This is a really big deal. And probably causes many people a lot of headache! Either have a way to prioritize the draw orders by category or just give us the option to change that.

[vitorbortoncello]

It's' not about drawing first, it is about override hierarchy and wall priority:

https://help.autodesk.com/view/RVT/2024/ENU/?guid=GUID-67D3D6DB-E78D-4711-B9C3-4D30F1C22205

https://help.autodesk.com/view/RVTLT/2022/ENU/?guid=GUID-1CCD1005-CBDA-4338-8D60-489095D4BB25

[barthbradley]

Revit should be printing exactly what you see (WYSIWYG). Sounds like you are saying that it is not.  Post the file you're working on and we'll take a look and see. 

[meVAWU8]

that is true but not the reason for that problem i described.

you can simple test it out yourself. Draw two walls and let them cross, without connection you will see the one drawn later will be "above" the earlier.

[meVAWU8]

here you go, side by side

[mhiserZFHXS]

I may just be misinterpreting what's going on here, but this all just looks messy. What do you mean you use "volumes" to define areas? You make an actual 3D extrusion?

The issue is you have objects just phasing through other objects like they're all ghosts. Its a mess. Even your example is a generic model passing through a wall (not two walls intersecting, as you claimed). One of those objects would cut the other. 

[meVAWU8]

- ignore the mess from before

my example is quite simple I use Volumes to "mark" an area in 3 dimensions so it is visibile in floorplan, section, elevation

it doesnt matter if you use volumes (massing tool) walles, furniture what ever you use, once you have them phasing over each other the order of modelling defines how they are going to be printed out in PDF. This is especially important to know since this also causes that Furniture lines and fill region of the furnite to be drawn above a wall when put next to each other, which makes "thin" lines in the places where you have a furniture for example a wardrobe next to a wall, and the thick line of the wall continous  when the furnite ends. to avoid this from happening just draw the wall after you have placed the furniture.

knowing this behavior means that there is some kind of priority of printing, when making PDFs. The priority is definied by when an object is created. IT doesn't matter if is a wall, a furniture, a volume, a window what ever you "draw/modell" first gets printed/drawn in pdf first. 

this is in most senarios perfectly fine but then when placing furniture you have a problem especially if it is sidebyside to a wall 

when you use volumes to mark an area it is a problem.

this two usecases are the ones i can think of right now but i am sure a lot of "bad" looking pdfs errors stem from this

[fespino]

Revit has printing issues for a long time now. It DOES NOT print what you see. For instance, we have an existing slab and a new slab at the same place, however some of the lines of the new slab do not print. I've tried different PDF apps with the same error (is not the app).

[barthbradley]

Toggle View Visual Style from Hidden to Wireframe.  

[fespino]

It is in wireframe. Done multiple research and no solution. It does not happen all the time but it is persistent with different models. 

[barthbradley]

Not following. 

Wireframe:

Hidden:  

[fespino]

Model

Print Preview (lines missing)

[barthbradley]

Post that rvt.  

[fespino]

Sorry, not allowed to do that, company policy. Just hoping if anybody was aware of this problem. Thanks for trying.