CURA-4451
- Add upgrade script for 3.0. to 3.1
- Upgrade old stack files so they will use "empty_quality" as the
"Not Supported" quality profile.
- Increase SettingVersion to 4
The UM3 definition sets the setting to 3mm. Nothing else sets it to another value except FDM Printer. I left the UM3 setting in and removed all travel_avoid_distance settings in the UM3 profiles.
This was found by the materials team to be a better value. All UM3 profiles have 20 now. I've left the third-party machines intact which override the prime tower size but those that didn't override the prime tower size have their prime tower size altered as well.
These optimisations should only remove settings that are exactly equal to the parent profile. Support interface settings are an exception, since they were defining non-existing settings in the original profiles. The stand-by temperature is also an exception, since the stand-by temperature of the material profile is set in stone because of firmware.
Contributes to issue CURA-3650.
There have been some problems in the optimization of these profiles, so we undo this for now, preventing people from editing these materials and risking some warnings in Cura's interface, but providing the correct experience for people trying the new materials.
These are now upgraded to version 3, meaning that they will have to increase their version numbers and remove any start_layers_at_same_position settings they define. None of these profiles define any start_layers_at_same_position so it's just the version number then.
Contributes to issue CURA-3479.
All print temperatures go down 5 degrees and then in the material profile the temperature is increased by 5. This gives the normal profile a +0 instead of +5.
Contributes to issue CURA-3433.
The optimisation script didn't know that the temperature settings in material profiles now refers to default_material_print_temperature rather than material_print_temperature. This caused a few things to go wrong here.
Contributes to issue CURA-3433.
These materials are hard-coded in the optimisation script, so the optimisation script didn't know that those materials were materials and this caused a chain reaction where in the end the profile could only override XML-settings.
