Hi,
Thanks for the tip, It’s good advice and this sometimes might be the fastest way to deal with things, but at the same time, it seems very case/job sensitive. I started this topic to highlight a problem, so this command could serve better every user in general case scenarios.
I must point a few things out:
- I already proposed a case/job sensitive workaround to this problem in my post.
- Deleting some geometry and doing it from scratch once again is the most destructive workflow. If any geometry is: referenced in the GH, used in Named Selections, has some attributes, materials, etc. I lose all of that.
- I might be not allowed to modify geometry created by others (I’m not an author of it and I only must unwrap it)
- These are parts of the zipper and they are not aligned to the straight line. I would need to create a curve and control the rotation of the parts as they are distributed along. This task, depending on the scale of the project might be a bit of work. Those geometries might be far more complicated in terms of alignment, shape, number o unique shapes.
- It doesn’t make any sense for the user that we can’t use multiple meshes in the SelMeshEdges command.
- I agree with and follow that advice
I don’t know what kind of task I might need to solve next time with the SelMeshEdges command. I noticed that since it’s not working for multiple meshes at once, it can be very limiting.
I started this topic now, so maybe in the future, this command will be already enhanced so I would not need to look for help or think about any workarounds.