Degenerated Polygons? Everywhere!

[Patrick M]

Can someone please explain to me why custom profile beams almost always have "degenerated polygons"? This session report comes up any time a project uses custom profiles. It's a very simple profile with about 7 nodes and a curved edge. The beam settings do not have any additional modifiers, it is not stretched in any way. There has to be something I'm missing, but I've done everything I can think of to fix files with degenerated polygons in the beams and I'm coming up empty. Anyone at GS here can shed light on it?

Operating system used: Mac Apple Silicon Sonoma

     

[Lingwisyer]

If an extra edge is not an issue, adding an extra node along the curve may resolve it.

[Patrick M]

I'll give that a try; not holding my breath.
I also do not think this report is a factor in file performance. There are MEP degenerated polygons that are triggering crashes, but this particular profile (and session report error) has been in this file for years

But I'll see if an extra node on the profile clears it from the report... good suggestion!

[runxel]

Coincidentally I've found some corrupted profiles in my template file today (contour lines could not be overriden) and the only solution was to redraw everything – like completely, not just putting a node somewhere or whatever. (The node still might help since it fixes the small radius)

But yeah, there might be some underlying issue in any case that is not resolved by "Open & repair" either.

[Patrick M]

different project, different profile, no curves, same warning: "degenerated polygons".
these are literally just a few squares and a couple L shaped fills. No curves, no extra nodes, nothing tricky. Beams they are applied to have no slope, angle, taper or rotation setting...  so is this a complex profile issue? what gives? I'm seeing basically any file using complex profiles getting more and more degenerated polygons and session report warnings (which is every file I'm managing).

[Barry Kelly]

Are you sure the degenerated polygons are coming from these complex profiles and not a mesh or slab somewhere?

Or are these complex profile beams/walls interacting with other elements and causing the problems?

Barry.

[Patrick M]

Barry,

Even when I pull them away from the model, their unique ID's are still being reported. It does seem prevalent where beams are intersecting with beams... but if we can only use complex profiles where model elements do not intersect, what is the point of them?
The above (most recent) example could have been modeled with 4 slabs or 2 slabs and an SEO; but that would have been tedious to maintain and to model in the first place. I'll try copying a single beam with that profile to a separate blank file as a test; but the fact that the unique ID being identified are these beams with complex profiles (seemingly any profile some times) is a bit concerning.
I'd think it's something to do with the fill thickness, but these are 1/8" min. thicknesses. If AC can't model/document elements less than 1/8" thickness in a complex profile, the tool needs to be revisited and maybe rebuilt. We are often times designing things to align and flush to finish to a 1/32" tollerance