Previously it was using this 'peak_height' which is the total height of the model in scale_vector.y. However it was then multiplying the height map with that scale vector and adding the base height again a second time. So the scaling part was too thick and included the base height, and the total height of the mesh was also too big.
I also reduced an unnecessary re-calculation of the height_from_base parameter. And as a result we don't need the peak_height variable at all any more.
Fixes#8902.
These formulas were using a setting that didn't exist any more.
Not sure how this got through QA. Oh well, this is what they are intending.
This formula is a little bit weird in how it works with support meshes if support is disabled, but it's more or less as good as it gets. The formula is mirrored from how other Ultimaker printers write it down, but slightly simplified with the same outcome.
After https://github.com/Ultimaker/Cura/pull/8684 raft_airgap and speed_layer_0 existed twice in some of the quality profiles.
This commit fixes that by removing the old (calculated) values.
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
If for some reason the print sequence is set to one-at-a-time be default in the printer definition
and the number of extruders of the printer is set to >=2, then the print_sequence won't show up in
neither the quality changes nor the user changes, yet it will still have "one-at-a-time" as a
value. In a such case, it will still need to be set to "all-at-once" in the user changes.
This is a theoretical case, as it is very unlikely for a printer to have "one-at-a-time" set by
default in its definition (.def.json) file and still be able to support more than one extruders.
But it is a world full of possibilities out there, so you never know...
CURA-7827
Previously, the print sequence would be always set to all-at-once in the user container whenever
the second extruder would be enabled. This was causing an interface issue, where the circular
reset-setting arrow would appear next to the setting, even if the quality changes already had the
correct value ("all-at-once").
This is now fixed by checking the following:
- If print_sequence == "one_at_a_time" in the quality (so it is already saved in a quality profile)
then set the print_sequence to "all_at_once" in the user changes so that it will be displayed as
an unsaved change
- If print_sequence == "one_at_a_time" in the user changes container only, meaning that it is not
saved in any quality profiles, then just reset the print_sequence in the user changes, so that it
will have the correct value ("all-at-once") without the reset-setting arrow appearing next to it.
CURA-7827
