I can't trust Prusa Slicer 2.6.1
Hello to all,
I've been working on the mainframe with Prusaslicer 2.6..1 for a while now and I'm loving the new options for Connection Pins and Cutting.
The problem is the following:- There are models that do not load in this 2.6.1 version (I have to go back to 2.3.3 to be able to laminate and launch the print.- Some parts get burrs in the retractions (I have to go back to version 2.3.3 so that they don't appear).- I have noticed an improvement in the 30'-60' print times which I appreciate but it is not vital for my 3D printing service.
Conclusion: I'm using version 2.6.1, but I can't leave 2.3.3 for certain STLs.
I offer 3D printing service, and it's an issue that concerns me because I make my living from it.
I'm sorry I can't post comparative images right now, but I wanted to put it on record in case someone is in my situation.
Best regards and happy printing to all of you.
PS: The printers I work with are Prusas MKS3+, always PLA, always the same colour, always the same manufacturer.
RE: I can't trust Prusa Slicer 2.6.1
Have you tried the 2.7 Alpha 1 from here: https://github.com/prusa3d/PrusaSlicer/releases to see if there's any improvement?
If you think you have found bugs/issues then please report them on the GitHub site: https://github.com/prusa3d/PrusaSlicer/issues
RE: I can't trust Prusa Slicer 2.6.1
Thank you for your response.I will try 2.7 when I have time. By the way I take this opportunity to say that when I cut a model with connection pins and save it as STL it gives an error and then the pins appear, but the holes don't. I have to save it as a project to avoid losing my work. I have to save it as a project to avoid losing my work.At the moment I'm surviving with both versions. I appreciate very much the organic supports, but when I go back to 2.3.3 I don't have them :(The computer with 2.3.3 is 10 years old and I have 2.6.1 on a one year old computer with maximum performance.
RE: I can't trust Prusa Slicer 2.6.1
You can run multiple versions of Prusa slicer on the same computer if you run from customised start up batch files. Basically force them to use different folders for the configuration data. All the previous versions are available on the Prusa slicer GitHub repository.