topic Re: More Stair Fun (Bugs?) in Modeling

More Stair Fun (Bugs?)

Laura Yanoviak — Thu, 25 May 2023 14:45:18 GMT

I'm pretty sure the Nosing and Tread Pens and Line Types are reversed.

Re: More Stair Fun

Laura Yanoviak — Wed, 19 Jul 2017 18:21:36 GMT

Also -- Turning off the "Structure - Beam" setting in MVO does not turn off the beams (this is apparently controlled by "Structure - Cantilevered", although the structure of this particular stair is Beam for both Flight and Landing).

Re: More Stair Fun

Steve Jepson — Fri, 21 Jul 2017 02:00:52 GMT

And try to show total Run of the Stair. Even with a label.
I haven't found how to do that yet.

The annotation I need to show for the Stair looks something like this: or at least this kind of information.

(17) RISERS @ 7 5/32" = 10'-1 3/4" - TOTAL RISE
(16) TREADS @ 11"= 14'-8" - TOTAL RUN

And what this annotation needs to represent is the Stair - not the Carriage which most often will have one less riser than the appropriate way to annotate the Stair.
Be careful how you use Start with riser/tread - End with riser/tread because you may be generating annotation for the Carriage rather than for the Stair.

If there is a Number of Risers = Stair Height, Why is there no Number of Goings = Stair Run ?

Goings?!?! Really? Why didn't they just ask me to help them with the words?

Re: More Stair Fun (Bugs?)

Steve Jepson — Fri, 21 Jul 2017 18:18:38 GMT

or this one...

Re: More Stair Fun (Bugs?)

Steve Jepson — Fri, 21 Jul 2017 18:23:13 GMT

?

Answer: Use the End with Tread function - but what if you don't want to end with a tread but you don't want the gap?

Re: More Stair Fun (Bugs?)

Laszlo Nagy — Sat, 22 Jul 2017 14:24:42 GMT

Guys,

I will report these issues you raised to GRAPHISOFT.

Re: More Stair Fun (Bugs?)

Ernest Atanasiu — Fri, 18 Aug 2017 10:56:13 GMT

Hello there,

I will just add this here, no reason to open a new thread.

I have a monolithic stair with slanted risers, no finish on the treads.
As you can see the value of the slanting distance is not equal to the real distance in a section view.

later that day: I noticed that even if you select the "no finish"option and previously had a non-zero value on the finish tread, it still takes into account that value somehow.

It looks to me as this approach is part of a broken workflow. Once I have set the "no finish" the tool shoudn't consider those values anymore, don't you think?

Thank you for looking into this.