Prusa slicer 2.30  

RE: Prusa slicer 2.30

2.3.0 of apps and drivers contains PrusaSlicer 2.2.0. PrusaSlicer 2.2.0 is the latest stable release. 2.3.0 is on the PrusaSlicer Github currently in alpha0 phase.

RE: Prusa slicer 2.30

@halcon-designs

I'm sorry I was really referring to the drivers I guess. With the hollowing of prints and stuff. I have downloaded the latest drivers but the features don't appear to be there.

RE: Prusa slicer 2.30

At the moment its very confusing due to the similar version numbers.  When developing software ALL parts of the process usually get their own individual version number.  So Prusa Slicer is currently at version 2.2.0.  The other drivers inside the package will also have their own individual version number(s).  All  those bits and pieces are then put together into a package file.  That package file ALSO has its own version number, so that it can be tracked too.  Due to circumstances the package version is now 2.3.0. 

This similar version number is confusing a lot of people. Especially as the pre-alpha, not yet available unless you build it your self Prusa Slicer is ALSO at version 2.3.0 now.

If you are running released versions of the software then you will NOT be able to get Prusa Slicer 2.3.0 as it has not been released as yet.

RE: Prusa slicer 2.30

@neophyl

Thank you so much! I watched the video and thought it was available. I thought I was doing something wrong.

RE: Prusa slicer 2.30

Keep the firmware and prusaslicer version together, update both at the same time, and do not update the software only.

RE: Prusa slicer 2.30

Posted by: @peter-m26

Keep the firmware and prusaslicer version together, update both at the same time, and do not update the software only.

There are several programs and data files in the bundle. Not all will be updated at the same time. 

RE: Prusa slicer 2.30

Maybe they should take the slicer out of the drivers bundle, it's confusing and it not as if the slicer is in some "lock step" with the drivers.

RE: Prusa slicer 2.30

I can see why they don't want to align the version numbers -- changing PrusaSlicer version numbers when nothing's changed would lead to chaos -- but perhaps including some differentiator in the version number itself might work. A numeric code (e.g. all PrusaSlicer versions start with 1000) or simply an alpha designator (e.g. PS2.30) might help. It's interesting that this hasn't been an issue until now with the announcement of the PrusaSlicer 2.3 Alpha that everyone is after and coincidental numbering of the "driver" package to 2.3.