Chaotic Weirdness - Overgrown Walls #1049

Closed
OhmEye opened this Issue Mar 13, 2013 · 7 comments

Projects

None yet

3 participants

@OhmEye
OhmEye commented Mar 13, 2013

I'm not sure how to title this one, but when slicing a vase object with a single perimeter, zero infill and no top layers instead of getting a single perimeter wall the result is chaotic mess. A bisect shows that the trouble started with 0eecf33

Prior to this commit the results are ok:
Good Results

Starting with this commit the results are bad:
Bad Results

The STL and settings used:
http://ohmeye.com/download/debug/debug_031213/DoubleInsideout100_fab.stl
http://ohmeye.com/download/debug/debug_031213/bisect_config.ini

I haven't tried narrowing down any settings that may trigger this, it's an STL that has been run through netfabb and that I've sliced before and never had trouble with before this commit.

@alexrj
Owner
alexrj commented Mar 18, 2013

@OhmEye, I fixed this. Can you confirm? Thank you!

@alexrj alexrj added a commit that referenced this issue Mar 18, 2013
@alexrj Bugfix: artifacts near walls. #1049 0b81911
@OhmEye
OhmEye commented Mar 18, 2013

Sorry, it's not fixed. I get same results with the same test file and config.

@beanz
Collaborator
beanz commented Mar 26, 2013

This might be to do with the solid-infill-below-area setting. I think this should be zeroed automatically if fill-density is 0 but it doesn't seem to be. Does setting this to zero fix it?

@alexrj alexrj added a commit that referenced this issue Mar 26, 2013
@alexrj Bugfix: solid-infill-below-area wasn't ignored when fill_density = 0,…
… causing solid layers here and there. #1049
aae9625
@alexrj
Owner
alexrj commented Mar 26, 2013

@beanz, thank you – that was a very useful hint and I was able to fix it and add a unit test for it.

@OhmEye, does this fix your issue too?

@alexrj
Owner
alexrj commented Mar 30, 2013

@OhmEye, I believe my latest commit fixes this issue. I tested with your model and it looks to be clean as expected. Do you have a chance to confirm?

@alexrj alexrj added a commit that referenced this issue Mar 30, 2013
@alexrj Bugfix: is_printable() wasn't discarding narrow ring-shaped top/botto…
…m surfaces because it was only considering the contour. This caused extra shell material even in hollow prints. #1049
04d2231
@OhmEye
OhmEye commented Mar 30, 2013

The bug is not only fixed, the result is now cleaner than before it appeared. The paths I see now look perfect in a viewer. Good job!

Compare to the first test image, no more noisy interior path, this is how it looks now:
Fixed result

@alexrj
Owner
alexrj commented Apr 11, 2013

@OhmEye, forgot to say thank you for testing!

@alexrj alexrj closed this Apr 11, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment