[BUG?] Stair Clearance doesn't work if stair doesn't intersect with slab

So this is sort of two wishes in one.

  1. We usually draw stairs without the top landing, this leads to a smoother transition to the slab(when looking at the graphics). It would be great with an option to end with a riser instead of tread or similar, currently we’re doing the stairs relatively manually, taking off one riser height and removing a step. So it’s sort of a hacky way of solving that issue.
  2. Our current issue is that the excellent function _vaSlabSubtractStairClearance only works when the stair actually intersects the slab, which means our hacky solution doesn’t work as well anymore. The solution we’re currently using is to instead use _vaStairClearanceContour, but that’s an additional step which we’d love to avoid. :slight_smile:

All right!

  1. This is already in our wishlist. To have an option to remove the last step but keeping all the stair parameters.
  2. 100% agree. We need to make _ vaSlabSubtractStairClearance command work when the stair top part doesn’t meet exactly the slab top surface.


1 Like

Hi @fsalla, possibly @enric

Would it be possible to get access to stairs in a upcoming update to the VisualARQ API? That’d make 1. possible to create relatively easily.

Hi @rheinason,

I added your API request, we will let you know in which update it is available.

Hi @rheinason,

I just want to let you know that we have just released VisualARQ 2.13, which includes methods for stairs in the API.

You have all the information about this new version here: VisualARQ 2 - Version 2.13 released