Prusaslicer: overlapping objects do not get sliced correctly

Created on 12 Jun 2019  Â·  10Comments  Â·  Source: prusa3d/PrusaSlicer

Version

Version: 2.0.0+
Build: PrusaSlicer-2.0.0+-201905201652

Operating system type + version

Operating System: Macintosh
System Architecture: 64 bit
System Version: macOS High Sierra Version 10.13.6 (Build 17G7024)

3D printer brand / version + firmware version (if known)

Prusa MK3

Behavior

  • _Describe the problem_

I have added helper discs to a model. They are of course overlapping with the main model. From the preview it seems like it would print overlapping layers.

  • _Steps needed to reproduce the problem_

Open the attached project.

  • _Expected Results_

The model union should be sliced - not models individually. Spots on the layers should only be printed once.

  • _Actual Results_

Screen Shot 2019-06-12 at 04 20 16

_Is this a new feature request?_ No, a bug report.

Project File (.3MF) where problem occurs

NP-FZ100_HolderRemix_001.3mf.zip

All 10 comments

In comparison S3D does it correctly.

Screen Shot 2019-06-12 at 12 51 49

As a workaround, you can arrange them how you want, go to File, Export, Export as STL, then add the exported STL to the plater again. The new STL will be treated as a single object.

@haarp as a workaround I sliced it with S3D :) but I hope this will be fixed in the future

If you want to overlap objects, you should load them as parts of an object.
This is not possible in a simple mode, but it is possible in advanced or
expert mode. Just click the right mouse button at the object in the object
list and load another part.

st 12. 6. 2019 v 22:29 odesílatel Torsten Curdt notifications@github.com
napsal:

@haarp https://github.com/haarp as a workaround I sliced it with S3D :)
but I hope this will be fixed in the future

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/prusa3d/PrusaSlicer/issues/2501?email_source=notifications&email_token=ABMPSI5PIEBUPNBJBF3WJ4DP2FMDXA5CNFSM4HXEZL3KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXRWWFY#issuecomment-501443351,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABMPSI7AAUXGVZFWH5VTQODP2FMDXANCNFSM4HXEZL3A
.

Interesting. Not quite so straightforward but glad it's possible.

The difference between S3D and PrusaSlicer is, that S3D slices the whole plater at once, while PrusaSlicer slices each object separately. This allows PrusaSlicer for example to chose different layer height for each object.

Could you please close this issue?

I've been passively watching this. I don't think that PS does anything wrong here.

If I can put some thought, maybe what's needed is some feedback in the normal view. Similarly to how we change the color to blue when an object doesn't fit, changing the color of the two overlapping objects to something else (red?) would be useful.

This could also pave the way of some form of warning in the future ("overlapping objects detected: convert them to parts?").

@bubnikv That is an explanation of the cause - but frankly speaking not a good reason to close the issue (IMO). The least it should do is detect the overlap and give a warning. Right now it is slicing it in a non-printable manner - which I would argue is the wrong behaviour.

"Add part" works but when I click on "add instance" it duplicates the whole object - not just the selected part.
A work around is to use c&p of the part.

I have to agree with tcurdt.. I don't see any reason overlapping parts should be sliced separately causing overlapping extrusions which can lead to clogs. If there is a reason for it, please enlighten us. It would be better to give a notification when it happens and slice all of it as a single object.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

yschroeder picture yschroeder  Â·  3Comments

TimothyGold picture TimothyGold  Â·  4Comments

Foxtrek64 picture Foxtrek64  Â·  4Comments

ManuGithubSteam picture ManuGithubSteam  Â·  4Comments

karek314 picture karek314  Â·  4Comments