PrusaSlicer 2.2.0 on the horizon  

RE: PrusaSlicer 2.2.0 on the horizon

I assume adding the Mini is worth a minor bump (X.+1.X).

RE: PrusaSlicer 2.2.0 on the horizon

I'm slightly surprised a Mini compliant version isn't already out bearing in mind it was originally due to start shipping 'by the end of November'...

Texy

RE: PrusaSlicer 2.2.0 on the horizon

Posted by: @texy

I'm slightly surprised a Mini compliant version isn't already out bearing in mind it was originally due to start shipping 'by the end of November'...

Texy

It's probably much like the SL1 where they kept that functionality buried until release... But since it's another FDM it could probably even be done with just a profile update, no major rework required.

RE: PrusaSlicer 2.2.0 on the horizon

I agree with @vintagepc that the Mini should mostly just need profile updates. Though, it might be for the Mini they need to add it to the configuration wizard... Also, (as of right now) there have been 721 commits to the repository since 2.1.0 came out, so hopefully that points to some bug-fixes/enhancements coming to all of us.

Thinking of it though... If the commits are all just bug fixes then the version number format would only need an x.x.x+n version number change. @lichtjaeger might be right that the mini is forcing the x.x+1.x version number change.

RE: PrusaSlicer 2.2.0 on the horizon

looking at most of the changes i don't see any mini specific changes - but I do see adding creality printers to the predefined list

RE: PrusaSlicer 2.2.0 on the horizon

Found something:

min_slic3r_version = 2.2.0-alpha0

1.1.0 Filament aliases, Creality profiles and other goodies for PrusaSlicer 2.2.0 - alpha0

min_slic3r_version = 2.1.1-beta0

1.0.6 Added Prusa MINI profiles

min_slic3r_version = 2.1.0-alpha0

1.0.5 Added SLA materials

RE: PrusaSlicer 2.2.0 on the horizon

Hey, I just noticed that Plicer 2.1.1 is available on the github releases page: 

https://github.com/prusa3d/PrusaSlicer/releases

Get it now before they are all gone. 😉

RE: PrusaSlicer 2.2.0 on the horizon

Hmm... No windows installer, just a zipped program archive for the windows version.

RE: PrusaSlicer 2.2.0 on the horizon

I installed prusa3D_win_2_2_9.exe, Slicer 2.1.1 is included.

RE: PrusaSlicer 2.2.0 on the horizon

Supermerill just released an Alpha of his fork that is merged with 2.2.  Its an alpha so be cautious, but I'm going to download it today for a looksee.

RE: PrusaSlicer 2.2.0 on the horizon

Posted by: @towlerg

I installed prusa3D_win_2_2_9.exe, Slicer 2.1.1 is included.

Duh... I should have known better... (FreeCAD has the installers on the github releases page, not Prusa...)

RE: PrusaSlicer 2.2.0 on the horizon

I'm not sure if this is the place to ask/discuss this, but in the Release announcement on Github one of my most wanted features is listed:

- Insert pause or custom G-code at a certain layer

I'd like to know a detail about this feature implementation along with firmware response.  Specifically, when I use M600 (change filament) today to do this same feature, the printer pushes the bed to Y=0, and then the X to max.  This allows for very easy filament change, but not so easy insertion of parts into the print (and the little annoyance of pulling and putting back in the filament).

Does the M601 implementation put the bed to Y=max and X=max, or does it allow you to choose a corner to temporarily "park" the extruder during the operation?  I'd love the BED to be out front, so that I don't have to reach over/around the printer to do the insertion maneuver, and then, when I click the front button, to push the bed back, and bring the extruder to an easy spot to purge/remove ooze from the nozzle.

Thanks in advance for your response.

--

Phil K.

RE: PrusaSlicer 2.2.0 on the horizon

I'm not sure how they are doing it, I haven't gotten around to installing the new alpha in parallel to my current install.

You can do this yourself as the alphas (and betas) typically don't need an install, just unzip into a convenient folder and run from there. They should (they have in the past) created their own settings in parallel to the stable releases. To get your profiles from the stable that you use into the alpha, open the stable and export config bundle to a file. Then in the alpha (or beta when they arrive) import that config bundle file.

And, if/when you find a bug be sure to report it over on github so they have a chance to fix the bug before the eventual stable release.

Disclaimer: This has been my experience on the Windows platform. YMMV on other platforms.