-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
FIX: check bounds for fill->min_spacing causing fill_density<100 to abort #4524
FIX: check bounds for fill->min_spacing causing fill_density<100 to abort #4524
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Revert this change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will take a closer look over this tomorrow and (probably) commit it. I apologize for not getting to it from now.
No need to apologize :) Like I said, I commited to the wrong branch, as time-stamping is used for my debugging and cross-referencing. Nonetheless, I guess it would not harm, if it could be added upstream (maybe as transversal feature). With that said, I wouldn't know why that raised the red flag, because the travis output below:
mentions wrong scope, but it complies to my compiler settings. From the same travis output, I see that I could rewrite to a more portable/compatible version, but like I said it was just for my debugging :) Sorry for any inconvenience :) Always learning :) |
If there's an exceptional condition, should use exceptions instead.
I've made some changes to your PR to instead set a relatively sane value for the config width. You'll still get credit for the merge (and spotting the issue in the c++ CLI toolchain). I made a similar fix on the perl side a few months ago (that I just remembered when I saw your PR). The root cause here is that the config code assumes that the infill width gets calculated as per flow (which doesn't exist here). I think we will want, going forward, to refactor Flow so that the auto logic behaves appropriately for SLA/DLP/. I use a LCD mask on my own printer. |
Yeah, I also thought that proper bounding was the way to go :) The way I see it (and I could be wrong), but if the But, like you said, if the problem is upstream ( And thanks, for further investigating the issue :) |
In that code path, nozzle_width doesn't exist ;) |
Fill->min_spacing
was being initialized to 0, due to theinfill_extrusion_width
being set to 0 in the config file.nozzle_diameter
.Tests
For convenience, I had the result of some tests:
Infill_extrusion_width = 0.5
:Infill_extrusion_width = 0.1
:Infill_extrusion_width = 2.1
:Infill_extrusion_width = 0.01
: Was taking too long.This lasts two values highlight the importance of convenient bounding, but for now, I will leave as it is, as it suits my needs.