Unusual Behavior

[Dwight]

I'm just learning the annoyance and liberation of solid fills within elements.

The following two images show a column placed, and then the column layer is made invisible.

While the 3D is correct, the plan remains masked.

Am I doing something wrong?

[Dwight]

ho

[__archiben]

you're 'rebuilding' after hiding the layer?

sounds like a bug to me . . . although it could be quite useful . . .

~/archiben

[Dwight]

Absolutely.
And repeatable.

Playing with it again, I have discovered that between walls and columns with identical intersection priorities, this masking will occur, but dissimilar priorities fixes it.

Since I am unfamiliar with this feature, I see the error now.

Are intersection priorities important to many other users?

[Anonymous]

Dwight wrote:
Are intersection priorities important to many other users?

Now that we have to deal with them, they are very important.

Failure to set them correctly can result in embarrassing drawings (as you have seen). The feature was added in 8.0 to correct problems with the previous automatic system, such as walls on hidden layers (i.e. demo walls) continuing to clean to visible walls.

The general rule is that any layer containing walls or columns that is hidden should also be set to a different intersection priority (in the layer combination; manually managing this is unmanageable).

[Anonymous]

Are intersection priorities important to many other users?

Yes. Especially for remodel jobs and you use a wall to be removed layer. Without intersection priorities the hidden walls "clip" existing or new walls that are showing in the plan.

[Link]

Are intersection priorities important to many other users?

They are VERY useful! To add to Matthew's post, some other important things to note are:

Like locking/visibility/wireframe, intersection priority numbers are layer combination specific.

Intersection priority numbers do not increase in value (like 3D Intersection Priorities), so that a 1 is not any stronger than a 3 or vice versa. As long as the numbers are different the elements on that layer will not heal with elements on a layer with another intersection priority number.

The consequence of these intersection priority numbers are important in Solid Element Operations. Lets say for example you use a white beam (or any other 3D non-wall element) to subtract a recess out of a brick wall. To make it a white recess, you would set the SEO subtraction so that the 'New Surfaces of Target will: Inherit Attributes of Operator'. However, if the layer of the beam has the same intersection priority number as the layer of the wall, the recess will still appear as brick. You will need to change the intersection priority number of one of them (say the beam) to get the recess to show up white. Attached is an image of what I am talking about. It has also has a recess subtracted by a red column.

Cheers,
Link.

[Karl Ottenstein]

Link wrote:
The consequence of these intersection priority numbers are important in Solid Element Operations. Lets say for example you use a white beam (or any other 3D non-wall element) to subtract a recess out of a brick wall. To make it a white recess, you would set the SEO subtraction so that the 'New Surfaces of Target will: Inherit Attributes of Operator'. However, if the layer of the beam has the same intersection priority number as the layer of the wall, the recess will still appear as brick. You will need to change the intersection priority number of one of them (say the beam) to get the recess to show up white.

Ah, Link my man! That deserves a tip-of-the-month! If this feature is documented, I never noticed it ... but I've wondered why sometimes I couldn't get the "inherit attributes of operator" to work and other times it did. Thank you!

Karl

[Karl Ottenstein]

Dwight wrote:
Are intersection priorities important to many other users?

Really important. Without them, I'd have to use the patch tool quite a bit to get my drawings to look right. (If I used composites more, I'd still have to use the patch tool, but that's another story....)

Karl

[Link]

Ah, Link my man! That deserves a tip-of-the-month! If this feature is documented, I never noticed it ... but I've wondered why sometimes I couldn't get the "inherit attributes of operator" to work and other times it did. Thank you!

Thanks Karl. It seemed like a little find, in the grand scheme of things! Sometimes I submit posts that I find extremely valuable and no one blinks an eyelid. Then times like this when I flop in front of my laptop, before my morning coffee, and tap out a sleepy wake up post, it turns out to be pretty useful. Ahhhh - this is the beautiful thing about ArchiCAD-Talk. You never know what your going to get!

I always enjoy your posts, so it's a pleasure to return the favor once in a while! Hope all is well up north and you get to attend Robert Bissett's Art Gallery opening. That guy just keeps impressing!

Best regards,
Link.