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
Bad support generation with default settings in Alpha 3 #5209
Comments
Support enforcers and blockers do not work unless they intersect with the model, thats the way they are supposed to work. They aren't keep out areas in the case of blockers. I downloaded it and used the new support painting function, but I just used autoset by angle to 35 degrees which is sufficient for this model. The supports look reasonable to me, although as they are printing on top of parts of the model I would expect them to be difficult to remove on that side from experience. I also did try it with a slab support enforcer and the pattern of supports was similar but did grow outward slightly from the painting as its also supporting the part more on the less steep angles too as the slab is less discriminate. PS_alpha4_WyvernPhoneStand.zip I also tried the default quality at 0.2 and 0.15 profiles with support everywhere option (which changed the detect bridging setting via the pop up as usual) and the support on that while more than when using an enforcer still wasn't doing anything like in your picture. Just noticed that you are on mac, my tests were done on win 64 so there's the possibility its OS specific behavior. |
thank you for trying to reproduce. i couldn’t figure out what in the model was making prusa think the dead area in front of the head needed support. i suspect there’s a bad detection happening somewhere which results in an infinity and the result is presumption that supports are needed to the edge of the bounding box in that direction. given that, it could be graphics card specific or driver specific. i don’t know that i’m qualified to diagnose that though. |
@thetrebor Would you please attach a 3MF so we can reproduce? |
Fresh install, default profiles, added default "supports everywhere" |
Thanks, I can reproduce the issue. There is a numeric issue in one of the algorithms in succession to the Clipper offsetting library creating tiny self intersections in an offsetted contour. I have not seen this kind of issues being reported for along time though. út 24. 11. 2020 v 19:30 odesílatel Robert Maefs <notifications@github.com> napsal:
…
WyvernPhoneStand.3mf.zip <https://github.com/prusa3d/PrusaSlicer/files/5591942/WyvernPhoneStand.3mf.zip> [image: Screen Shot 2020-11-24 at 1 29 47 PM] <https://user-images.githubusercontent.com/305910/100136493-2012c480-2e59-11eb-89dd-12f8ee4eb1fc.png> Fresh install, default profiles, added default "supports everywhere" — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#5209 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABMPSI7Q23CEQJ36LM3MJ3LSRP3VFANCNFSM4T56KMPQ> .
|
that seems reasonable. I saw that some of the cusps on the model were being supported despite having no overhangs whatsoever. it appeared to be "self intersecting" "non manifold" style problems so my first thought was to repair the model. Nice to know I'm not crazy. Good luck tracking it down! |
For my reference, the issue is |
2.2.0+win64 |
Version
2.3.0-alpha3+
Operating system type + version
OSx 10.15.7
3D printer brand / version + firmware version (if known)
Stock prusa mk3s
Behavior
Use this model: https://www.thingiverse.com/thing:4128842
Use default profiles. Tried 0.2 and 0.1
Support blocker does not work unless it is in contact with the model.
Repaired the model using ADMesh and did not change outcome
Changed support overhand angle and did not change outcome
Model appears OK to me. Didn't see any loose geometry.
The text was updated successfully, but these errors were encountered: