ultimaker.def.json is also cleaned and put in alphabetic order.
Ultimaker 2 and original are kept mostly as they were, since they are not tested. PP-42
We've removed a bunch of settings and transformed others. To allow profiles to be checked for these and edited if necessary, we now need to increment this version number.
Contributes to issue CURA-8466.
Since the setting version 18 is used in the arachne beta build, we decided to make the the setting version to 19 in the normal releases, so that we make sure that projects made in arachne beta won't use any version upgrade scripts if a user attempts to open them in 4.12.
CURA-8510
We now have version 18, where Flsun Super Racer has customised profiles.
Nothing changes in the built-in profiles. It only needs a change in the machine instances.
Contributes to issue CURA-8510.
We have a change now that requires a version upgrade. This triggers all profiles to update for the user, and we must update accordingly in the built-in profiles.
Contributes to issue CURA-7118.
Conflicts:
resources/quality/ultimaker2_plus/um2p_pp_0.8_draft.inst.cfg -> Weights being changed while a whole slew of fixes were being done on 4.0
resources/quality/ultimaker2_plus/um2p_pp_0.8_verydraft.inst.cfg -> Ditto
This reverts commit 9432252de4. It was assuming the wrong default speed_print value of 60. It's not always 60. We need to find a different solution or modify the script.
Reverts the fix for issue CURA-5342.
- Add a new field "variant" in "metadata" section for quality profiles.
"material" will only contain values such as "generic_abs", and
"variant" will contain values such as "0.25 mm", "AA 0.4", etc.
- Reformat "metadata" section to have the following order:
- setting_version
- type
- quality_type
- weight
- global_quality
- material
- variant
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
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.
Otherwise you get cryptic error messages about settings that may be hidden having invalid values, since minimum fan speed may not be higher than maximum fan speed. The value of the setting with the default settings should be the same.
Contributes to Github issue #1268.
