-
-
Notifications
You must be signed in to change notification settings - Fork 104
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
[Bug] Suction cup resolution is not sucessful #756
Comments
This is your first time submitting an issue with UVtools 🥳Please review your issue and ensure that the submit template was followed, the information is complete, and not related to any other open issue. It will be reviewed shortly. Debugging is very important and make the program better. Thanks for contributing and making the software better! 🙌 |
Addendum. I want to be clear that the issue is with the program "thinking" that the suction cup has been resolved. If you print this, for example, directly on the plate it will make a suction cup. However, if you use a raft and loose supports then the holes in the model work as vents. Based on the fact that this probably doesn't need to be resolved in UVTools I'm going to preemptively mark this as closed. However, should someone with the desire and coding skills to do this then it could be added as a self check. i.e. run the suction cup detection again and if not resolved tell the user. |
Suction cups and islands fix is an attempt, it does not guarantee it correctness nor success. If issue goes down to plate it won't drill and will keep detecting. Additionally you should not try to fix stress tests or any other tests that are design to print as is it. |
System
Printer and Slicer
Description of the bug
Using the Phrozen XP finder STL Lychee produces a reasonably sliced files.
When loaded into UVTools it correctly detects a suction cup but subsequently "drilling" produces a product that would not ameliorate the problem. i.e. you can repeat the suction cup detection again of the drilled/corrected file without fail.
How to reproduce
Files
No response
The text was updated successfully, but these errors were encountered: