PrusaSlicer 2.2 released

[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?

[Turbo]

@Danal Is that within prusaslicer or the firmware? never used dual extrusion before and i half expected it to just insert t0/t1/etc into the gcode. i open up a thread about it:
My Post

[insertnamehere]

Another slicer to try is Slic3r++

It's a fork of PrusaSlicer, and is currently at 2.2, but also include a lot of extra functionality, like top layer ironing, (see image). Gives great results.

[droftarts]

@insertnamehere said in PrusaSlicer 2.2 released:

Another slicer to try is Slic3r++

This one? https://github.com/supermerill/Slic3r

Ian

[insertnamehere]

@droftarts said in PrusaSlicer 2.2 released:

This one? https://github.com/supermerill/Slic3r
Ian

Yes, that's it.

[zapta]

Apparently PrusaSlicer disables the Filaments management tab in Configuration Assistance for duet printers. That tab is enabled only for prusa and third part printers but not for custom printers. To reproduce install PrusaSlicer with only a duet printer and see if you can see that tab.

Developers say it's by design bu I don't understand the logic behind it.

[PaulHew]

@zapta Is this the tab you are referring to?

[arhi]

I'm slowly migrating from s3d to ideamaker but am constantly checking out slic3r and ps too and they are producing very good results. PS2.2 fixed the major issue I had with slic3r/PS and that's "lot more movement than s3d/ideamaker for same object", looks like they figured out how to optimize moves.

[matt3o]

@zapta I believe the only option that is hidden is the "machine limits" one that is limited to marlin for some reason. As far as I understand it only helps with print-time-prediction though