Beam length schedule issue

[Milan]

Guys, once again thing that I don't get it!

I have a curved beam (vertically), and I'm trying to do quantities for it, but one simple parameter I can't 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]

 .  I deleted this post because I did not realize you wanted a tilted and curved beam.  No such thing in Archicad - as far as I know -  unless you use a little .gdl scripting. So how did you make the tilted and curved "beam" you want to schedule the length of?

[Milan]

Hi Steve. I appreciate your help, but dont see how modeling everything twice with another type of tool would help. That means that i would need to update model twice when any change happens... which is not an option. 

For now I created property, called beam cength, and I sust copied the real value in there... 

It would be nice to extract somehow real value in there automatically. but im not expert in property expression thing

[Steve Jepson]

 .