upgrading older templates - PBCproblems AC 17

[Anonymous]

Hi all,
I have dragged my composites with me for many versions (maybe since V9 or 10).
Now however I cannot get the PBC working.
Any composite I have created or modify from my composites and new composites I make in my template will not work.
However when I opened the new AUS template and brought in (cut and paste) some composites from there , the PBC work.
When I take my composites to an AUS template file, the PBC dont work.

In the image the walls at either end of this slab are mine.

When I substitute different BM's in both directions, no change , mine don't work, the templates do, so the BM's don't seem to be the problem.

Before I start the process of building the entire template from absolute scratch, does anyone have ideas, suggestions or experience with this?

Are there version barriers you should not cross with old templates?

Cheers Hugh

[David Maudlin]

Hugh:

Have you checked the Intersection Priority of your Building Materials (new attribute) in the Building Materials dialog box?

In the ArchiCAD Reference Guide, read the Migration Guide for ArchiCAD 17 > Migrating from ArchiCAD 16.

David

[Barry Kelly]

Hi Hugh,
Not sure if this is the same problem you are experiencing but I find that PBC doesn't seem to work properly when a wall is located on the edge of a slab.

See the image below.
The slab strength is higher than the face brick leaf.
But the slab has exactly the same strength as the cavity.
If the slab passes through the wall then the brick leaf is cut but if the slab edge and the wall line up then the external brick leaf is not cut - but it still does cut the cavity.

I am not sure if this is by design or by fault.
In this case it works well as I wouldn't want the slab exposed but if I did then tough luck - unless I make the slab strength stronger then it will cut everything.

To me logically it should be cutting the external wall skin as well so I would say it is a fault.

Barry.

[David Maudlin]

Barry:

I don't know what the difference is, but I cannot reproduce your error.

David

[Barry Kelly]

I think it is because I have a cavity that has exactly the same strength as the concrete slab BM.
If I make the slab BM stronger it of course runs through.
If I make it weaker then the cavity runs through and the slab stop inside the cavity.
It is only when they are exactly the same strength and at the edge of the slab that the slab cuts the cavity but then thinks it has to stop.
As soon as the slab extends past the side of the wall the slab cuts everything.

I understand that when 2 BMs have the same strength then Archicad will decide which cuts the other.
Clearly here the slab is cutting the cavity of both walls but why is it not cutting the face brick skin which is weaker.
Just a glitch that I can live with as I would never model the slab to the edge of the wall because that is not how it is built so the floor plan display would be incorrect even if the section was.

Probably it is a deliberate decision by GS because there may be an external render skin or cladding (siding?) on the outside of the wall that has a much weaker strength.
Because the slab does not pass all the way through the wall but meets with a skin (cavity) that is stronger then it will stop the slab on the side of that skin that the slab is on and the weaker skins on the outside of the wall will continue.
But when the strengths are equal and the slab is clearly cutting the cavity then my logic says it should continue cutting the other skins as well if they are weaker.
So in my opinion a glitch.

Barry.

[Anonymous]

Well fellows,
thank you for your efforts and suggestions,
apologies for not responding sooner but I have just resolved the problem, which was my layer settings.

The dilemma was caused by layer intersection group values which I never knew were saved by view.

This meant that for some layer combinations the intersections would work but not others.
Injecting attributes onto the same layers was not fixing the error and jumping from saved view to saved view was making the intersections change- very confusing!

I had reset all the layer intersection values once, but did not realise or spot that the view sets were turning them all back until just now.

Re-defining all my saved views has resolved the errors.

Thanks again for your thoughts,

Another trap for young (and not so young) players

Hugh

[Anonymous]

Sorry, to further clarify,
It is Layer Combinations which save Layer Intersection Group Values,
not the saved views, which reference those Combinations.

I redefined all my Layer Combos, not my saved views.