-
Notifications
You must be signed in to change notification settings - Fork 18
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
chamfer question #86
Comments
Sure, The limitation to it is the presence of crossover edges in the mesh, the current chamfer algorithm cannot deal with crossover. |
Could you help me test this model? |
I can but what operation do you want to apply on it ? what is your problem with that mesh ? |
Thanks a lot.Can you make bevel along a curved line? I want to see if it can handle a more special environment |
Thanks a lot.Looking forward to your good news |
If i want to choose any edge to bevel, how should I do it? |
Just like I wrote in my example, you have to provide a Since your part is imported, it does not carry surface groups, so I added the segmentation step to automatically produce surface groups based on the surface curvature # import your mesh, without surface groups and without connectivity
part = read('/tmp/cop_4_of_clip.stl')
# a STL file does not have connectivity informations, so here we merge similar points and connect triangles together, chamfering will then become possible
part.mergeclose()
# produce surface groups out of surface curvature, edge selection will then become possible
part = reverse.segmentation(part, tolerance=inf)
# execute chamfer
chamfer(part, part.frontiers(0, 1), ('width', 1)) |
Thank you very much for your reply.But I can't test other simple grid models, and I don't know if there is something wrong with my parameters. |
I think there is an issue with subdivided meshes, because it makes points in the middle of straight lines on the chamfered edges |
Is there any better solution?Because the fine mesh model also has a complete topology,How should we solve this problem is better? |
Hello,Why is the offset in the loop assigned multiple times? for b in prox: So how to save during the loop? |
A better solution would be a better implementation in this case, this is a bug I should work on ;) but I need to find time for it.
Don't forget to format the code you post in python code blocks, just as in regular makdown I guess you are speaking of this line (don't forget just a code screenshot doesn't help much to understand where it is in the library). I don't remember why I did this that way. you are right, maybe some accumulator is missing here, something like a |
Thanks a lot. |
If I input a more complex triangular mesh model, can I still chamfer the inner edges?
The text was updated successfully, but these errors were encountered: