I think I figured out why it is almost impossible to model the most basic railing in Archicad, when the railing is turning a tight on a stair or ramp corner. The problem is that the railing tool uses the posts centre line to define the reference line. The Railings are then offset from this line. It is a basic geometry issue, that due to this offset, a straight portion of the rail would be necessary to generate a level connection. In real life, the reference line is the centre or inner most line of the railing, therefore the turning can be done easily. The balusters and posts are then offset from this reference line. This is also the logic of the Regulations and Standards in all countries that I know, because the important dimension is the clear distance between the railings. (specifically, not the centre line, but the inner most point of the rail profile) It would be much appreciated if GS could improve the railing tool to give option to set the reference line to any of the Rails instead of the posts centre line.
Barry, if the connection controls would solve this issue, I would not have raised it here. 🙂 Typically this problem occurs on every single stair / ramp where the stair / ramp turns 90 deg (or other). The problem is always the inner rail. If I have space to add a flat portion to the ascending stair (typically an extra going in stairs) the geometry problem is solved. Here down under it is a regulatory requirement that a railing has to be continuous, going at the same height, with no vertical (goose neck) connection to other rail. Unfortunately, I am afraid, the only solution would be to allow the reference line to be set by the rail, not the posts.
Just another little annoying thing (not little) Why can't we lock an associated dimension to the inner point of a rail? Archicad recognises it as a point, yet the dim will not be associated.
If I have space to add a flat portion to the ascending stair (typically an extra going in stairs) the geometry problem is solved.
It has to be exactly that amount, if the railing has to follow the stair's slope. If two risers meet at the corner, there would be two riser's height that the rail would have to follow.
This extra going's length can be on the 90° bend of the railing, giving the extra riser height. From this the radius (equal to the rail offset) can be calculated, which is about 19 cm for a typical 30 cm going.
That would be the theory, but I still can't set up the connection to be perfect.
Another workaround is to set an offset for the whole railing, so its reference line will be on the handrail. After deassociating it from the stair the reference line can be moved inwards,. Adding nodes to adjust the heights will be necessary.
Péter Baksa Software Engineer, Library as a Platform Graphisoft SE, Budapest
I am glad that now you understand the geometry issue, you now have to look at real life: in reality, there will be no flat transitions!
As far as I can tell there has to be a flat transition if your rail goes out over the flat landing.
Then only time it doesn't, is if the rail is centred over the edge of the ramp where there is one point at the very corner that is the same height for both ramps and the landing with no flat portions.
As soon as the rail is offset out over the flat landing, then if the rail is to be all at the same height, then it must rake up with the ramp, go flat over the landing and then rake up with the next ramp.
It is physically impossible to connect 2 rails parallel with each ram as they just won't intersect.
Take the extreme and let's assume the railing is on the other side of the ramp.
The rails must go flat when they get to the landing.
Yes there are extra posts here.
On the inside corner it is the same thing, but you wouldn't have 3 post as they would all be to close, so you have one and just flatten the rails as the go around it.
If this is not the case in real life, then I suggest that the rails are not perfectly parallel to the ramps.
I'd like to see a photo if you have an example.
One of the forum moderators. Versions 6.5 to 25 Dell XPS- i7-6700 @ 3.4Ghz, 16GB ram, GeForce GTX 960 (2GB), Windows 10 Dell Precision 3510 - i7 6820HQ @ 2.70GHz, 16GB RAM, AMD FirePro W5130M, Windows 10