These settings have been removed and should no longer be in the profiles.
They were added during a merge, since they were updated recently for Cura 4.13. The merge 'resolved' the conflict automatically without informing me. And resolved it wrongly.
Conflicts:
plugins/SimulationView/SimulationPass.py -> Reverted layer view optimisation in Master while some whitespace changed in Arachne.
resources/definitions -> Bunch of conflicts with profile updates.
resources/quality -> Bunch of conflicts with profile updates.
resources/texts/change_log.txt -> Removed the Arachne change log (as they are internal versions). It'll have to be re-added when we release this version as stable.
It is a global setting, so it can't currently be changed with an intent profile.
A resolve function would resolve this. But which function that should be is to be decided.
Contributes to issue CURA-8746.
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.
Should've done this in the merge, but I just increased the setting_version for these.
I also removed a deleted setting from the advanced visibility. We don't have tests that ensure that these visibility presets are good. Lucky I found it then, with a Ctrl+Shift+F search.
Conflicts:
cura/CuraApplication.py: Setting version
fdmprinter and fdmextruder: Setting version
intents, qualities and variants: Setting version
Changelog: 4.9.1 was added, should be below Arachne changes
- Travel avoid supports
- Dual Extrusion : switch_extruder_retraction_amount = 10
- PETg updates
- Reduced infill jerk in "quick" intent and removed useless first layer jerk
- Removed no more used 1.2x material_flow_layer_0 in order to compensate a bad bed leveling
- Rewiewed forced PLA and PETg temperatures
Context: Print Thin Walls and Fill Perimeter Gaps are old settings that aren't needed any more since we switched to libArachne (Varianble Line Widths).
CURA-7148
Although it is not entirely sure yet, we are fairly certain that libArachne release will have
a setting version of 18, so it is changed by this commit. With this change, the VersionUpgrader
will be properly triggered.
Contributes to CURA-7683 and CURA-7656
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.
We wanted it to end up on 0.2mm by default but still scale with any customised horizontal expansion. To do that we need to add the default horizontal expansion here, rather than subtract it, since the horizontal expansion is negative.
Contributes to issue CURA-7537.
To compensate elephant foot -> initial layer horizontal expansion setting is modeified for engineering and AA0.25 core profile for UMS5 and for UM3 for AA0.4 and AA0.25 cores.
Conflicts:
plugins/VersionUpgrade/VersionUpgrade460to462/VersionUpgrade460to462.py -> On master we removed the getCfgVersion function, while we moved the entire plug-in to a different folder in 4.6.
resources/definitions/skriware_2.def.json -> On master we merged a PR that changes more or less all settings, while on 4.6 we doubled the maximum deviation.
