-
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
With autospeed on and either brim or skirt (or both) present, the first layer is too fast. #2945
Comments
Thanks for the reference. I'm still processing the information, but I wouldn't dismiss skirt/brim link completely as there's clearly a correlation. Also this got my attention — But, as I said, I'm still processing the information. The most reasonable thing to do is to look into code, but last time I tried to make it work I lost my fight with perl, cpan and macports and I don't want to look at the code that I can't sensibly change :) Need to try again… If I get time… |
I also experienced this today while trying autospeed. First layer was much faster than my 30mm/s setting for first layer. Any news or ideas? |
I find Autospeed currently ignores % for first layer, but honors hard numbers like 30mms. First layer set to 45mms with autospeed (ignore the title I put 30mms in incorrectly) First layer set to 50% with autospeed and a later layer to show its about the same speed as the first layer I am not commenting on what I think or whether thats desired behavior just noting what I am finding as current behavior. |
Thank you for the bug report. I fixed this. First layer speed was not applied over autospeed when set as percent. |
I have tried the autospeed feature (in the 1.2.9 Slic3r) and it turns out that it prints the first layer at a higher speed if either brim or skirt or both are enabled. I reproduced it with the 0.5mm-thin-wall STL.
Here are some fragments of G-code generated. Courtesy of
grep -e Z0.24 -e Z0.48 -e F 0.5mm-thin-wall.gcode
. Layer height is 0.24.This one is without skirt and brim:
The first reasonable F (1044.685) appears after Z0.24
This one with a skirt:
The first 1044 rate is at Z0.48, with a nice F2564 before that. The same and brim:
Nothing less that 4800 before Z0.48.
I don't know if it's a bug or a feature, I'm relatively new to the whole thing, but it does look like a bug to me? Alternatively, I'm doing something wrong to trigger this behaviour. The configuration (from .gcode tail) looks like this:
The text was updated successfully, but these errors were encountered: