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

Organic supports do not create interfaces other objects in plate (and they become fused) #10616

Closed
2 tasks done
paurullan opened this issue May 19, 2023 · 2 comments
Closed
2 tasks done

Comments

@paurullan
Copy link

Description of the bug

hello there,

I was preparing a big plate of multiple objects and found that organic supports getting generated upon other objects in plate (and they become fused). I have the feeling that the slicer is not creating the interface on the already in-place object.

This is a screenshot of my multi-object.

I prepared a minimal example with two discs and it happens there too.

If this is actually expected do not hesitate to tell me and I will take a look on how to expand the documentation.

Project file & How to reproduce

prusa-issue_supports-over-object.3mf.zip

image

image

Checklist of files included above

  • Project file
  • Screenshot

Version of PrusaSlicer

PrusaSlicer-2.6.0-beta2+linux-x64-GTK3-202305170854.AppImage

Operating system

Ubuntu 23.04 with 6.2.0-20-generic

Printer model

Artillery Genius (non-pro)

@neophyl
Copy link

neophyl commented May 19, 2023

Duplicate of many issues. For example #10451 . The primary earliest one is #316 from May 2017.

Prusa Slicer has always worked this way, its just that organic supports with their larger base sizes have highlighted the issue and made it more apparent to more people.
Each object is sliced independently. You can even place 2 objects over lapping and it will do the same, no warning etc. If you do so you will have a 'very bad day (tm)'. You the user are expected to place objects accordingly.

You can combine objects into one, in which case the supports generated will respect the other Parts now they are a single Object.

It is apparently being discussed internally as it has resulted in so so many raised issues, see #10127 (comment)

@kubispe1
Copy link
Collaborator

Thanks, I am closing the issue as a duplicate

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