Prusaslicer 2.7.0.... bad idea  

RE:

No one forced you to update.
Yes, I bet you really did not like that response.

You should be able to install older version and be back in the business an read about changes.
If not, recover from backup.

No backup? Well now you know why you want one 😀

2.7.0 means new features vs previous version (unfortunately profile changes forcing to be binary gcode should be marked as 3.0.0 but well....)

RE:

Posted by: @_kaszpir_

No one forced you to update.
Yes, I bet you really did not like that response.

Nice one. But it has to be said. 

Naah, I'm half of the moron here. No Biggy. 

MY INTENTION was a reminder as a responding Prusa-Customer: Pleeeease, Developers - check your final Deployment before you give it free. It's just bad for the company's reputation. 

Thanks by the way. 

PS. I stick to Prusa,, my 3MKS is trusty 

RE: Prusaslicer 2.7.0.... bad idea

why do developers agree on handing out faulty software updates to customers

There hundreds of millions of PCs out there, apart from those in locked down corporate environments they will all pretty much be different in some way. You will have different hardware, different software, different peripherals, different drivers for the hardware, different patch levels etc. Then you've got the different ways people use the software, do people click on a file to launch the app, stl or 3mf, open slicer then select a file, single file or multiple, select using menus or drag and drop, open menus by mouse, alt key or shortcuts, same variables in usage for slice settings. So if you can come up with a 100% way of testing everyone one of those configurations and ways of using then I suggest you go into business to sell your solution as you will make a fortune. The majority of people have found 2.7 to work fine.

Rather than just slagging off the devs on here, why don't you file a detailed bug report, then you might have a chance of getting a fix for your particular situation.

You can bet your house, that the software was extensively tested and not released with any significant problems, you apparently have found an issue that was not known. You have three choices on what to do about it:

1. Whinge to the world at large about how rubbish the software and its developers are, which achieves nothing.
2. Live with it or an alternative app, until the software gets a fix for your particular problem
3. Or be constructive and try to help the devs to trace and fix the software.

And before you ask, I am a retired developer, and spent my working life dealing with whingers

RE: Prusaslicer 2.7.0.... bad idea

I think the major issue was the fact that new PrusaSlicer was developed along with new firmwares for the printers - there is quite a lot of threads on the forums people ranting about  both.

If you have a working system and deadlines then you really better not change the system. You need to plan and test an upgrade on one printer from the farm and computer used for managing it.

Some people are lucky to have a more than one printer and more than one computer so it is doable.

But most people probably not, and that require even more attention and time to look around about forums what people are experiencing during upgrade. I know I have some integrations with my current printer and updating firmware will require altering other 4 software apps that use that printer. It will take some time to adjust it so I am for now postponing firmware and software upgrade.

I don' need to have those new firmware/software features yet, so I am waiting for a better moment, probably after Xmas.

RE: Prusaslicer 2.7.0.... bad idea

Simple rule: don't perform updates when on a deadline. Plan your updates around your production schedule.