-
-
Notifications
You must be signed in to change notification settings - Fork 519
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: manual seam placement tool #152
Comments
Maybe a new type of modifier mesh (like the pr 728) ? |
Another option would be Kiss like seam settings. In Kiss you specify a sector where kiss is allowed to place seams. Allows you to dither a seam on the back of a part, for example. |
Hi, This would be very useful. I could see it working like the support enforcer and support blocker. Or maybe could use the same UI element as the Place on Face tool and allow you to select faces you dont want the seam on or do for instance? |
@Stephan3, has this actually something to do with where on the outside perimeter the seam should be placed? It looks like the seam gets hidden inside by some perimeter-x-crossing. If that's the case, I would recommend openig a new feature request (only if it does not yet exist) and explain it. Looks very interesting! |
I was not able to place a seam at the inside of a C-Shaped object with kisslicers way: prusa3d#728 (comment) |
Current implementation (in next release):
Maybe later I or someone can modify the slicer to also slice the seam object to be able to have a complex seam object. |
Hi supermerill. I love Slic3r++, very nice job!!
I know slicer++ has "hidden seam" option, but..
Maybe would be nice (and maybe unique feature, does not exist in any slicer) if the
user could "paint" in 3d view the seam position (across Z ). So user can decide where goes seam in each part of a model. Would be something like variable layer height editor. Not sure if is easy to implement.
I did prusa team request prusa3d#2527
and several users liked it.
Time ago, some users tried similar solutions:
prusa3d#728
prusa3d#342
The text was updated successfully, but these errors were encountered: