• Added the following (L.J. Smith) rosettes: LJ7037, LJ7027, LJ7026, LJ7033.
• Fixed a floating point rounding error in the "Move Segment" tool.
• Enabled handrailing fittings (ie. rosettes) for the start and end of a handrail when no post at these locations is selected.
• Added a left and right half-post component into the newel post library.

I tested out a half post because I've seen stair railings that terminate like the image below:

• Added the following tools to the Medeek Wall Stairs toolbar: Draw Railing, Edit Railing, Move Railing.
• Enabled the railing tool/module, added railing type: balustrade (stair rail).
• Added various handrail fittings (OTP) for the LJ6000 series handrail: M0209, M0219, M0220, M0211_L, M0211_R, M0211_135_L, M0211_135_R, M0221_L, M0221_R, M0221_135_L, M0221_135_R.
• Added the following (L.J. Smith) shoerail profiles: LJ6000S, LJ6001S, LJ6006S, LJ6045S.

This is brand new so there will be few fires to put out and some fine tuning or maybe even a few additional parameters needed. Send me your feedback.

However if the face count of the "cutting" post is under 100 then I just use the original post geometry. I've noticed that some of these ornate posts can have over 400 faces or polycounts.

Now I just need to do a few more checks and throw the kitchen sink at this thing:

Here is a first look at these various railings with shoerail added.

The offset option for each post position allows one to have the shoerail cut by the posts or rest underneath the posts. I'm trying to make this as flexible as possible. Also I created the four standard LJ Smith profiles beyond the very basic rectangular profile.

Due to the fact that there is quite a bit of boolean subtraction that can happen with the interaction between the posts and the handrail/shoerail combo, regenerating a railing can take a while, especially if it is much more than about five or six segments. I guess its a tradeoff between simplicity and ornate details.

The only way to squeeze more performance out of the boolean subtraction is to convert it to a more low level C++ routine, I may consider that.

The problem with boolean subtraction is that if you are a dealing with a lot of rail segments and posts it can slow things up a bit. I may have to rethink this or have a way to disable the boolean subtraction for those who prefer performance over cosmetics.