For polypropylene a wipe distance of twice the nozzle size is fine. Even required, since the material warps so much that it breaks open automatically if a breach starts to appear at the seam. For other warping materials this could also be a problem, so let's just increase the warning value.
Contributes to issue CURA-3960.
The stand-by temperature should be 175 for these profiles because the UM3 firmware levels the bed with that temperature. It should be 100 in the quality profiles because that's what the stand-by temperature should be when standing by while the other nozzle is printing.
Contributes to issue CURA-3960.
The stand-by temperature in the material profiles is the temperature at which the build plate levelling should be done. The actual stand-by temperature in Cura should be 100, so these profiles have to overwrite the material profile then.
Contributes to issue CURA-3960.
It looks very wierd to have the Material category label translated but not the rest of the categories. I don't know the proper translations for the rest, so I must remove this one. The label is left intact though.
Contributes to issue CURA-3950.
These profiles have been tested and they are in the process of optimising them, but there is still some room for improvement there so this is supposed to lower the expectations of our users.
Contributes to issue CURA-3960.
Note that Git says that Fast was renamed to Verydraft, but in reality Fast was renamed to Draft and Draft was renamed to Verydraft.
Contributes to issue CURA-3960.
These are optimised to the level of the materials: Anything that is common between quality profiles with the same material and nozzle gets bubbled to the profile for that material (per nozzle). It doesn't bubble any further (to the variant) because that could have an impact on the other profiles.
This basically only removes settings because where these settings then bubble to is the material profile in the fdm_materials repository. And a lot of settings are just removed because they are equal to the default.
Contributes to issue CURA-3960.
They are now supported. This breaks the stacks of people who had these profiles active when they upgraded from 2.6.0 to 2.6.1, which causes them to get a screen of which printer they want to add, and they lose their current settings. But we decided that this use case is too slim to make an entire version upgrade for this patch-version release.
Contributes to issue CURA-3960.
This removes all settings that are equal to the defaults. Some settings are 'common' between all profiles of the same material. I've let those settings bubble up to the material profiles but that change is then obviously only apparent in the fdm_materials repository.
Contributes to issue CURA-3960.
These profiles are improved by the materials team. This is directly copied from them and should now be optimised for our use.
Contributes to issue CURA-3960.
When there is 1 extruder, the frontend stores all settings in the global stack. Sending an extruder stack confuses CuraEngine into using the values of the extruder stack, which results in defaults being used.
This translation is only translating the setting descriptions. However it is also missing one translation: smooth spiralized contours. We decided not to block these translations just for that one. It was also missing another translation: Support bottom pattern. I inferred that from the description of Support Roof Pattern, basically doing the translation myself.
Contributes to issue CURA-3950.
Because of this wrong MIME type, the material profile would get saved using the preferred extension of the instance container, .inst.cfg. This would then get interpreted as having the MIME type of instance containers, and then it would fail to load because it is not an INI file.
Now it stores it as .xml.fdm_material and so the MIME type database interprets it as an XML file.
Contributes to issue CURA-3937.
There's one copy for every stack. It doesn't matter which one we take as long as they have the same name. Global is always present, even in single extrusion. Seems the most logical one to display.
Contributes to issue CURA-3935.
NB: previously the "approximate_diameter" metadata was stored as a number. This caused some issues passing arguments from QML to Python. Now "approximate_diameter" is stored as a string.
