Priority based intersections odd behaviour

[Anonymous]

Hello there. This is my first post after some self taught archicad sessions.

I have modelled the foundation structure of a project where I have underground piles held together by pads.
What you see in the picture is the pile's intersection with the pad. Pad & pile have different material priority so when I produce a scheme I get the correct net volume of the pad (i.e pad volume - intersecting piloti volume). However, the visualisation is wrong: the piloti is subtracted by the pad and not the other way round.

I have also encountered this behaviour with other elements. Note that the pads are modelled with the slab tool, but this behaviour also shows up if I convert them to forms.

Any ideas?

[Barry Kelly]

You said that the pad and pile have "different material priority".
You are correct with that - you just need to make sure your pile has a stronger Building Material Intersection Priority than the pad.

Barry.

[Anonymous]

Barry wrote:
You said that the pad and pile have "different material priority".
You are correct with that - you just need to make sure your pile has a stronger Building Material Intersection Priority than the pad.

Barry.

Thanks Barry. The priorities are setup correctly. As I said, I get the correct deduction in volume - according to the priorities setup - but the visualization is wrong. This has happened with other elements, mainly those modelled with the slab tool.

I'm currently using the educational version, if that may influence the outcome of it...

Anyone has encountered this?

[Barry Kelly]

What is the strength of you pad Building Material and what is the strength of you pile Building material?

Barry.

[Anonymous]

Barry wrote:
What is the strength of you pad Building Material and what is the strength of you pile Building material?

Barry.

Sorry for the delay.

The pad material is Structural Concrete, intersection priority 760
The soil material has an intersection priority of 140.

I have also noticed that the intersection priority of slabs with slabs does not seem to work... Are there any restrictions on that?

[Barry Kelly]

I think it is working properly.
If you select just your pad and view in in 3D (shaded view not wire frame) you should see the column holes.
And if you select just the columns you should find they are not being cut.

More examples to follow.

Barry.

[Barry Kelly]

If you are looking at your 3D window in OpenGL with wire frame mode it will appear incorrect.
I think this is what you were showing.

My original images were done by making the pad layer wireframe and not the whole 3D window.

This is the same 3D in OpenGL with wireframe on.

Barry.

[Barry Kelly]

Oddly if you switch to the Internal engine in 3D with wireframe still it all looks correct.

Maybe a bug with OpenGL wireframe?

Barry.

[Barry Kelly]

As for your slab to slab connections there is no automatic connection for those.
You must use Solid Element Operation to make the connections.

Here is a chart (from the reference guide) showing what can connect to what and if the connections are completely automatic (green), required you to invoke the 'connect' command (blue) or only interact with SEO (red).

Barry.

[Anonymous]

Thanks Barry. Didn't have the SEO matrix in my radar...

Barry wrote:
As for your slab to slab connections there is no automatic connection for those.
You must use Solid Element Operation to make the connections.

Here is a chart (from the reference guide) showing what can connect to what and if the connections are completely automatic (green), required you to invoke the 'connect' command (blue) or only interact with SEO (red).

Barry.