Joining sketch lines so that swept object doesn't have joins

I have searched high and low and followed all the suggestions.
I am modelling a handrail by sketching lines, then adding arcs at the corners.
If I double-click one of the lines, all of them become selected, which I’m told means that they are all part of the one sketch?

I then sweep a circle on that path to make the handrail. This works, except it is in segments. I don’t want those division lines visible, as I want this to be one continuous extrusion.

I’ve tried Union and that doesn’t work. I’m missing something obvious I think?

This isn’t an answer but another way of doing this quite efficiently is to create a box, fillet the corners and then sweep your circle around the edges of the box. I find this so much quicker.

Oh yeah. Dont know why I didn’t think of that method!

Hi MyrtleTurtle,
Welcome to the Shapr3D community! Those lines are there only when you are modeling. If you go into Visualization, they will disappear and your handrail will look great.

Actually they are still there in Visualisation - in fact even in a technical drawing that I created for export. I’m confused because everything I read suggested the same as you.

Further info: I just tried it again with a new sketch that was just a rectangle that I swept a circle around. Same thing! Is it normal that when you sweep something you have to select each “section” of the path to be swept along?

Each section needs to be selected. If you start the sweep with the face and one section selected, you will need to select each in the path. If you select all sections, as in this video, the sweep is a little quicker. The result is the same.

1 Like

Also see @Shaun’s video. Working with body edges instead of sketches works very well!

Exactly these kind of approaches makes projects slow in recent version. The method is great but it leaves additional unnecessary trace in history (sketch for body, extrusion, filets and then body deletion).

This is not true, and additional steps by themselves should not slow down Shapr3D. In some situations it can, but it shouldn’t really cause an issue.

1 Like

What I’m saying is keeping history shorter is more efficient because app don’t need to calculate additional steps, at project opening for example.