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

Supports of one object go through another object #316

Open
jindrichbenes opened this issue May 25, 2017 · 6 comments
Open

Supports of one object go through another object #316

jindrichbenes opened this issue May 25, 2017 · 6 comments
Labels

Comments

@jindrichbenes
Copy link

ver. 1.35.0.7

two separate objects

image

@bubnikv
Copy link
Collaborator

bubnikv commented Jul 7, 2017

Supports are generated per object, and collisions of objects are not tested by Slic3r. This is a known issue.

wavexx pushed a commit to wavexx/PrusaSlicer that referenced this issue Sep 21, 2020
but the html pictures as they blurry if I use a %
wavexx pushed a commit to wavexx/PrusaSlicer that referenced this issue Sep 21, 2020
but the html pictures as they blurry if I use a %
@bubnikv bubnikv changed the title Supports go through object Supports of one object go through another object Mar 18, 2021
@ciekawy
Copy link

ciekawy commented May 10, 2022

why not combine/merge objects into one first and only then slice, generate support, raft etc
For anyone who found this issue here - there is one simple solution currently - it is possible to select all the objects, then right-click and choose "Merge" - this will create single raft/support.

Bonus tip - you can always chose undo to rearrange.

@redfast00
Copy link

@lukasmatena I just came across this issue: as an easier alternative to automatically fixing this, would it be possible to detect overlapping gcode and show a warning 'The gcode is overlapping. Merge the models to fix this'? I just had to scrap a large part because of this issue.

@lukasmatena
Copy link
Collaborator

@redfast00 It is a possibility.

@foreachthing foreachthing mentioned this issue Apr 24, 2023
2 tasks
@kubispe1 kubispe1 mentioned this issue May 30, 2023
2 tasks
@morphias2004
Copy link

+1

7 years on and still an issue. :(

@el-bart
Copy link

el-bart commented Oct 5, 2024

there are 2 other, "interesting" side effects / fallouts of this bug, namely:

  • when using --duplicate cmd line option objects are auto-positioned incorrectly, causing collision with supports
  • when running from cmd line, slicing ends up with SEGV

see #13464 (closed as duplicate) for more details.

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

7 participants