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

Layer conflict with organic support while using multiple copies and automatic part distribution #10766

Closed
1 of 2 tasks
Sapheus opened this issue Jun 8, 2023 · 4 comments
Closed
1 of 2 tasks

Comments

@Sapheus
Copy link

Sapheus commented Jun 8, 2023

Description of the bug

Hey just made multiple copies of a small part. Normally there is an automatic placement oft the parts. But this time the slicer created a Layer hight conflict. the Parts are too close together because the organic support creates a larger first layer wich results in overlay of the first layer. The solution is to increase the distance between the parts. May be it is necessary to recalculate the distance of the copied and automatically placed Parts depending on the place that is needed to avoid overlapping of the support layer .
Hope I could help a little to ameliorate your slicer ( wich I love ). Thank you for your work .
Wonderful greetings from Saarbrücken - Germany.

Project file & How to reproduce

3 Pictures.zip

Checklist of files included above

  • Project file
  • Screenshot

Version of PrusaSlicer

2.6 beta 4

Operating system

Mac OS Ventura 13.4

Printer model

MK3s upgraded (no Printer Error)

@Mundball
Copy link

Hello Prusa Dev Team,

this "bug" affects all types of support and brim too.

Is there a way to set/change the minimal distance between the objects placed on the bed with automatic placement?

@lukasmatena
Copy link
Collaborator

@Sapheus Thanks for the feedback. This is a long existing issue, which was only made a bit more visible with the organic supports. The 2.6.0-beta4 and later should at least warn about the toolpath collisions after slicing.

@Mundball Yes. Right-click the Arrange icon in the top toolbar.

@Mundball
Copy link

@lukasmatena
Thank you.

@kubispe1
Copy link
Collaborator

Basically, that's a duplicate of #9723 and #11176. We collect this issues here: #316
At the moment there is a notification of G-Code collision. We have a plan to make some improvements in this way. But not now. Closing this issue.
Thanks for discussion

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

No branches or pull requests

4 participants