-
Notifications
You must be signed in to change notification settings - Fork 2k
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
No support generated #114
Comments
This is certainly weird. I am collecting a change log, I will release the beta binaries tomorrow. |
I repeated the support test with the new released beta, same situation. I'm using default settings for supports and tried multiple stl files - nothing. Realy strange.. |
Would you please provide
|
Here they are: |
Thanks, I can reproduce it now. It is something about your configuration,
that this slic3r does not like. I will look into it.
…On Fri, Feb 10, 2017 at 7:09 PM, Sebastianv650 ***@***.***> wrote:
Here they are:
Example.zip <https://github.com/prusa3d/Slic3r/files/767459/Example.zip>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#114 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AFj5Iyc6mLKN0VnpTwanCqAoffIe-Wy_ks5rbKf3gaJpZM4L8i6Q>
.
|
The problem is in the setting of the first layer height (100% of the normal layer height). There is a bug in the new supports, which does not work with the percent value of the first layer height correctly. If you enter 0.2 into the first layer height field, the supports will work. I will fix it soon. Thanks for the bug report. |
when a first layer height was set in percents.
Fixed by 8d6acd2 |
Version
Creation date of this one
Operating system type + version
Win10 64bit
Behavior
No matter witch stl I choose and what options I set (overhang threshold, pattern, ..) in the support section, there is no support structure generated. I also checked the gcode output to see if it's only a visualisation thing - it isn't.
I hope it's not again a mistake intruduced by myself, but I don't think so because rest of slic3r is now compiling and running great.
The text was updated successfully, but these errors were encountered: