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

improper 1st layer support material overlap object #2598

Open
ohthetrees opened this issue Jul 4, 2019 · 4 comments
Open

improper 1st layer support material overlap object #2598

ohthetrees opened this issue Jul 4, 2019 · 4 comments
Labels

Comments

@ohthetrees
Copy link

Version

PrusaSlicer-2.0.0+-201905201652

Operating system type + version

MacOS 10.14.3

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

Prusa MK3S

Behavior

  • Describe the problem
  • Steps needed to reproduce the problem
    • If this is a command-line slicing issue, include the options used
  • Expected Results
  • Actual Results
    • Screenshots from PrusaSlicer preview are preferred

I'm using multiple materials the old fashioned way: on a single extruder MK3S I set up multiple extruders in Prusaslicer and issue a M600 Gcode command on tool change. Works great. I use it to print inlays into the first couple of layers of an object. This technique relies on multiple stls that fit together like puzzle piece, then I assign different "extruder" to each stl.

Problem is that if I have support material, these weird little spurious pieces of support material get put down on the first layer here and there. When printing one stl, they tend to be harmless, but aesthetically annoying. But in my situation, these little random squiggles of support material, which don't support anything or serve any function, ruin my inlay effect.

As far as I can tell, two separate problems are combining to make me miserable.

A) For some reason Prusaslicer will make little random bits of 1st layer support material, even if they don't support anything.

B) Prusaslicer doesn't respect another object when making support material. I found #316 which seems to be a similar bug, but guys, it is from 2017, and still no resolution.

I'm filing this as a new bug, because #316 alone wouldn't cause this problem for me, my problem A is also necessary.

Please take my complaint in good spirit. I really like Prusa pinters and Prusaslicer. Thanks for all the hard work!

IMG_8007
Screen Shot 2019-07-04 at 12 27 20 AM
Screen Shot 2019-07-04 at 12 29 37 AM

Project File (.3MF) where problem occurs

This is not a "real" file I use, the model has some problems, but it demonstrates the issue I'm talking about.
Demo support problem.3mf.zip

@supermerill
Copy link
Contributor

As a short-term fix for this "bug", you can use support enforcer to exclude the area where you don't want them (the 'bits').

@ohthetrees
Copy link
Author

Unfortunately, support blockers don't block the "bits". I tried on both the stl that needs the support (the case) and the stl that is interfered with (the "e" stl).

@neophyl
Copy link

neophyl commented Jul 5, 2019

Merril said support ENFORCERS not blockers. There is a world of difference. I have attached a modified version of your 3mf with a single support enforcer as an example for you to work with.

Essentially you turn off automate support and then put enforcers for the area where you need it. You can play around with the size of the enforcers to fine tune the area. They are much better than blockers for some reason. Since the betas and now 2.0 allowing much easier placement of modifiers Ive stopped using blockers completely and just use enforcers.

image

As you can see no squiggly bits.

Demo support problem_ENFORCERS.zip

@ohthetrees
Copy link
Author

Thanks @neophyl, this workaround worked for me. Of course, I think there is an underlying bug that should be addressed, but at least I can get my desired result.

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

4 participants