Bug with the presentation of beams on slabs

[runxel]

If this option in the MVO is on (show hidden lines under a slab for a beam)

and you place a beam with its reference line on TOP of a slab like this:

your graphic output in the plan will be wrong:

Ouch! This should have been a solid outline...

Looks like an easy fix however and somebody just got an IF clause wrong.

Found just now in AC 27, other versions are probably affected too.

[Mahmoud Qenawi]

Hi @runxel,

I see hidden in INT attributes represented by dash lines while what you show is dotted lines so it may be something related to the beam display or GO.

[runxel]

Thanks for your comment, but no, there is no GO involved here 😉 The linetype comes from the beam settings themself.

It's a bug, just as I stated. You can try it yourself!

[Laurentiu C]

This probably really is a bug.

If the reference line touches the top of the slab or is below the top of the slab it will display as hidden.

The reference line axis can either be a top/middle or bottom, it doesn't really matter. It only matters if it touches the top of a slab or is below it.

Here's a quick comparison. It's definitely not the expected behavior.

This feature is from AC23. Hopefully someone at Graphisoft can look into it.

[Mahmoud Qenawi]

Hi @runxel & @Laurentiu C ,

According to the video yes you're right.

But i think defining the slab and beam with Top surface  criteria was before being able to change the slab and beam reference lines,

so if @GRAPHISOFT can correct the video to replace the Top surface with Reference line that's all.

check it and you'll find that there's no bug, thx.

[runxel]

Not sure what you're talking about?!

This current behavior is a bug no less.

[Mahmoud Qenawi]

I'm talking about this video from GS explaining this case and was shared @Laurentiu C reply above,

https://youtu.be/Zj9VEpmxhUc?si=5gwVA86jvVA0RQcr

I hope this helps.

[DGSketcher]

This looks like one of those mathematical failures that happens elsewhere in AC. Commonly seen highlighted in the GDL coding as ["if A = B then " - Warning: Comparison of real values may lead to unexpected results]. In this case an assessment should be made on where the rest of the beam is positioned.

The case that frustrates me is the view cut off line for Sections. If an element is coincidental with, but outside the view, any logged Changes will appear in the Revision Object for that View. And the one obvious workaround... offset the view boundary, then looses associative dimension nodes.