Slic3r 0.5.7 Hello everybody, this is to let you know that 0.5.7 is out and ready for download on http://slic3r.org/. You can read the list of changes on the home page, however the key news are better solid surfaces (they were a bit sparse in 0.5.6) and a "Slice and save as..." command to choose the output filename. Many other things, though. Enjoy! https://reprap.org/forum/read.php?263,110934,110934#msg-110934 Fri, 07 Aug 2026 21:13:55 -0400 Phorum 5.2.23 https://reprap.org/forum/read.php?263,110934,114954#msg-114954 Re: Slic3r 0.5.7 https://reprap.org/forum/read.php?263,110934,114954#msg-114954
So i guess it's just some bug with the lastest experimental version of Pronterface, I logged this issue on Kliment's Printrun Github page.

Edit: Kliment replied to the issue I logged and said this problem has been fixed in the current github version, but he just hasn't made a binary of it yet.]]> daufhammer Slic3r Sat, 21 Jan 2012 14:57:31 -0500 https://reprap.org/forum/read.php?263,110934,114946#msg-114946 Re: Slic3r 0.5.7 https://reprap.org/forum/read.php?263,110934,114946#msg-114946
When i open the gcode file in Pronterface it generates all the estimates, but doesn't seem to finish, it leaves off the total duration time at the end...(I haven't integrated Slic3r with Pronterface yet, just using them separately).
It looks like this...

449.243 mm of filament used in this print

the print goes from 63.6 mm to 136.4 mm in X
and is 72.8 mm wide

the print goes from 63.27 mm to 136.66 mm in Y
and is 73.39 mm wide

the print goes from 0.48 mm to 15.28 mm in Z
and is 14.8 mm high

Estimated duration (pessimistic): .... estimating ....
layer z: 0.0 will take: 00:00:02
layer z: 0.48 will take: 00:01:42
layer z: 0.88 will take: 00:00:42
...
layer z: 14.48 will take: 00:00:10
layer z: 14.88 will take: 00:00:10

When i open gcode sliced with SF it finished loading it completley and shows a total duration at the bottom and generates a gcode preview.
like this
...
layer z: 14.48 will take: 00:00:10
layer z: 14.88 will take: 00:00:10
Total Duration:
00:09:35]]> daufhammer Slic3r Sat, 21 Jan 2012 14:16:41 -0500 https://reprap.org/forum/read.php?263,110934,114942#msg-114942 Re: Slic3r 0.5.7 https://reprap.org/forum/read.php?263,110934,114942#msg-114942
The only issue I have came across is if I am trying to generate Gcode from any STL that has 3D text in it.

For example The Scooby Snack cutter [www.thingiverse.com]

If I load it into Printer Interface, skeinforge slices it up and I can flick through the layers and see it is all fine and prints okay.

If converted with Slic3R it misses letters or starts different letters at different heights?


Any ideas

Cheers

Sean.]]> CLaNZeR Slic3r Sat, 21 Jan 2012 14:09:17 -0500 https://reprap.org/forum/read.php?263,110934,114881#msg-114881 Re: Slic3r 0.5.7 https://reprap.org/forum/read.php?263,110934,114881#msg-114881 Sound Slic3r Sat, 21 Jan 2012 04:50:14 -0500 https://reprap.org/forum/read.php?263,110934,114871#msg-114871 Re: Slic3r 0.5.7 https://reprap.org/forum/read.php?263,110934,114871#msg-114871
Gcode generated by SF or SFact show up just fine though. It seems like other people are able to view Slic3r gcode in Pronterface, so it's probably something wrong on my end. Any thoughts on what could be causing this?]]> daufhammer Slic3r Sat, 21 Jan 2012 04:06:27 -0500 https://reprap.org/forum/read.php?263,110934,112726#msg-112726 Re: Slic3r 0.5.7 https://reprap.org/forum/read.php?263,110934,112726#msg-112726
I am the guy who modifed SF to be SFACT. I actively use slic3r myself now.


I think that Slic3r is a great piece of software and is covering its shortcomings in an unbelivable pace.
It has missing features and probably some mistakes (have not encountered anything vital so far) but bad dimensional accuracy is not one of them.
I recently printed an extruder and the fit for the bearings (Z-plane) and the fit for M5 nuts was perfect.

I am assuming that you are using the acceleration option in SFACT. That means that you have different (and lower) E-acceleration for your perimeters which will give you better accuracy in critical parts like the belt pulley.

have a look at the picture below:
That is a slic3r piece.

P97999300.jpg
Kimden Actions Prusa

(there also other pictures on picasa)
The most part of that pulley was printed with a E accelaration of 500. (feeds were very high for that part to magnify the difference.. 60mm/s perimeters and 100mm/s fill). Then I sent a command M201 E10 to lower the E acceleration.

See how it changed the looks and actually the dimensions.. The print was not interrupted btw.

So please always consider that if most people have it right and its not working for You that your settings are to blame..

Thanks to Sound(Alex) for the cool work..]]> ahmetcemturan Slic3r Sat, 07 Jan 2012 19:12:32 -0500 https://reprap.org/forum/read.php?263,110934,112687#msg-112687 Re: Slic3r 0.5.7 https://reprap.org/forum/read.php?263,110934,112687#msg-112687 >
> Most of people (including me) use Pronterface as a
> good G-code viewer.

Unfortunately, not the same level of detail and readability (you can check gcode lines for the individual moves with Skeinview, color coded, etc.).





>
> Other options include Pleasant3D (for Mac),

very nice for general views, but short on detail.

Threr's also gcode2vtk, allows using paraview and mapping colors to different properties (build time, speed etc.)

> Repetier-Host,

windows only afaik my wrong, he now has linux and mac. Going to try it.

> the Blender G-code plugin (which I
> updated to make it compatible with modern G-code;
> look for it in my Thingiverse page).

Not yet set a serious foot on blender-land. THX for the link!

> I also heard
> of a new G-code previewer that was released
> recently, but I can't remember its name or where I
> read of it.
]]> Lanthan Slic3r Sat, 07 Jan 2012 13:04:15 -0500 https://reprap.org/forum/read.php?263,110934,112674#msg-112674 Re: Slic3r 0.5.7 https://reprap.org/forum/read.php?263,110934,112674#msg-112674 -------------------------------------------------------
> Still, we'd benefit a lot for having a way to
> visually inspect the layers (apart of printing
> 'em) and might help by accelerating the debug
> cycle.

Most of people (including me) use Pronterface as a good G-code viewer.

Other options include Pleasant3D (for Mac), Repetier-Host, the Blender G-code plugin (which I updated to make it compatible with modern G-code; look for it in my Thingiverse page). I also heard of a new G-code previewer that was released recently, but I can't remember its name or where I read of it.]]> Sound Slic3r Sat, 07 Jan 2012 11:09:20 -0500 https://reprap.org/forum/read.php?263,110934,112670#msg-112670 Re: Slic3r 0.5.7 https://reprap.org/forum/read.php?263,110934,112670#msg-112670
I tried running skeinveiw on slicer-generated gcode, it doesn't like it at all and dies. Probably it is because of the additional gcodes. Still, we'd benefit a lot for having a way to visually inspect the layers (apart of printing 'em) and might help by accelerating the debug cycle.]]> Lanthan Slic3r Sat, 07 Jan 2012 10:21:43 -0500 https://reprap.org/forum/read.php?263,110934,112643#msg-112643 Re: Slic3r 0.5.7 https://reprap.org/forum/read.php?263,110934,112643#msg-112643
@Andrew: that issue is probably already entered in this ticket [github.com]

@Lanthan: Slic3r includes an algorithm to detect arcs from subsequent segments at the very last stage. Its purpose is, more or less, to save bytes in the resulting G-code by combining multiple segments into a single G2/G3 arc command where this won't visibly change the shape of the paths. The resulting better quality is a plus benefit, of course.]]> Sound Slic3r Sat, 07 Jan 2012 05:02:40 -0500 https://reprap.org/forum/read.php?263,110934,112593#msg-112593 Re: Slic3r 0.5.7 https://reprap.org/forum/read.php?263,110934,112593#msg-112593 brnrd Slic3r Fri, 06 Jan 2012 16:44:20 -0500 https://reprap.org/forum/read.php?263,110934,112591#msg-112591 Re: Slic3r 0.5.7 https://reprap.org/forum/read.php?263,110934,112591#msg-112591 Lanthan Slic3r Fri, 06 Jan 2012 16:37:02 -0500 https://reprap.org/forum/read.php?263,110934,112565#msg-112565 Re: Slic3r 0.5.7 https://reprap.org/forum/read.php?263,110934,112565#msg-112565
I've found a few situations where infill is outside the object's perimeter]]> Andrew Diehl Slic3r Fri, 06 Jan 2012 14:19:52 -0500 https://reprap.org/forum/read.php?263,110934,112535#msg-112535 Re: Slic3r 0.5.7 https://reprap.org/forum/read.php?263,110934,112535#msg-112535
@brnrd: the Z feed rate should be limited by your firmware, not by your slicer. Check the max_feedrate option of your firmware and configure it so that no G-code could be harmful for your machine. Regarding your second question, when you load the G-code in Pronterface it will show the total length of required plastic as well as a pessimistic time estimate. I am aware of the missing retraction in that situation, and I will work on it soon.

@Andrew: I love that print! and thank you for the input, some of those features will be implemented some day.

@Tarjak: 1) make sure your firmware E steps are good, 2) make sure your filament diameter is exact and measured with a caliper, 3) make sure your Z = 0 (adjust endstop or the z-offset config option), 4) raise the extrusion multiplier.

@Nudel: invoking Slic3r with --gcode-arcs is sufficient to activate arcs. You can check that by searching for G2 and G3 commands in the resulting G-code. Beware that arc support is still experimental as I had no time to bring it from proof-of-concept to a stable state; other priorities kept me busy.]]> Sound Slic3r Fri, 06 Jan 2012 09:41:33 -0500 https://reprap.org/forum/read.php?263,110934,112456#msg-112456 Re: Slic3r 0.5.7 https://reprap.org/forum/read.php?263,110934,112456#msg-112456


[attachment 6239 slic3r_notretracting.jpg]
]]> brnrd Slic3r Thu, 05 Jan 2012 20:18:23 -0500 https://reprap.org/forum/read.php?263,110934,112400#msg-112400 Re: Slic3r 0.5.7 https://reprap.org/forum/read.php?263,110934,112400#msg-112400 -------------------------------------------------------
> Option to prefer starting/ending a perimeter where
> there is not any overhang.
Agreed, perimeters are not treated as a bridge, and can cause some problems.

> I think the outermost perimeter should be printed
> before the inner ones
I disagree. Especially when printing serious overhangs it's best to print the inner perimeter first, as the outer perimeters sticks to the side of the previous loop, it's not much but I've gotten better prints when the order was changed.


I absolutely love slic3r! It's incredibly fast, it sliced this huge 5mb stl i less than 3 minutes! [www.thingiverse.com]

One question though, is it enough to make a shortcut to "slic3r.exe --gcode-arcs" to activate arc support?]]> Nudel Slic3r Thu, 05 Jan 2012 12:29:35 -0500 https://reprap.org/forum/read.php?263,110934,112336#msg-112336 Re: Slic3r 0.5.7 https://reprap.org/forum/read.php?263,110934,112336#msg-112336
I never had much luck either with esunpla filament, the PLA is tricky to use and not very consistent and the ABS was a total disaster for me, I'm sure both the ABS and PLA have 'added' materials that make using it with printing much harder, but I could not get any info out of them about the real mix, maybe their new stuff is better?]]> richrap Slic3r Thu, 05 Jan 2012 03:23:12 -0500 https://reprap.org/forum/read.php?263,110934,112290#msg-112290 Re: Slic3r 0.5.7 https://reprap.org/forum/read.php?263,110934,112290#msg-112290
250C for the PLA. Makes bonding really strong, and at this size of an object part cooling is a non-issue. If you are printing a small part, the corners always seem to curl on me at this thickness.

It is just crappy natural PLA from esunpla. Actually got really lucky the part even finished, there was a big blob on the filament 20mm upstream when the part completed.]]> Andrew Diehl Slic3r Wed, 04 Jan 2012 17:33:23 -0500 https://reprap.org/forum/read.php?263,110934,112260#msg-112260 Re: Slic3r 0.5.7 https://reprap.org/forum/read.php?263,110934,112260#msg-112260
What print speed and temperature did you use?

I have been having some issues printing lower than 0.1mm, I can't work out if it's temperature or speed related.

Is that pearlescent White PLA?]]> richrap Slic3r Wed, 04 Jan 2012 14:47:33 -0500 https://reprap.org/forum/read.php?263,110934,112254#msg-112254 Re: Slic3r 0.5.7 https://reprap.org/forum/read.php?263,110934,112254#msg-112254
Side note, printed Yoda at .1mm layers, 2 perimeters, 10% fill, 1.5x scale:

Sliced in 6min, 32s.


]]> Andrew Diehl Slic3r Wed, 04 Jan 2012 14:14:51 -0500 https://reprap.org/forum/read.php?263,110934,112171#msg-112171 Re: Slic3r 0.5.7 https://reprap.org/forum/read.php?263,110934,112171#msg-112171 I also have a problem with slic3r, the outline perimerter comes out really well, but the infill is never solid. I set the infill to 1, but I get prints like in this picture:


I also tried setting the solid layers to 1000, means that all layers should be printet solid, and infill is ignored, but this also did not work.

Fill pattern and solid infill pattern are set to rectilinear with 45°.

Any idea what I can do? Because the tunig options in slic3r are really limited.
]]> Tarjak Slic3r Wed, 04 Jan 2012 02:47:05 -0500 https://reprap.org/forum/read.php?263,110934,112159#msg-112159 Re: Slic3r 0.5.7 https://reprap.org/forum/read.php?263,110934,112159#msg-112159
That being said, I have a list of suggestions I would love to see implemented :)

Have a "Save as default profile" button in the GUI

Make every 'island' perimeter start from the same place. ie: lower left corner. Parts look better without the tiny layer change blobs arbitrarily scattered about.

Option to prefer starting/ending a perimeter where there is not any overhang.

I think the outermost perimeter should be printed before the inner ones (or at least give the option somewhere)

Cool (already mentioned)

And of course, support generation (also mentioned)

Also, I've found smallish internal circles around 8mm diameter sometimes do not have their perimeters meeting up and are leaving gaps (~.5-1mm)

THANKS for the hard work!]]> Andrew Diehl Slic3r Tue, 03 Jan 2012 21:52:22 -0500 https://reprap.org/forum/read.php?263,110934,112154#msg-112154 Re: Slic3r 0.5.7 https://reprap.org/forum/read.php?263,110934,112154#msg-112154
Can you give me an answer of my question ?

Thanks !



Michael]]> Hardwarekiller Slic3r Tue, 03 Jan 2012 21:22:19 -0500 https://reprap.org/forum/read.php?263,110934,111758#msg-111758 Re: Slic3r 0.5.7 https://reprap.org/forum/read.php?263,110934,111758#msg-111758
1. Is there a feed rate limit for z in slic3r? I noticed that the feed rate for z moves is quite fast in the g-code. The first layer move was done at the travel speed of 130 mm/s which is too fast for a Mendel. I know that the firmware (Marlin, Sprinter, etc) also has a limit, and with acceleration this speed will probably not be reached. But on combined x, y and z moves, could this pose a problem?

2. How can I see statistics on plastic used, printing time etc?]]> brnrd Slic3r Sat, 31 Dec 2011 08:01:48 -0500 https://reprap.org/forum/read.php?263,110934,111587#msg-111587 Re: Slic3r 0.5.7 https://reprap.org/forum/read.php?263,110934,111587#msg-111587 -------------------------------------------------------
> Hardwarekiller Wrote:
> --------------------------------------------------
> -----
> > Than i take the Slic3r 0.5.7 Version, and the
> same
> > Slice the 0.5mm thin wall and the Programm
> give
> > NOT an GCode, it is an Bug !
>
> No, it's not a bug. Support for thin walls is a
> feature that hasn't been implemented yet.

Hi Thanks for the Info !

When make a Version i can Slice one Line Objekts ?


Hire an other Prob !

This ist an Belt Gear Pully, from
[www.thingiverse.com]
and i sliced whis sfact and print it
The Print iss ok

I can the Belt over the Pulley, ist all OK !

This the same Gear, i sliced whis all versions old and the last slic3r 0.5.7 and print it
The Print is NOT OK !


The Problem is hire !

1 all T5 bridge round
2 all T5 bridge iss not deep enough


I Belt can NOT over the Gear

Who iss the Problem ??

And a another question
At the moment i take as Firmware Sprinter
I wont change to Marlin
In the Marlin Firmware ask the Author the Diamander for the Firlament, is that an problem for the Slic3r ??
Why make that Marlin in the Firmware ?


Michael
]]> Hardwarekiller Slic3r Thu, 29 Dec 2011 23:06:09 -0500 https://reprap.org/forum/read.php?263,110934,111441#msg-111441 Re: Slic3r 0.5.7 https://reprap.org/forum/read.php?263,110934,111441#msg-111441
It was that video and this blog post that prompted me to finally play with lower layers, it really is very easy with Slic3r, I'll let you know how they turn out, it's going to be a long print....

Cheers,

Rich.]]> richrap Slic3r Wed, 28 Dec 2011 14:34:21 -0500 https://reprap.org/forum/read.php?263,110934,111440#msg-111440 Re: Slic3r 0.5.7 https://reprap.org/forum/read.php?263,110934,111440#msg-111440
Quote

most people set it to 0.95 or so to compensate for die swell.
Die swell does not alter the volume of plastic extruded, it just makes it come out fatter and slower when extruded into mid air. It doesn't affect the maths but it allows you to extrude bigger filament or if you keep it the same size it gets stretched more, leading to more hole shrinkage.]]> nophead Slic3r Wed, 28 Dec 2011 14:28:18 -0500 https://reprap.org/forum/read.php?263,110934,111431#msg-111431 Re: Slic3r 0.5.7 https://reprap.org/forum/read.php?263,110934,111431#msg-111431 > I have not printed it yet, just wondering about
> the way the total length is calculated in
> Slic3r,and if it's correct.

That's a challenging question :-)
The filament length is calculated by just summing all the E values from the G-code file before each reset of the E axis. This is what other software, like Pronterface, do and it gives exact values. Why this happens is a good question, but it doesn't concern me at all, since a lot of things can change as a consequence of changing layer height including toolpaths and extrusion math. Not a problem at all.

See this video from Spacexula: [www.youtube.com] printing at an unbelievable layer height. :-)]]> Sound Slic3r Wed, 28 Dec 2011 14:01:29 -0500 https://reprap.org/forum/read.php?263,110934,111421#msg-111421 Re: Slic3r 0.5.7 https://reprap.org/forum/read.php?263,110934,111421#msg-111421 -------------------------------------------------------
> richrap Wrote:
> --------------------------------------------------
> Hey Rich, the funny (or not so funny) thing is
> that for each version there's some people
> reporting too much extrusion, and other too few.
> For 0.5.7 I got almost all good reports,

I did have a play with the Advanced tab and also the extrusion multiplier, and with a tiny fudge I have perfect filling, I think this nozzle maybe slightly out of 0.5mm.

It seems perfect with solid, loose and hollow printing so I'm very happy and it's now identical to my Skeinforge prints.

I'm messing with tiny layers now and have one more question -

below all being Sliced using 3 solid layers and 25% infill.

If I slice an object (simple hollow triangular tube with a 0.9mm solid bottom) at 0.3mm layers I get a filament used of - ; filament used = 1555.2mm (9.5cm3)
If I slice the same object again at 0.1mm layers I get more filament used - ; filament used = 1593.0mm (9.7cm3)

I expecting the exact opposite, I would have thought that the3 x solid layers (0.9mm) using 0.3mm layers would use up more filament than the 3x 0.1mm solid layers (0.3mm solid, +25% infill for 0.3, +0.3 solid).

If I then slice the same object at 0.01 (Ten microns) it uses even more plastic - ; filament used = 1615.7mm (9.9cm3) I would have thought this would use slightly less than the 0.1?

Am I just being dim and missing something or is this wrong? The walls of the object are identical all the way up so it makes identical Gcode for every layer other than the base (being 0.9mm solid)

I have not printed it yet, just wondering about the way the total length is calculated in Slic3r,and if it's correct.

Cheers,

Rich.]]> richrap Slic3r Wed, 28 Dec 2011 12:51:29 -0500 https://reprap.org/forum/read.php?263,110934,111380#msg-111380 Re: Slic3r 0.5.7 https://reprap.org/forum/read.php?263,110934,111380#msg-111380 -------------------------------------------------------
> Than i take the Slic3r 0.5.7 Version, and the same
> Slice the 0.5mm thin wall and the Programm give
> NOT an GCode, it is an Bug !

No, it's not a bug. Support for thin walls is a feature that hasn't been implemented yet.]]> Sound Slic3r Wed, 28 Dec 2011 05:01:17 -0500