The draft and ooze shield use the skirt/brim settings to print. So these settings should be adjustable if the draft or ooze shield is enabled. It's a bit weird UX-wise, but it's correct. The UX problem will be tackled later.
Apparently this was already done for the speed/acceleration/jerk settings so no change necessary there.
Contributes to issue #8808.
Two problems with this description:
- It claims that meshes with lower rank override meshes with higher rank. It's the other way around.
- It mentions 'rank' in one sentence and then 'order' in the next. I've corrected this to use the term 'rank' in both sentences for clarity. This is also the term used for the setting label, to be consistent.
Found in issue #8821.
The ProBundle rejects materials which have these values a positive number.
Users should not be allowed to set it to a positive number.
Fixes CURA-7856.
This platform mesh is 3MF (whose texture coordinates we cannot read) and doesn't contain actual texture coordinates either.
Contributes to issue CURA-7852.
* Add files via upload
* Add files via upload
* Add files via upload
* Update fusedform_300_draft_abs.inst.cfg
* Add files via upload
* Delete fusedform_300_draft_abs.inst.cfg
* Delete fusedform_300_draft_pla.inst.cfg
* Deletion of old files
* changes in STD quality profiles
* Changes in mini quality files
* Changes in FF600 quality files
* changes in machine definition name
* Changes in definition files
* extruder and definition linking
* ff300 inherits and extruder def
* Update fusedform_300.def.json
* category deprecation in definitions
* inherits
* ff300 extruder definition machine
* extruder machine definitions
* Fused form FF600plus machine profiles
* PETG profiles
* Update fusedform_300.def.json
* changes in start gcode
* machine configuration dynamics on definitions
* speed adjustments
* dynamics modification in petg and flex quality
* Further adjustments on dynamics definitiosn
* Modification of all files under inherits data structure.
* Quality setting version 15 to 16
* These changes are for limiting quality types in the materials defined
* Quality Modification under Global and Material specific structure
Global quality structures and material specific definitions under the global structures
* Addition of double extruder machine definitions
* Machine definitions update according to structure
* Doppia Base definitions erased, Doppia definitions updated to use a single base definition.
* extruder 1 base definition fix
* extruder train overrides
* extruder modifications
* Update fusedform_300_doppia.def.json
* Base settings and extruder definitions
* retraction modification to avoid filament damage
* REdefinition test of second extruder train in doppia
* Update fusedform_300_doppia.def.json
* Update fusedform_base_extruder_1.def.json
* Update fusedform_300_doppia.def.json
* Update fusedform_300_doppia.def.json
* Update fusedform_300_doppia.def.json
* Update fusedform_base_extruder_1.def.json
* Update fusedform_300_doppia.def.json
* Update fusedform_600_doppia.def.json
* Update fusedform_600_doppia.def.json
* Additional updates in Doppia definitions
* Creation of Doppia base definition, doppia extruders. Update in doppia machine definitions
* correction in quality definitions to pull base definitions from a single base
* more corrections
* add Syndaver AXI machine
Added Syndaver AXI Machine and Extruder Profile
* Correct text in json file
removed the spaces in the json file names
* remove unused text
remove the unused name assigning code in the json machine file
* corrected start/end gcode
specified values that could not be replaced
* Update syndaveraxi.def.json
corrected the machine dimesions
Also convert it to 3MF, to save some file size.
According to reports in #8663 this is the true orientation of the printer w.r.t. the coordinate system in its firmware.
Fixes#8663.
This was found to be better in https://github.com/Ultimaker/Cura/issues/8321 due to changes to the simplification function.
Other printers are assumed to have a similar effect, or have their original value copied from Creality printers.
There were a number of problems with it:
* There were duplicate JSON keys. One of the duplicates gets ignored then according to the JSON implementation in Python.
* There were some 'value' properties that contained undefined variables since the setting type was a string and the value is a string containing a Python expression that should result in a string, not a plain string.
* There was one instance in which a 'default_value' property contained a formula.
Contributes to issue CURA-7752.
