hi R_KRI, yes I understand what you mean. I don’t know of a good and easy solution to this problem.
Ideally it would not use loose edges for marking the sewing seams, it was just the easiest way I could think of to quickly add the feature.
I would prefer to be able to mark two sets of edges as a seam pair, and use that, but i’m not sure of a good way to do this.
I’m not sure if I’m doing something wrong or if the patch is not working correctly. Lately, I haven’t been able to make ‘Shrinking’ work with sewing. I’ve tried by adding vertices to a vertex group - a loop or two - with a weight of 1, which I’ve added to the 'Shrinking field in the cloth section. When I run the simulation, I see no effect on the vertices in the group. All vertices behave the same, with no shrinking. I’ve tried with various values for min/max and various values for velocity and for gravity. (This with a build from the last few days. I don’t remember the exact build number)
@thesleepless. I hope you get some time soon to continue work on the patch.
ahh i know there was a bug at some point where it wouldn’t do the vertex group stuff unless you had pinning enabled. try activating that option. that should be fixed in a newer patch.
i have a question regarding the edges that we have to create between the cloth panels that are to be joined - is there a way to create them all at once or do i have to select pairs of verts in turn and create the edges one by one?
You can select the edges with the verts you want to join. Press w, the LoopTools and Bridge. This should leave the faces created selected. Then x, faces only.
thanks for the help! unfortunately i’m not there yet (told you i 'm new to Blender :)) i select the edge loops, hit ‘w’ but i get a Specials menu and there is no Bridge tool. i searched for Bridge with the Space Bar but it returns nothing
Ah, right. I thought looptools was in Blender as standard if you use a recent version of blender from Graphical.org. Not sure, but you may have to enable it in user preferences, in the add on tab? Maybe someone can verify or.correct that? Have a look and see if you find it.