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

[Bug ] big brims collides with waste tower on mmu prints by using auto arrange #9309

Closed
2 tasks done
Kyrunix opened this issue Dec 21, 2022 · 2 comments
Closed
2 tasks done

Comments

@Kyrunix
Copy link

Kyrunix commented Dec 21, 2022

Description of the bug

Greetings everyone,
if you print a small multi color object with mmu2s, enable a big brim and use the auto arrange option, the brim can collide with waste tower.

Add multicolor object, in this case basic cube with a 15mm brim
grafik
Use auto arrange to arrange objects
grafik
Brim collides with waste tower basement
grafik
first layer view
grafik

This cube is just an example, because it happend by every object.

I think the "brim width"-parameter need to be added to auto arrange method.

Project file & How to reproduce

brim-collision.zip

Checklist of files included above

  • Project file
  • Screenshot

Version of PrusaSlicer

2.5.0+win64

Operating system

Windows 10 Professional

Printer model

Mk3s+ with MMU2s

@Kyrunix Kyrunix changed the title big brims collides with waste tower on mmu prints by using auto arrange [Bug ] big brims collides with waste tower on mmu prints by using auto arrange Dec 21, 2022
@lukasmatena
Copy link
Collaborator

Arrange function accounts for brim and skirt since 2.6.0-alpha6. Closing.

@Snuff1eupagus
Copy link

Snuff1eupagus commented Apr 26, 2024

It is already possible to control your brims, since 2021. even though this individual knows how, they have not shown this yet, however this may help.

https://www.youtube.com/watch?v=dhsbMmosbLU&t=4s

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

No branches or pull requests

3 participants