Nice work, this will allow users to create very ornate newel posts and stair assemblies.
Thank you
Perfect, Nathaniel, thank you for adding this feature. Users can now create any style of staircase they want.
For someone who creates concepts this is so helpful making the overall workflow completely flexible and parametric.
Version 4.4.8c - 04.19.2026
- Fixed a minor typo in the stair module.
- Added a ornamental iron baluster into the baluster component library.
The limitations of profile cutting balusters can be overcome by using a predefined component instead, which allows for much more intricate baluster geometries.
However as I have been researching various baluster layouts I’ve noticed that with iron balusters usually more than one baluster style is utilized. The typical scenario is two or three different baluster geometries are alternated along the run of stairs. I will need to give this some more thought.
Stairs can be a “rabbit hole”.
Version 4.4.9 - 04.19.2026
- Enabled a secondary custom profile/component parameter for balusters.
- Added additional ornamental iron balusters into the baluster component library.
I think I’ve beat this horse to death. Hopefully with this added option we can configure most of the common baluster layouts, however there will always be a few that will be beyond the scope of the plugin (ie. three or more baluster types in various repeating patterns).
Perfect, this looks great.
Version 4.5.0 - 04.20.2026
- Enabled custom components as posts for OTP handrails.
- Enabled “profile cutting” of posts for OTP handrails.
- Modified the bottom trimming algorithm for balusters to better accommodate complex baluster components.
- Added one additional ornamental iron baluster into the baluster component library.
- Added one OTP newel post into the newel post component library: LJ4270_43
I will readily admit configuring OTP handrails with their associated posts and fittings is a bit tricky, adjusting the various offsets takes a few iterations to really hone things in.
I appreciate everyone who has pushed me to flesh out the newel post and baluster capabilities. I feel like the stair module is a bit complicated now and perhaps even a bit clunky with so many options and variables but at the same time it is much more configurable and flexible and can I say with these new capabilities more powerful.
Obviously it would be optimal if I could spend some serious time and create many of the standard balusters and newel posts found in LJ Smith’s general catalog so that the user would have a bevy of options to choose from without having to exert additional effort in creating their own. However, such an undertaking could easily consume two to three weeks and my development time is probably better spent elsewhere at the moment.
This is fantastic! Thank you for all your ongoing effort in making this module so customisable.
Well… I thought I was done with balusters and newel posts, but I’m not quite there yet.
The problem is that with metal or iron balusters they are often installed with a shoe as shown below:
My current algorithm installs balusters just like they are installed in real life:
First I trim the top of the original baluster component/group and then I have to trim them individually for each of their bottoms because the balusters may intersect the treads at different heights hence their heights/lengths will be different.
Because of this a predefined shoe positioned at the base of the baluster component may work for one location (ie. no trimming required) but then it will be removed in subsequent baluster locations.
What this means in practice is that a shoe (if that option were enabled) needs to be a completely separate group/component just as it is in real life. My algorithm needs to position it individually in the Z-dir just as I trim each baluster bottom individually.
Arguably, there is a lot going on with stairs, the guys that install these must be real craftsmen, I certainly take my hat off to them.
Version 4.5.1 - 04.22.2026
- Enabled custom components as baluster shoes for vertical and OTP handrails.
- Added the following (L.J. Smith) baluster shoes into the baluster shoe component library: LI_ALFSH01, LI_ALR010, LI_ALRD201, LI_ALSQ301, LI_ALSQPL1, LI_PROCOL.
I took the time today to carefully model a few of these baluster shoes since they are fairly simple geometry and it is always fun to get my hands dirty with some actual modeling and take a small break from the code.
Looking at all the updates I’ve made to the stair module these last couple of weeks made me realize that stair assemblies rival wall assemblies in complexity and the underlying data base (attribute library) for a stair assembly is quite large now. I have thought about splitting the stair module out as a separate extension but there has to be more than one reason to do so. For now I will probably keep it hitched to the Wall plugin but at some point I need to put together a balustrade or railing tool, at that point it may make sense to create a separate extension for the railing and stair tool combo. Thoughts?
Version 4.5.2 - 05.08.2026
See the Medeek Stair thread for more details. My plan is to split out the stair module in the next few weeks, but right now it is not the highest priority.
Version 4.5.4 - 05.22.2026
- Added an option for a top and a bottom baluster shoe.
- The top baluster shoe can be controlled with the additional “shoe height” parameter, which in turn allows for baluster collars.
- Added the shoerail offset parameter to vertically offset the shoerail.
- Fixed a bug in the railing edit menu with metric units.
Version 4.5.5 - 05.24.2026
- Enabled presets for railings within the draw and edit menus.
Hi Nathaniel,
This is great for building detailed railing assemblies, using custom components,
Thank you
Can we have presets for stair too, working with any configuration?
Let me see what I can do on that.
Version 4.5.6 - 05.25.2026
- Enabled presets for beams.
- Enabled presets for in-wall columns.
Now I just need to enable presets for stair assemblies. Stairs have a lot of parameters so that will take me a couple hours. The memorial day weekend has been quiet (not too many tech support emails) so I’ve been able to knock out few things.
Thank you — I’ve been wishing for that the last couple weeks.