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

1.33.3: skirt can become a few kilometers large, and is not always printed first #122

Closed
DrLex0 opened this issue Feb 11, 2017 · 8 comments

Comments

@DrLex0
Copy link

DrLex0 commented Feb 11, 2017

Version

1.33.3

Operating system type + version

Mac OS X 10.11.6

Behavior

  • When using more than one raft layer, the skirt extends a few kilometers outside the print bed. When using support material without a raft, the skirt is not printed as the very first thing.
  • Example: use attached STL file with attached config.
  • Expected results: the skirt is printed around the object and stays on the print bed. The skirt is always printed first.
  • Actual Results: the skirt takes various unexpected shapes and runs off the print bed towards the other side of town. When disabling raft layers, the support material is printed before the skirt.

No raft:
noraft
One raft layer:
raft1layer
Two raft layers:
raft2layers

STL/Config (.ZIP) where problem occurs

ConfigAndSTL.zip

@bubnikv
Copy link
Collaborator

bubnikv commented Feb 13, 2017

When using support material without a raft, the skirt is not printed as the very first thing.

Are you sure about that? It seems to me that the skirt is printed as the first thing, if the raft is disabled.

@DrLex0
Copy link
Author

DrLex0 commented Feb 13, 2017

Are you sure about that? It seems to me that the skirt is printed as the first thing, if the raft is disabled.

Yes, attached is a GCode file with the .ini that generated it. The support material is printed before the skirt, unlike in previous versions.

RaftVsSkirt.zip

@Saij
Copy link

Saij commented Feb 13, 2017

I can also say that the support is printed before the skirt and the model.
For me it seems that the support is always a layer below the rest of the model. GCode.ws and Pronterface show the support on a seperate layer than the rest of model (so it is always support, then model, then support, then model and so on).

Tested yesterday with model http://www.thingiverse.com/thing:986652
Standard Prusa settings, 100% infill, support enabled and no raft.

@nebbian
Copy link

nebbian commented Feb 15, 2017

I noticed the same thing this morning regarding the skirt being printed after the support (and possibly brim). This is different to all previous versions of Slic3r that I've used.
Perhaps the first layer height isn't being applied to the support and brim?

@bubnikv
Copy link
Collaborator

bubnikv commented Feb 15, 2017 via email

@bubnikv
Copy link
Collaborator

bubnikv commented Feb 15, 2017

Fixed the order of a skirt, raft, support & object on the 1st layer. This is a new issue after I switched the order of support and object extrusions being printed at the same Z height. By the way, are there pros / cons to printing the support before / after an object? My gut feeling is, it is better to print the support first due to the overhangs. 3549021

Fixed (hopefully) the issue with the skirt sticking out of the print bed by re-writing the suspicious part from Perl to C++.
3d11d1a

And finally, I have fixed a handful of bugs in the rafts, which were again introduced with the new C++ supports.
f5e4026

@DrLex0
Copy link
Author

DrLex0 commented Feb 15, 2017

By the way, are there pros / cons to printing the support before / after an object? My gut feeling is, it is better to print the support first due to the overhangs.

It doesn't really matter I think, as long as the support is there when the next layer is printed on top of it… But intuitively I also prefer support first.

@bubnikv
Copy link
Collaborator

bubnikv commented Feb 15, 2017

But intuitively I also prefer support first.

Good, because the old slic3r did it vice versa, the object first.

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

4 participants