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

Slicer not respecting 'Initial Layer Print Speed' for all initial layer perimeters #17602

Open
grilparto opened this issue Dec 11, 2023 · 1 comment
Labels
Status: Duplicate Duplicate of another issue. Type: Bug The code does not produce the intended behavior.

Comments

@grilparto
Copy link

Cura Version

5.5.0

Operating System

Windows 10

Printer

Ender 5 Plus with Klipper

Reproduction steps

  1. Sliced a model with 'Initial Layer Print Speed' set to 30mm/s. Outer (and Inner) Wall Speed set to 150mm/s.
  2. Previewing 1st layer, some perimeters on layer 1 are set to print at 150mm/s instead of 30mm/s.
  3. Attempting to print, the printer does indeed print some of the initial layer perimeters at 150mm/s.

Here is a link to the model I'm trying to slice: https://www.thingiverse.com/thing:5384951

Actual results

Slicer preview shows some initial layer perimeters are set to print at 150mm/s instead of 30mm/s.

Expected results

All surfaces and perimeters of initial layer should print at the Initial Layer Print Speed (30mm/s).

Add your .zip and screenshots here ⬇️

3mf file is over 25MB. Shared here.

Screenshot of first layer with some perimeters printed at incorrect speed

@grilparto grilparto added Status: Triage This ticket requires input from someone of the Cura team Type: Bug The code does not produce the intended behavior. labels Dec 11, 2023
@Asterchades Asterchades added Status: Duplicate Duplicate of another issue. and removed Status: Triage This ticket requires input from someone of the Cura team labels Dec 11, 2023
@Asterchades
Copy link
Collaborator

This would appear to be a duplicate of #17210. While it's buried a little bit in there, the solution for this particular model is to set the Top Surface Skin Layers to zero (0).

Note that while the model itself is faulty this does not appear to have any impact on the issue. Correcting the faults halves the file size and speeds up slicing considerably, but otherwise has no effect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Duplicate Duplicate of another issue. Type: Bug The code does not produce the intended behavior.
Projects
None yet
Development

No branches or pull requests

2 participants