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

Absurd toolhead movements after last top layer when slicing model in angled position causing printhead to crash into other objects #13826

Closed
1 of 2 tasks
3dpr-foss opened this issue Dec 22, 2024 · 2 comments
Labels

Comments

@3dpr-foss
Copy link

Description of the bug

When trying to slice the following model (main part / bin) https://makerworld.com/de/models/599038#profileId-521158 positioned laying on a small corner (like in the provided 3mf) so that the bin is printed at an angle and needs only minimal support the slicer generates absurd tool head movements after the last layer way beyond the printers dimensions which sometimes even can cause it to crash into other objects on the print bed...

The path is generated rather erratic, so slicing can either result in the following path (visible in the gcode viewer)
2024-12-22_18-44

crashing into other objects or the print bed - or some other movements also way beyond the print volume like moving to X: 406.745, Y: 0.031, Z: 83.400

Project file & How to reproduce

This happens with the stock settings of the printer (MK4 with InputShaper) and print profiles (ege. 0.2 Structural) when slicing the model as described above, the movements are seemingly generated random on every time hitting the 'Slice' button, but at least for me always results in generated movements beyond the printers dimension and sometimes even back through other objects on the print bed...

Checklist of files included above

  • Project file
  • Screenshot

Version of PrusaSlicer

PrusaSlicer-2.9.0+flathub.org

Operating system

Linux Mint 22

Printer model

Prusa MK4

@SachCZ
Copy link
Collaborator

SachCZ commented Dec 27, 2024

Hello, thank you. I reproduced this and it is a bug. I have created and issue in our internal system (SPE-2633).

@Jan-Soustruznik
Copy link
Collaborator

Closed as solved by the new release of 2.9.1-Alpha1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants