PrusaSlicer 2.2 released

zapta

@Phaedrux, not commenting on any specific slicer or controller but I think that in general having that many manual controls is an indication of the immature stage of this technology.

All we need is a single control, to select the color of the printed object.

Phaedrux

@zapta said in PrusaSlicer 2.2 released:

@Phaedrux, not commenting on any specific slicer or controller but I think that in general having that many manual controls is an indication of the immature stage of this technology.

All we need is a single control, to select the color of the printed object.

I don't think it will ever be as simple as a 2d paper printer. Just look at CNC machining. It's been around for ages and it takes a skilles operator with a specific intention and advanced tools to get good results. And honestly where's the fun in that if it were that easy?

deckingman

Does anyone know of a slicer which has the concept of tools which aren't necessarily extruders? What I mean by that is the slicer needs only to put a Tn command in the gcode file and can otherwise be completely dumb of what that Tn consists of. I still use a very early version is SliC3r which does that. Slic3R PE assumes that all tools must have a single extruder so before I can use say tool 9 which might be orange (a mix of red and yellow) I have to set up 9 extruders in the slicer, even though only 6 physically exist.
Come to that, does anyone know of a slicer which has no limit (or a very high one) on the number of tools? I need at least 9.

PaulHew

@Danal said in PrusaSlicer 2.2 released:

I've slowly switched from Cura to Slic3rPE.

I am sometimes forced to use Simplify3D (long story) and have really come to despise it.

Have to agree, I am now trying to use PrusaSlicer primarily. Works really well on the Railcore and the config bundle JohnOFCII produced is superb.
Getting to grips with it for the Ender3 but at least Prusa have included support for it.
S3D, could not justify the cost. £130 per year.
My twopence worth!

P.

matt3o

@Phaedrux said in PrusaSlicer 2.2 released:

I don't think it will ever be as simple as a 2d paper printer

my 2D printer still jams paper...

I've read on e3d forums that Prusa is the only slicer able to handle very high flow extrusions (fast movements and/or big nozzles). Can you guys confirm that?

dc42

I first tried PrusaSlicer two days ago, because I needed to test the new object cancellation facility in RRF, which relies on object labelling. I am impressed by it, and planning to switch over to it from S3D. It has other benefits too, such as the built-in file upload to Duets and support for firmware retraction.

droftarts

@dc42 said in PrusaSlicer 2.2 released:

because I needed to test the new object cancellation facility in RRF, which relies on object labelling.

I was about to ask which slicers support that! Any others?

There was a couple of things in the video I liked the look of. The main thing missing, for me, seems to be tree support, but I don’t use it that frequently in Cura.

Ian

whosrdaddy

Been using prusaslicer/Slic3r PE for years now and has never let me down...
Now that we finally have layer pause option with v2.2 it's sad that it only emits M601 but RRF only support M226 for pausing the print.
@dc42 can you implement M601 as an alias for M226 in the firmware?

droftarts

@whosrdaddy I don’t think M601 is defined, so you can make a macro in the sys folder called M601.g which will be called when RRF encounters it in Gcode. Then put M226 in that macro. At least, in theory...

Ian

whosrdaddy

@droftarts didn't know about that one.
Printer is busy printing atm but will test this asap, that would be awesome!

mrehorstdmd

I sliced a 42 MB STL file to a 280 MB gcode file a couple days ago and it ran fine on the printer. I've had trouble in the past with slicing very large STL/gcode files, so they must have fixed something.

droftarts

@whosrdaddy from the video, I thought you could put any Gcode in at a particular layer? Haven’t watched it again, though.

Ian

zapta

@matt3o said in PrusaSlicer 2.2 released:

my 2D printer still jams paper...

Please post your config.h file.

zapta

@whosrdaddy said in PrusaSlicer 2.2 released:

Now that we finally have layer pause option with v2.2

I saw the announcement about this feature. Previous version had an easy to use pause at layer option that worked very well for me.

I just move the vertical layer slider to the layer I want and click on the [+] icon next to the slider. The printer then pauses at that layer, and you can change filament or just resume with same filament.

whosrdaddy

@droftarts Lol now that you say it, indeed you can. I was too focused on the "pause" thing

oliof

@mrehorstdmd they did significant changes to their movement planner. Maybe that helped.

zapta

@PaulHew said in PrusaSlicer 2.2 released:

S3D, could not justify the cost. £130 per year.

S3D is in decline, both the company and the product. I have a paid license but I now prefer the free slicers.

You can get some insight on how the company operates here: https://www.glassdoor.com/Reviews/Simplify3D-Reviews-E1187369.htm

(They could learn a thing or two from Duet3d which is smaller but is more productive and provides much better customer support.)

mrehorstdmd

@oliof so it seems!

Turbo

It's now my go to slicer instead of Cura, but there's one major issue for me and thats how it handles dual extrusion. Ill set it to extruder 2 and it'll heat up extruder 1, and when 1 heats up, it tries to extrude out of heater 2. I have to manually heat up extruder 2 before sending it gcode, otherwise things aren't pretty

Danal

@Turbo said in PrusaSlicer 2.2 released:

It's now my go to slicer instead of Cura, but there's one major issue for me and thats how it handles dual extrusion. Ill set it to extruder 2 and it'll heat up extruder 1, and when 1 heats up, it tries to extrude out of heater 2. I have to manually heat up extruder 2 before sending it gcode, otherwise things aren't pretty

Hmmm... I'm running SlicerPE output into a toolchanging printer with no editing of the G-Code. Everything heats just fine. Hmmm...

Do you have "wait for temp" g-code in your TPOST macros?