-
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
Division by zero when changing infill density #3617
Comments
gege2b
changed the title
Division by zero
Division by zero when changing infill density
Dec 14, 2016
Make absolutely sure that your model is manifold. "Unable to close loop"
errors are usually as sign that something else is wrong.
The illegal division by zero, however, is definitely related to the
bounding box issue.
"Nothing unreal exists." - Kiri-kin-tha's First Law of Metaphysics.
…On Wed, Dec 14, 2016 at 5:05 PM, gege2b ***@***.***> wrote:
Version
current dev (as of 3a3b24e
<3a3b24e>
)
Operating system type + version
Debian 8.6 x64
Behavior
It's an issue pretty similar to #3589
<#3589> except one thing : I don't
have to switch to 3D preview for Slic3r to hangs.
All I do is load the STL (witch have some errors but I don't think it's
the problem here), let the background slicing to complete and simply change
infill % from default 20 to 25% (or 30 or 15 or whatever). It hangs
instantly.
weirdly, if I simply change the type of infill it doesn't hangs
So, right now, I just can't change the infill %
Anyway If I change the infill density and then load a model, it's all
right.
(note : the four folowing lines may vary or simply vanish. The last is always here.)
Unable to close this loop having 26 points
Unable to close this loop having 167 points
Unable to close this loop having 1 points
Unable to close this loop having 4 points
Illegal division by zero at /home/gege/3Dprint/Slic3r/lib/Slic3r/GUI/3DScene.pm line 379.
STL/Config (.ZIP) where problem occurs
STL : http://www.thingiverse.com/thing:1727943 (my daugher loves Skye ^_^
) in this case. But I also tried with other error-free STLs with same
results
Default config
####Note : Maybe this is the same issue than the one mentioned above, but
it appears when doing something else, that's why I opened a new issue.
Don't hesitate to close it if it was unnecessary
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#3617>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAB8CjDVAIr7xW85jsOZua0B0HX2346wks5rIHZIgaJpZM4LNhdB>
.
|
Yeah, that's why I tested other STL witch are manifold (no error and already printed in the past) OK, so except for the non manifold and the "loop" errors witch are unrelated, I still get the division by zero error. I'll close this issue as it's a duplicate of #3589 (possibly fixed by #3591 I guess) , feel free to reopen it if needed for any reason |
Allright, problem gone since #3591 has been merged :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
current dev (as of 3a3b24e )
Operating system type + version
Debian 8.6 x64
Behavior
It's an issue pretty similar to #3589 except one thing : I don't have to switch to 3D preview for Slic3r to hangs.
All I do is load the STL (witch have some errors but I don't think it's the problem here), let the background slicing to complete and simply change infill % from default 20 to 25% (or 30 or 15 or whatever). It hangs instantly.
weirdly, if I simply change the type of infill it doesn't hangs
So, right now, I just can't change the infill %
Anyway If I change the infill density with empty plater AND THEN load a model, it's all right.
STL/Config (.ZIP) where problem occurs
STL : http://www.thingiverse.com/thing:1727943 (my daugher loves Skye ^_^ ) in this case. But I also tried with other error-free STLs with same results
Default config
####Note : Maybe this is the same issue than the one mentioned above, but it appears when doing something else, that's why I opened a new issue. Don't hesitate to close it if it was unnecessary
The text was updated successfully, but these errors were encountered: