Beam length schedule issue

[Milan]

Guys, once again thing that i dont get it!

I have a curved beam (vertically), and Im trying to do quantities for it, but one simple parameter I cant extract, and it is Beam Length. All I can get is 3d Length, Left and right length. I tried all of them, left and right leave me empty field in a schedule, but 3d length is not correct. Is way smaller that in reality should be!

Is this value that is correct and that I need to show in my schedule. Any idea? 

Operating system used: Windows 11

[Milan]

I mean. Is possible to do anything in this program, besides of basic rectangular shapes. Is soo freaking annoying how it lacks basic functionalities... And every time improving with some features we actually dont need... huh 

[runxel]

I can't confirm that. 3D length works fine for me:

[Milan]

Works for me in the floor plan, but not when vertically curved beam. Is both inclined and vertically curved, quarter of a circle, and is giving me some random value, cant figure out which one, is neither chord length, projected length, nothing, just some number, smaller than real length... 

[Milan]

Also, to mention, is not taking in mind SEO extraction for calculations

[runxel]

---

@Milan  schrieb:

Works for me in the floor plan, but not when vertically curved beam.

---

In that case, yes, you're right. That's a shame. For vertically curved beams there is no 3D length.... 😒

@James B another thing you could fix 😉

Also double curved beams (floor plan and vertical!) please!

[Milan]

Do you have any idea how I should handle it ? I would write expression and new property if id knew how they got 218 instead of 296cm, and then schedule that property...

[Steve Jepson]

There are quite a few situations where fundamental data like lengths can not be properly extracted.  And yes - it is annoying. 

There are of course work arounds.  There is always a way to get what you want out of ArchiCAD - if you want to fuss with it long enough 😞

One solution I use is to make the part that will generate the correct data in the Interactive Schedules and place it off to the side somewhere.  That part is the one included in the Schedule, the other one is in the model for the sake of various graphics, perhaps converted to a morph.    

Theoretically, you can keep the two parts in the same place and control visibility with layers and such, but I like to keep such Scheduling-Only components out of the model where I can keep track of them better.   Nothing like that should be necessary - but sometimes it more efficient than a .gdl or Expressions type solution.