Skip to content
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

First Layer Speed modifier partially ignored if auto-speed enabled #256

Closed
kizza42 opened this issue May 29, 2020 · 2 comments
Closed

First Layer Speed modifier partially ignored if auto-speed enabled #256

kizza42 opened this issue May 29, 2020 · 2 comments
Labels
bug Something isn't working as intended fixed for the next version That means that you should be able to test it in the latest nightly build

Comments

@kizza42
Copy link

kizza42 commented May 29, 2020

Version

2.2.50

Operating system type + version

Win10

3D printer brand / version + firmware version (if known)

Tevo Little Monster with Klipper

Behavior

It seems the First layer speed modifier is partially ignored in this version, The brim prints at this speed but first layer of the model does not. This issue does not present in PrusaSlicer
2020-05-29_17-38-31
slic3r++_2020-05-29_17-38-38

Project File (.3MF) where problem occurs

Extrusion_Test.3mf.txt

@supermerill
Copy link
Owner

supermerill commented May 29, 2020

This only happens if you let the auto-speed algo do the job. Did you let some speed box to 0 (perimeters, solid infill,...) in prusa also?

@supermerill supermerill changed the title First Layer Speed modifier partially ignored First Layer Speed modifier partially ignored if auto-speed enabled May 29, 2020
@supermerill supermerill added the bug Something isn't working as intended label May 29, 2020
@kizza42
Copy link
Author

kizza42 commented May 29, 2020

The same settings in Prusa seem to honour the first layer speed.

2020-05-29_18-38-14
2020-05-29_18-37-25

@supermerill supermerill added the fixed for the next version That means that you should be able to test it in the latest nightly build label May 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working as intended fixed for the next version That means that you should be able to test it in the latest nightly build
Projects
None yet
Development

No branches or pull requests

2 participants