topic Re: Trouble with Stitch in Fusion Design, Validate & Document Forum

Trouble with Stitch

Anonymous — Mon, 26 Feb 2018 21:50:36 GMT

Hi,

I'm following some surface modelling methods from an Autodesk video on youtube (see my previous unanswered post if you want to know which one exactly) and now I'm having trouble stitching.

I can't really find any support online for how to fix 'free edges', and I'd like to understand what they are and how to repair them - or better yet - avoid them.

When I click on the information window on the stitch panel, it takes me to a link about the 'merge' option in the modify menu, but that doesn't appear for me, is it perhaps outdated?

Any help with this would be greatly appreciated.

Here is the file : http://a360.co/2FytOOt

Re: Trouble with Stitch

laughingcreek — Tue, 27 Feb 2018 04:20:42 GMT

I'm not entirely sure what your questions is. The model you posted stitches up just fine. having free edges is just part of the nature of working with surfaces vs solid bodies. when the stitch tool shows edges that are green, it means there are free edges there, but the can be stitched together. when it shows an edge that is red, it means there is a free edge there, but there is nothing next to it to connect to.

Re: Trouble with Stitch

Anonymous — Tue, 27 Feb 2018 09:47:42 GMT

Thanks, it makes a little more sense.

Sorry I didn't make it clear in the first post, but I want this to be a solid body, not a surface body.

This is so I can do some further boolean work on the object in the model workspace.

I thought stitching all surfaces in the patch workspace automatically made it watertight, but obviously I'm missing something?

Thanks again.

Re: Trouble with Stitch

davebYYPCU — Tue, 27 Feb 2018 10:29:59 GMT

Your explanation is correct stitch all will convert to solid,

If you hide the suction cup, then window select all the rest of those bodies, it stitched up for me.

Might help

Re: Trouble with Stitch

Anonymous — Tue, 27 Feb 2018 11:33:44 GMT

Thanks, that's what I was doing but it turns out that I had too fine a tolerance set, making it a larger number fixed the issue 🙂