Is this meant to happen this way

… or is it an exception to how stickiness works?

Never encountered this situation until I was fooling around modeling a very simple railing segment.

Stickiness works as expected with just one rail in the equation. When I add the second rail, and the initial baluster is connected to both rails, the copies don’t stick to either one.

A way I found to make the baluster copies stick to the rails is to first group the two rails, then model and group the first baluster with the baluster copies. Finally, apply the outer shell command to the two groups.

It also works if the rails are grouped, and after the balusters are in place the group is exploded.

The reason I want the stickiness (rather than separate groups for rails and balusters) is because in some instances I find it faster to select geometry and just move (stretch) it for modifying height or length


Hello, when you push/pull your first baluster to the upper rail, it connects automatically. When you Select it and copy it, it does not intersect automatically. Select all and intersect.
Have you tried using components instead of groups ?

Currently Move tool is only capable of cutting a hole inside a face if the selection was cutting hole(s) in exactly one face. Since this selection cuts holes in two faces, SketchUp currently doesn’t bring those holes over when copying.

Thank you both.

Yes, I was just wondering why SU wouldn’t bring the holes over.

I had not thought of using Intersect Faces thanks! it is a quicker, more elegant solution for what I’m doing.

Eventually I do use components (if there is enough repetition) after I create the rails, doors, windows, etc. but I still use Move and its stickiness to elongate the objects.